NIST SP 800-171 Rev. 2 Level 2 (CMMC)

NIST SP 800-171 Revision 2 Level 2 - CMMC 2.0 assessment objectives (320 granular requirements)

Showing 320 controls

3.1.1[a] Access Control

Authorized users are identified.

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.1[b] Access Control

Processes acting on behalf of authorized users are identified.

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.1[c] Access Control

Devices (including other systems) authorized to connect to the system are identified.

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.1[d] Access Control

System access is limited to authorized users.

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.1[e] Access Control

System access is limited to processes acting on behalf of authorized users.

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.1[f] Access Control

System access is limited to authorized devices (including other systems).

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.10[a] Access Control

The period of inactivity after which the system initiates a session lock is defined.

Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

3.1.10[b] Access Control

Access to the system and viewing of data is prevented by initiating a session lock after the defined period of inactivity.

Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

3.1.10[c] Access Control

Previously visible information is concealed via a pattern-hiding display after the defined period of inactivity.

Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

3.1.11[a] Access Control

Conditions requiring a user session to terminate are defined.

Terminate (automatically) a user session after a defined condition.

3.1.11[b] Access Control

A user session is automatically terminated after any of the defined conditions occur.

Terminate (automatically) a user session after a defined condition.

3.1.12[a] Access Control

Remote access sessions are permitted.

Monitor and control remote access sessions.

3.1.12[b] Access Control

The types of permitted remote access are identified.

Monitor and control remote access sessions.

3.1.12[c] Access Control

Remote access sessions are controlled.

Monitor and control remote access sessions.

3.1.12[d] Access Control

Remote access sessions are monitored.

Monitor and control remote access sessions.

3.1.13[a] Access Control

Cryptographic mechanisms to protect the confidentiality of remote access sessions are identified.

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

3.1.13[b] Access Control

Cryptographic mechanisms to protect the confidentiality of remote access sessions are implemented.

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

3.1.14[a] Access Control

Managed access control points are identified and implemented.

Route remote access via managed access control points.

3.1.14[b] Access Control

Remote access is routed through managed network access control points.

Route remote access via managed access control points.

3.1.15[a] Access Control

Privileged commands authorized for remote execution are identified.

Authorize remote execution of privileged commands and remote access to security-relevant information.

3.1.15[b] Access Control

Security-relevant information authorized to be accessed remotely is identified.

Authorize remote execution of privileged commands and remote access to security-relevant information.

3.1.15[c] Access Control

The execution of the identified privileged commands via remote access is authorized.

Authorize remote execution of privileged commands and remote access to security-relevant information.

3.1.15[d] Access Control

Access to the identified security-relevant information via remote access is authorized.

Authorize remote execution of privileged commands and remote access to security-relevant information.

3.1.16[a] Access Control

Wireless access points are identified.

Authorize wireless access prior to allowing such connections.

3.1.16[b] Access Control

Wireless access is authorized prior to allowing such connections.

Authorize wireless access prior to allowing such connections.

3.1.17[a] Access Control

Wireless access to the system is protected using encryption.

Protect wireless access using authentication and encryption.

3.1.17[b] Access Control

Wireless access to the system is protected using authentication.

Protect wireless access using authentication and encryption.

3.1.18[a] Access Control

Mobile devices that process, store, or transmit CUI are identified.

Control connection of mobile devices.

3.1.18[b] Access Control

The connection of mobile devices is authorized.

Control connection of mobile devices.

3.1.18[c] Access Control

Mobile device connections are monitored and logged.

Control connection of mobile devices.

3.1.19[a] Access Control

Mobile devices and mobile computing platforms that process, store, or transmit CUI are identified.

Encrypt CUI on mobile devices and mobile computing platforms.

3.1.19[b] Access Control

Encryption is employed to protect CUI on identified mobile devices and mobile computing platforms.

Encrypt CUI on mobile devices and mobile computing platforms.

3.1.2[a] Access Control

The types of transactions and functions that authorized users are permitted to execute are defined.

Limit system access to the types of transactions and functions that authorized users are permitted to execute.

3.1.2[b] Access Control

System access is limited to the defined types of transactions and functions for authorized users.

Limit system access to the types of transactions and functions that authorized users are permitted to execute.

3.1.20[a] Access Control

Connections to external systems are identified.

Verify and control/limit connections to and use of external systems.

3.1.20[b] Access Control

Use of external systems is identified.

Verify and control/limit connections to and use of external systems.

3.1.20[c] Access Control

Connections to external systems are verified.

Verify and control/limit connections to and use of external systems.

3.1.20[d] Access Control

Use of external systems is verified.

Verify and control/limit connections to and use of external systems.

3.1.20[e] Access Control

Connections to external systems are controlled/limited.

Verify and control/limit connections to and use of external systems.

3.1.20[f] Access Control

Use of external systems is controlled/limited.

Verify and control/limit connections to and use of external systems.

3.1.21[a] Access Control

Use of organizational portable storage devices containing CUI on external systems is identified and documented.

Limit use of organizational portable storage devices on external systems.

3.1.21[b] Access Control

Limits on the use of organizational portable storage devices containing CUI on external systems are defined.

Limit use of organizational portable storage devices on external systems.

3.1.21[c] Access Control

Use of organizational portable storage devices containing CUI on external systems is limited as defined.

Limit use of organizational portable storage devices on external systems.

3.1.22[a] Access Control

Individuals authorized to post or process information on publicly accessible systems are identified.

Control CUI posted or processed on publicly accessible systems.

3.1.22[b] Access Control

Procedures to ensure CUI is not posted or processed on publicly accessible systems are identified.

Control CUI posted or processed on publicly accessible systems.

3.1.22[c] Access Control

A review process in in place prior to posting of any content to publicly accessible systems.

Control CUI posted or processed on publicly accessible systems.

3.1.22[d] Access Control

Content on publicly accessible systems is reviewed to ensure that it does not include

FCI. Control CUI posted or processed on publicly accessible systems.

3.1.22[e] Access Control

Mechanisms are in place to remove and address improper posting of FCI.

Control CUI posted or processed on publicly accessible systems.

3.1.3[a] Access Control

Information flow control policies are defined.

Control the flow of CUI in accordance with approved authorizations.

3.1.3[b] Access Control

Methods and enforcement mechanisms for controlling the flow of CUI are defined.

Control the flow of CUI in accordance with approved authorizations.

3.1.3[c] Access Control

Designated sources and destinations (e.g., networks, individuals, and devices) for CUI within systems and between interconnected systems are identified.

Control the flow of CUI in accordance with approved authorizations.

3.1.3[d] Access Control

Authorizations for controlling the flow of CUI are defined.

Control the flow of CUI in accordance with approved authorizations.

3.1.3[e] Access Control

Approved authorizations for controlling the flow of CUI are enforced.

Control the flow of CUI in accordance with approved authorizations.

3.1.4[a] Access Control

The duties of individuals requiring separation are defined.

Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

3.1.4[b] Access Control

Responsibilities for duties that require separation are assigned to separate individuals.

Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

3.1.4[c] Access Control

Access privileges that enable individuals to exercise the duties that require separation are granted to separate individuals.

Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

3.1.5[a] Access Control

Privileged accounts are identified.

Employ the principle of least privilege, including for specific security functions and privileged accounts.

3.1.5[b] Access Control

Access to privileged accounts is authorized in accordance with the principle of least privilege.

Employ the principle of least privilege, including for specific security functions and privileged accounts.

3.1.5[c] Access Control

Security functions are identified.

Employ the principle of least privilege, including for specific security functions and privileged accounts.

3.1.5[d] Access Control

Access to security functions is authorized in accordance with the principle of least privilege.

Employ the principle of least privilege, including for specific security functions and privileged accounts.

3.1.6[a] Access Control

Nonsecurity functions are identified.

Use non-privileged accounts or roles when accessing nonsecurity functions.

3.1.6[b] Access Control

Users are required to use non-privileged accounts or roles when accessing nonsecurity functions.

Use non-privileged accounts or roles when accessing nonsecurity functions.

3.1.7[a] Access Control

Privileged functions are defined.

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

3.1.7[b] Access Control

Non-privileged users are defined.

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

3.1.7[c] Access Control

Non-privileged users are prevented from executing privileged functions.

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

3.1.7[d] Access Control

The execution of privileged functions is captured in audit logs.

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

3.1.8[a] Access Control

The means of limiting unsuccessful logon attempts is defined.

Limit unsuccessful logon attempts.

3.1.8[b] Access Control

The defined means of limiting unsuccessful logon attempts is implemented.

Limit unsuccessful logon attempts.

3.1.9[a] Access Control

Privacy and security notices required by CUI-specified rules are identified, consistent, and associated with the specific CUI category.

Provide privacy and security notices consistent with applicable CUI rules.

3.1.9[b] Access Control

Privacy and security notices are displayed.

Provide privacy and security notices consistent with applicable CUI rules.

3.3.1[a] Audit and Accountability

Audit logs needed (i.e., event types to be logged) to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity are specified.

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.1[b] Audit and Accountability

The content of audit records needed to support monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity is defined.

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.1[c] Audit and Accountability

Audit records are created (generated).

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.1[d] Audit and Accountability

Audit records, once created, contain the defined content.

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.1[e] Audit and Accountability

Retention requirements for audit records are defined.

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.1[f] Audit and Accountability

Audit records are retained as defined.

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[a] Audit and Accountability

The content of the audit records needed to support the ability to uniquely trace users to their actions is defined.

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.2[b] Audit and Accountability

Audit records, once created, contain the defined content.

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[a] Audit and Accountability

A process for determining when to review logged events is defined.

Review and update logged events.

3.3.3[b] Audit and Accountability

Event types being logged are reviewed in accordance with the defined review process.

Review and update logged events.

3.3.3[c] Audit and Accountability

Event types being logged are updated based on the review.

Review and update logged events.

3.3.4[a] Audit and Accountability

Personnel or roles to be alerted in the event of an audit logging process failure are identified.

Alert in the event of an audit logging process failure.

3.3.4[b] Audit and Accountability

Types of audit logging process failures for which alert will be generated are defined.

Alert in the event of an audit logging process failure.

3.3.4[c] Audit and Accountability

Identified personnel or roles are alerted in the event of an audit logging process failure.

Alert in the event of an audit logging process failure.

3.3.5[a] Audit and Accountability

Audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity are defined.

Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.

3.3.5[b] Audit and Accountability

Defined audit record review, analysis, and reporting processes are correlated.

Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.

3.3.6[a] Audit and Accountability

An audit record reduction capability that supports on-demand analysis is provided.

Provide audit record reduction and report generation to support on-demand analysis and reporting.

3.3.6[b] Audit and Accountability

A report generation capability that supports on-demand reporting is provided.

Provide audit record reduction and report generation to support on-demand analysis and reporting.

3.3.7[a] Audit and Accountability

Internal system clocks are used to generate time stamps for audit records.

Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

3.3.7[b] Audit and Accountability

An authoritative source with which to compare and synchronize internal system clocks is specified.

Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

3.3.7[c] Audit and Accountability

Internal system clocks used to generate time stamps for audit records are compared to and synchronized with the specified authoritative time source.

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[a] Audit and Accountability

Audit information is protected from unauthorized access.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.8[b] Audit and Accountability

Audit information is protected from unauthorized modification.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.8[c] Audit and Accountability

Audit information is protected from unauthorized deletion.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.8[d] Audit and Accountability

Audit logging tools are protected from unauthorized access.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.8[e] Audit and Accountability

Audit logging tools are protected from unauthorized modification.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.8[f] Audit and Accountability

Audit logging tools are protected from unauthorized deletion.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.9[a] Audit and Accountability

A subset of privileged users granted access to manage audit logging functionality is defined.

Limit management of audit logging functionality to a subset of privileged users.

3.3.9[b] Audit and Accountability

Management of audit logging functionality is limited to the defined subset of privileged users.

Limit management of audit logging functionality to a subset of privileged users.

3.2.1[a] Awareness and Training

Security risks associated with organizational activities involving CUI are identified.

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

3.2.1[b] Awareness and Training

Policies, standards, and procedures related to the security of the system are identified.

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

3.2.1[c] Awareness and Training

Managers, systems administrators, and users of the system are made aware of the security risks associated with their activities.

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

3.2.1[d] Awareness and Training

Managers, systems administrators, and users of the system are made aware of the applicable policies, standards, and procedures related to the security of the system.

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

3.2.2[a] Awareness and Training

Information security-related duties, roles, and responsibilities are defined.

Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.

3.2.2[b] Awareness and Training

Information security-related duties, roles, and responsibilities are assigned to designated personnel.

Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.

3.2.2[c] Awareness and Training

Personnel are adequately trained to carry out their assigned information security-related duties, roles, and responsibilities.

Ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.

3.2.3[a] Awareness and Training

Potential indicators associated with insider threats are identified.

Provide security awareness training on recognizing and reporting potential indicators of insider threat.

3.2.3[b] Awareness and Training

Security awareness training on recognizing and reporting potential indicators of insider threat is provided to managers and employees.

Provide security awareness training on recognizing and reporting potential indicators of insider threat.

3.4.1[a] Configuration Management

A baseline configuration is established.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.1[b] Configuration Management

The baseline configuration includes hardware, software, firmware, and documentation.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.1[c] Configuration Management

The baseline configuration is maintained (reviewed and updated) throughout the system development life cycle.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.1[d] Configuration Management

A system inventory is established.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.1[e] Configuration Management

The system inventory includes hardware, software, firmware, and documentation.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.1[f] Configuration Management

The inventory is maintained (reviewed and updated) throughout the system development life cycle.

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life c...

3.4.2[a] Configuration Management

Security configuration settings for information technology products employed in the system are established and included in the baseline configuration.

Establish and enforce security configuration settings for information technology products employed in organizational systems.

3.4.2[b] Configuration Management

Security configuration settings for information technology products employed in the system are enforced.

Establish and enforce security configuration settings for information technology products employed in organizational systems.

3.4.3[a] Configuration Management

changes to the system are tracked.

Track, review, approve or disapprove, and log changes to organizational systems.

3.4.3[b] Configuration Management

Changes to the system are reviewed.

Track, review, approve or disapprove, and log changes to organizational systems.

3.4.3[c] Configuration Management

Changes to the system are approved or disapproved.

Track, review, approve or disapprove, and log changes to organizational systems.

3.4.3[d] Configuration Management

Changes to the system are logged.

Track, review, approve or disapprove, and log changes to organizational systems.

3.4.4 Configuration Management

Determine if the security impact of changes to each organizational system is analyzed prior to implementation.

Analyze the security impact of changes prior to implementation.

3.4.5[a] Configuration Management

Physical access restrictions associated with changes to the system are defined.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[b] Configuration Management

Physical access restrictions associated with changes to the system are documented.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[c] Configuration Management

Physical access restrictions associated with changes to the system are approved.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[d] Configuration Management

Physical access restrictions associated with changes to the system are enforced.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[e] Configuration Management

Logical access restrictions associated with changes to the system are defined.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[f] Configuration Management

Logical access restrictions associated with changes to the system are documented.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[g] Configuration Management

Logical access restrictions associated with changes to the system are approved.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.5[h] Configuration Management

Logical access restrictions associated with changes to the system are enforced.

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.6[a] Configuration Management

Essential system capabilities are defined based on the principle of least functionality.

Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

3.4.6[b] Configuration Management

The system is configured to provide only the defined essential capabilities.

Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

3.4.7[a] Configuration Management

Essential programs are defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[b] Configuration Management

The use of nonessential programs is defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[c] Configuration Management

The use of nonessential programs is restricted, disabled, or prevented as defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[d] Configuration Management

Essential functions are defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[e] Configuration Management

The use of nonessential functions is defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[f] Configuration Management

The use of nonessential functions is restricted, disabled, or prevented as defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[g] Configuration Management

Essential ports are defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[h] Configuration Management

The use of nonessential ports is defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[i] Configuration Management

The use of nonessential ports is restricted, disabled, or prevented as defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[j] Configuration Management

Essential protocols are defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[k] Configuration Management

The use of nonessential protocols is defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[l] Configuration Management

The use of nonessential protocols is restricted, disabled, or prevented as defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[m] Configuration Management

Essential services are defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[n] Configuration Management

The use of nonessential services is defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.7[o] Configuration Management

The use of nonessential services is restricted, disabled, or prevented as defined.

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.8[a] Configuration Management

A policy specifying whether whitelisting or blacklisting is to be implemented is specified.

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.8[b] Configuration Management

The software allowed to execute under whitelisting or denied use under blacklisting is specified.

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.8[c] Configuration Management

Whitelisting to allow the execution of authorized software or blacklisting to prevent the use of unauthorized software is implemented as specified.

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[a] Configuration Management

A policy for controlling the installation of software by users is established.

Control and monitor user-installed software.

3.4.9[b] Configuration Management

Installation of software by users is controlled based on the established policy.

Control and monitor user-installed software.

3.4.9[c] Configuration Management

Installation of software by users is monitored.

Control and monitor user-installed software.

3.5.1[a] Identification and Authentication

System users are identified.

Identify system users, processes acting on behalf of users, and devices.

3.5.1[b] Identification and Authentication

Processes acting on behalf of users are identified.

Identify system users, processes acting on behalf of users, and devices.

3.5.1[c] Identification and Authentication

Devices accessing the system are identified.

Identify system users, processes acting on behalf of users, and devices.

3.5.10[a] Identification and Authentication

Passwords are cryptographically protected in storage.

Store and transmit only cryptographically-protected passwords.

3.5.10[b] Identification and Authentication

Passwords are cryptographically protected in transit.

Store and transmit only cryptographically-protected passwords.

3.5.11 Identification and Authentication

Determine if authentication information is obscured during the authentication process.

Obscure feedback of authentication information.

3.5.2[a] Identification and Authentication

The identity of each user is authenticated or verified as a prerequisite to system access.

Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems

3.5.2[b] Identification and Authentication

The identity of each process acting on behalf of a user is authenticated or verified as a prerequisite to system access.

Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems

3.5.2[c] Identification and Authentication

The identity of each device accessing or connecting to the system is authenticated or verified as a prerequisite to system access.

Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems

3.5.3[a] Identification and Authentication

Privileged accounts are identified.

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

3.5.3[b] Identification and Authentication

Multifactor authentication is implemented for local access to privileged accounts.

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

3.5.3[c] Identification and Authentication

Multifactor authentication is implemented for network access to privileged accounts.

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

3.5.3[d] Identification and Authentication

Multifactor authentication is implemented for network access to non-privileged accounts.

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

3.5.4 Identification and Authentication

Determine if replay-resistant authentication mechanisms are implemented for all network account access to privileged and non-privileged accounts.

Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.

3.5.5[a] Identification and Authentication

A period within which identifiers cannot be reused is defined.

Prevent reuse of identifiers for a defined period.

3.5.5[b] Identification and Authentication

Reuse of identifiers is prevented within the defined period.

Prevent reuse of identifiers for a defined period.

3.5.6[a] Identification and Authentication

A period of inactivity after which an identifier is disabled is defined.

Disable identifiers after a defined period of inactivity.

3.5.6[b] Identification and Authentication

Identifiers are disabled after the defined period of inactivity.

Disable identifiers after a defined period of inactivity.

3.5.7[a] Identification and Authentication

Password complexity requirements are defined.

Enforce a minimum password complexity and change of characters when new passwords are created.

3.5.7[b] Identification and Authentication

Password change of character requirements are defined.

Enforce a minimum password complexity and change of characters when new passwords are created.

3.5.7[c] Identification and Authentication

Minimum password complexity requirements as defined are enforced when new passwords are created.

Enforce a minimum password complexity and change of characters when new passwords are created.

3.5.7[d] Identification and Authentication

Minimum password change of character requirements as defined are enforced when new passwords are created.

Enforce a minimum password complexity and change of characters when new passwords are created.

3.5.8[a] Identification and Authentication

The number of generations during which a password cannot be reused is specified.

Prohibit password reuse for a specified number of generations.

3.5.8[b] Identification and Authentication

Reuse of passwords is prohibited during the specified number of generations.

Prohibit password reuse for a specified number of generations.

3.5.9 Identification and Authentication

Determine if an immediate change to a permanent password is required when a temporary password is used for system logon.

Allow temporary password use for system logons with an immediate change to a permanent password

3.6.1[a] Incident Response

An operational incident-handling capability is established.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[b] Incident Response

The operational incident-handling capability includes preparation.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[c] Incident Response

The operational incident-handling capability includes detection.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[d] Incident Response

The operational incident-handling capability includes analysis.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[e] Incident Response

Establish an operational incident-handling capability for organizational systems.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[f] Incident Response

The operational incident-handling capability includes recovery.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.1[g] Incident Response

The operational incident-handling capability includes user response activities.

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.2[a] Incident Response

Incidents are tracked.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.2[b] Incident Response

Incidents are documented.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.2[c] Incident Response

Authorities to whom incidents are to be reported are identified.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.2[d] Incident Response

Organizational officials to whom incidents are to be reported are identified.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.2[e] Incident Response

Identified authorities are notified of incidents.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.2[f] Incident Response

Identified organizational officials are notified of incidents.

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.3 Incident Response

Determine if the incident response capability is tested.

Test the organizational incident response capability.

3.7.1 Maintenance

Determine if system maintenance is performed.

Perform maintenance on organizational systems.

3.7.2[a] Maintenance

Tools used to conduct system maintenance are controlled.

Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3.7.2[b] Maintenance

Techniques used to conduct system maintenance are controlled.

Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3.7.2[c] Maintenance

Mechanisms used to conduct system maintenance are controlled.

Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3.7.2[d] Maintenance

Personnel used to conduct system maintenance are controlled.

Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3.7.3 Maintenance

Determine if equipment to be removed from organizational spaces for off-site maintenance is sanitized of any CUI.

Ensure equipment removed for off-site maintenance is sanitized of any CUI.

3.7.4 Maintenance

Determine if media containing diagnostic and test programs are checked for malicious code before being used in organizational systems that process, store, or transmit CUI.

Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems

3.7.5[a] Maintenance

Multifactor authentication is required to establish nonlocal maintenance sessions via external network connections.

Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

3.7.5[b] Maintenance

Nonlocal maintenance sessions established via external network connections are terminated when nonlocal maintenance is complete.

Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

3.7.6 Maintenance

Determine if maintenance personnel without required access authorization are supervised during maintenance activities.

Supervise the maintenance activities of maintenance personnel without required access authorization.

3.8.1[a] Media Protection

Paper media containing CUI is physically controlled.

Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

3.8.1[b] Media Protection

Digital media containing CUI is physically controlled.

Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

3.8.1[c] Media Protection

Paper media containing CUI is securely stored.

Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

3.8.1[d] Media Protection

Digital media containing CUI is securely stored.

Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

3.8.2 Media Protection

Determine if access to CUI on system media is limited to authorized users.

Limit access to CUI on system media to authorized users.

3.8.3[a] Media Protection

System media containing CUI is sanitized or destroyed before disposal.

Sanitize or destroy system media containing CUI before disposal or release for reuse.

3.8.3[b] Media Protection

System media containing CUI is sanitized before it is released for reuse.

Sanitize or destroy system media containing CUI before disposal or release for reuse.

3.8.4[a] Media Protection

Media containing CUI is marked with applicable CUI markings.

Mark media with necessary CUI markings and distribution limitations.

3.8.4[b] Media Protection

Media containing CUI is marked with distribution limitations.

Mark media with necessary CUI markings and distribution limitations.

3.8.5[a] Media Protection

Access to media containing CUI is controlled.

Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.

3.8.5[b] Media Protection

Accountability for media containing CUI is maintained during transport outside of controlled areas.

Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.

3.8.6 Media Protection

Determine if the confidentiality of CUI stored on digital media is protected during transport using cryptographic mechanisms or alternative physical safeguards.

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 Media Protection

Determine if the use of removable media on system components containing CUI is controlled.

Control the use of removable media on system components.

3.8.8 Media Protection

Determine if the use of portable storage devices is prohibited when such devices have no identifiable owner.

Prohibit the use of portable storage devices when such devices have no identifiable owner.

3.8.9 Media Protection

Determine if the confidentiality of backup CUI is protected at storage locations.

Protect the confidentiality of backup CUI at storage locations.

3.9.1 Personnel Security

Determine if individuals are screened prior to authorizing access to organizational systems.

Screen individuals prior to authorizing access to organizational systems containing CUI.

3.9.2[a] Personnel Security

A policy and/or process for terminating system access authorization and any credentials coincident with personnel actions is established.

Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

3.9.2[b] Personnel Security

System access and credentials are terminated consistent with personnel actions such as termination or transfer.

Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

3.9.2[c] Personnel Security

The system is protected during and after personnel transfer actions.

Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

3.10.1[a] Physical Protection

Authorized individuals allowed physical access are identified.

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

3.10.1[b] Physical Protection

Physical access to organizational systems is limited to authorized individuals.

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

3.10.1[c] Physical Protection

Physical access to equipment is limited to authorized individuals.

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

3.10.1[d] Physical Protection

Physical access to operating environments is limited to authorized individuals.

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

3.10.2[a] Physical Protection

The physical facility where that system resides is protected.

Protect and monitor the physical facility and support infrastructure for organizational systems.

3.10.2[b] Physical Protection

The support infrastructure for that system is protected.

Protect and monitor the physical facility and support infrastructure for organizational systems.

3.10.2[c] Physical Protection

The physical facility where that system resides is monitored.

Protect and monitor the physical facility and support infrastructure for organizational systems.

3.10.2[d] Physical Protection

The support infrastructure for that system is monitored.

Protect and monitor the physical facility and support infrastructure for organizational systems.

3.10.3[a] Physical Protection

Visitors are escorted.

Escort visitors and monitor visitor activity.

3.10.3[b] Physical Protection

Visitor activity is monitored.

Escort visitors and monitor visitor activity.

3.10.4 Physical Protection

Determine if audit logs of physical access are maintained.

Maintain audit logs of physical access.

3.10.5[a] Physical Protection

Physical access devices are identified.

Control and manage physical access devices.

3.10.5[b] Physical Protection

Physical access devices are controlled.

Control and manage physical access devices.

3.10.5[c] Physical Protection

Physical access devices are managed.

Control and manage physical access devices.

3.10.6[a] Physical Protection

Safeguarding measures for CUI are defined for alternate work sites.

Enforce safeguarding measures for CUI at alternate work sites.

3.10.6[b] Physical Protection

Safeguarding measures for CUI are enforced for alternate work sites.

Enforce safeguarding measures for CUI at alternate work sites.

3.11.1[a] Risk Assessment

The frequency to assess risk to organizational operations, organizational assets, and individuals is defined.

Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational s...

3.11.1[b] Risk Assessment

Risk to organizational operations, organizational assets, and individuals resulting from the operation of an organizational system that processes, stores, or transmits CUI is assessed with the defined frequency.

Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational s...

3.11.2[a] Risk Assessment

The frequency to scan for vulnerabilities in an organizational system and its applications that process, store, or transmit CUI is defined.

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.2[b] Risk Assessment

Vulnerability scans are performed in an organizational system that processes, stores, or transmits CUI with the defined frequency.

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.2[c] Risk Assessment

Vulnerability scans are performed in an application that contains CUI with the defined frequency.

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.2[d] Risk Assessment

Vulnerability scans are performed in an organizational system that processes, stores, or transmits CUI when new vulnerabilities are identified.

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.2[e] Risk Assessment

Vulnerability scans are performed in an application that contains CUI when new vulnerabilities are identified.

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.3[a] Risk Assessment

Vulnerabilities are identified.

Remediate vulnerabilities in accordance with risk assessments.

3.11.3[b] Risk Assessment

Vulnerabilities are remediated in accordance with risk assessments.

Remediate vulnerabilities in accordance with risk assessments.

3.12.1[a] Security Assessment

The frequency of security control assessments is defined.

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

3.12.1[b] Security Assessment

Security controls are assessed with the defined frequency to determine if the controls are effective in their application.

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

3.12.2[a] Security Assessment

Deficiencies and vulnerabilities to be addressed by the plan of action are identified.

Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems

3.12.2[b] Security Assessment

A plan of action is developed to correct identified deficiencies and reduce or eliminate identified vulnerabilities.

Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems

3.12.2[c] Security Assessment

The plan of action is implemented to correct identified deficiencies and reduce or eliminate identified vulnerabilities.

Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems

3.12.3 Security Assessment

Determine if security controls are monitored on an ongoing basis to ensure the continued effectiveness of those controls.

Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.

3.12.4.[h] Security Assessment

System security plan is updated with the defined frequency.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[a] Security Assessment

A system security plan is developed.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[b] Security Assessment

The system boundary is described and documented in the system security plan.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[c] Security Assessment

The system environment of operation is described and documented in the system security plan.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[d] Security Assessment

The security requirements identified and approved by the designated authority as non-applicable are identified.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[e] Security Assessment

The method of security requirement implementation is described and documented in the system security plan.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[f] Security Assessment

The relationship with or connection to other systems is described and documented in the system security plan.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.12.4[g] Security Assessment

The frequency to update the system security plan is defined.

Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships wit...

3.13.1[a] System and Communications Protection

The external system boundary is defined.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[b] System and Communications Protection

Key internal system boundaries are defined.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[c] System and Communications Protection

Communications are monitored at the external system boundary.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[d] System and Communications Protection

Communications are monitored at key internal boundaries.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[e] System and Communications Protection

Communications are controlled at the external system boundary.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[f] System and Communications Protection

Communications are controlled at key internal boundaries.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[g] System and Communications Protection

Communications are protected at the external system boundary.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.1[h] System and Communications Protection

Communications are protected at key internal boundaries.

Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.

3.13.10[a] System and Communications Protection

Cryptographic keys are established whenever cryptography is employed.

Establish and manage cryptographic keys for cryptography employed in organizational systems.

3.13.10[b] System and Communications Protection

Cryptographic keys are managed whenever cryptography is employed.

Establish and manage cryptographic keys for cryptography employed in organizational systems.

3.13.11 System and Communications Protection

Determine if FIPS-validated cryptography is employed to protect the confidentiality of CUI.

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

3.13.12[a] System and Communications Protection

Collaborative computing devices are identified.

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

3.13.12[b] System and Communications Protection

Collaborative computing devices provide indication to users of devices in use.

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

3.13.12[c] System and Communications Protection

Remote activation of collaborative computing devices is prohibited.

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

3.13.13[a] System and Communications Protection

Use of mobile code is controlled.

Control and monitor the use of mobile code.

3.13.13[b] System and Communications Protection

Use of mobile code is monitored.

Control and monitor the use of mobile code.

3.13.14[a] System and Communications Protection

Use of Voice over Internet Protocol (VoIP) technologies is controlled.

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.

3.13.14[b] System and Communications Protection

Use of Voice over Internet Protocol (VoIP) technologies is monitored.

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies

3.13.15 System and Communications Protection

Determine if the authenticity of communications sessions is protected.

Protect the authenticity of communications sessions.

3.13.16 System and Communications Protection

Determine if the confidentiality of CUI at rest is protected.

Protect the confidentiality of CUI at rest.

3.13.2[a] System and Communications Protection

Architectural designs that promote effective information security are identified.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.2[b] System and Communications Protection

Software development techniques that promote effective information security are identified.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.2[c] System and Communications Protection

Systems engineering principles that promote effective information security are identified.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.2[d] System and Communications Protection

Identified architectural designs that promote effective information security are employed.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.2[e] System and Communications Protection

Identified software development techniques that promote effective information security are employed.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.2[f] System and Communications Protection

Identified systems engineering principles that promote effective information security are employed.

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.3[a] System and Communications Protection

User functionality is identified.

Separate user functionality from system management functionality.

3.13.3[b] System and Communications Protection

System management functionality is identified.

Separate user functionality from system management functionality.

3.13.3[c] System and Communications Protection

User functionality is separated from system management functionality.

Separate user functionality from system management functionality.

3.13.4 System and Communications Protection

Determine if unauthorized and unintended information transfer via shared system resources is prevented.

Prevent unauthorized and unintended information transfer via shared system resources.

3.13.5[a] System and Communications Protection

Publicly accessible system components are identified.

Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

3.13.5[b] System and Communications Protection

Subnetworks for publicly accessible system components are physically or logically separated from internal networks.

Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

3.13.6[a] System and Communications Protection

Network communications traffic is denied by default.

Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

3.13.6[b] System and Communications Protection

Network communications traffic is allowed by exception.

Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

3.13.7 System and Communications Protection

Determine if remote devices are prevented from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks (i.e., split tunneling).

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

3.13.8[a] System and Communications Protection

Cryptographic mechanisms intended to prevent unauthorized disclosure of CUI are identified.

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

3.13.8[b] System and Communications Protection

Alternative physical safeguards intended to prevent unauthorized disclosure of CUI are identified.

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

3.13.8[c] System and Communications Protection

Either cryptographic mechanisms or alternative physical safeguards are implemented to prevent unauthorized disclosure of CUI during transmission.

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

3.13.9[a] System and Communications Protection

A period of inactivity to terminate network connections associated with communications sessions is defined.

Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

3.13.9[b] System and Communications Protection

Network connections associated with communications sessions are terminated at the end of the sessions.

Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

3.13.9[c] System and Communications Protection

Network connections associated with communications sessions are terminated after the defined period of inactivity.

Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

3.14.1[a] System and Information Integrity

The time within which to identify system flaws is specified.

dentify, report, and correct system flaws in a timely manner.

3.14.1[b] System and Information Integrity

System flaws are identified within the specified time frame.

dentify, report, and correct system flaws in a timely manner.

3.14.1[c] System and Information Integrity

The time within which to report system flaws is specified.

dentify, report, and correct system flaws in a timely manner.

3.14.1[d] System and Information Integrity

System flaws are reported within the specified time frame.

dentify, report, and correct system flaws in a timely manner.

3.14.1[e] System and Information Integrity

The time within which to correct system flaws is specified.

dentify, report, and correct system flaws in a timely manner.

3.14.1[f] System and Information Integrity

System flaws are corrected within the specified time frame.

dentify, report, and correct system flaws in a timely manner.

3.14.2[a] System and Information Integrity

Designated locations for malicious code protection are identified.

Provide protection from malicious code at designated locations within organizational systems.

3.14.2[b] System and Information Integrity

Protection from malicious code at designated locations is provided.

Provide protection from malicious code at designated locations within organizational systems.

3.14.3[a] System and Information Integrity

Response actions to system security alerts and advisories are identified.

Monitor system security alerts and advisories and take action in response.

3.14.3[b] System and Information Integrity

System security alerts and advisories are monitored.

Monitor system security alerts and advisories and take action in response.

3.14.3[c] System and Information Integrity

Actions in response to system security alerts and advisories are taken.

Monitor system security alerts and advisories and take action in response.

3.14.4 System and Information Integrity

Determine if malicious code protection mechanisms are updated when new releases are available.

Update malicious code protection mechanisms when new releases are available.

3.14.5[a] System and Information Integrity

The frequency for malicious code scans is defined.

Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

3.14.5[b] System and Information Integrity

Malicious code scans are performed with the defined frequency.

Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

3.14.5[c] System and Information Integrity

Real-time malicious code scans of files from external sources as files are downloaded, opened, or executed are performed.

Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

3.14.6[a] System and Information Integrity

The system is monitored to detect attacks and indicators of potential attacks.

Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

3.14.6[b] System and Information Integrity

Inbound communications traffic is monitored to detect attacks and indicators of potential attacks.

Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

3.14.6[c] System and Information Integrity

Outbound communications traffic is monitored to detect attacks and indicators of potential attacks.

Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

3.14.7[a] System and Information Integrity

Authorized use of the system is defined.

dentify unauthorized use of organizational systems.

3.14.7[b] System and Information Integrity

Unauthorized use of the system is identified.

Identify unauthorized use of organizational systems.