Cisco ASA NDM V1R3

b

The Cisco ASA must be configured to limit the number of concurrent management sessions to an organization-defined number.

AC-10 - Medium - CCI-000054 - V-239896 - SV-239896r666051_rule

RMF Control

AC-10

Severity

M

CCI

CCI-000054

Version

CASA-ND-000010

Vuln IDs

V-239896

Rule IDs

SV-239896r666051_rule

Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to DoS attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions.

Checks: C-43129r666049_chk

Review the ASA configuration to determine if concurrent management sessions are limited as show in the example below: quota management-session 2 Note: This requirement is not applicable to file transfer actions such as FTP, SCP, and SFTP. The default is 5 sessions, which would not be shown in the configuration unless the show run all command is used. If the ASA is not configured to limit the number of concurrent management sessions, this is a finding.

Fix: F-43088r666050_fix

Configure the ASA to limit the number of concurrent management sessions to an organization-defined number as shown in the example below. ASA(config)# quota management-session 2

b

The Cisco ASA must be configured to automatically audit account creation.

AC-2 - Medium - CCI-000018 - V-239897 - SV-239897r666054_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000018

Version

CASA-ND-000090

Vuln IDs

V-239897

Rule IDs

SV-239897r666054_rule

Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. Notification of account creation helps to mitigate this risk. Auditing account creation provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes.

Checks: C-43130r666052_chk

Review the ASA configuration to determine if it automatically audits account creation. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If account creation is not automatically audited, this is a finding.

Fix: F-43089r666053_fix

Configure the ASA to log account creation using the following commands: ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to automatically audit account modification.

AC-2 - Medium - CCI-001403 - V-239898 - SV-239898r666057_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001403

Version

CASA-ND-000100

Vuln IDs

V-239898

Rule IDs

SV-239898r666057_rule

Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel with the appropriate and necessary privileges. Auditing account modification along with an automatic notification to appropriate individuals will provide the necessary reconciliation that account management procedures are being followed. If modifications to management accounts are not audited, reconciliation of account management procedures cannot be tracked.

Checks: C-43131r666055_chk

Review the ASA configuration to determine if it automatically audits account modification. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If account modification is not automatically audited, this is a finding.

Fix: F-43090r666056_fix

Configure the ASA to log account modification using the following commands: ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to automatically audit account-disabling actions.

AC-2 - Medium - CCI-001404 - V-239899 - SV-239899r682909_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001404

Version

CASA-ND-000110

Vuln IDs

V-239899

Rule IDs

SV-239899r682909_rule

Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account disabling actions will support account management procedures. When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.

Checks: C-43132r666058_chk

Review the ASA configuration to determine if it automatically audits account disabling. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If account disabling is not automatically audited, this is a finding.

Fix: F-43091r666059_fix

Configure the ASA to log account disabling using the following commands: ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to automatically audit account removal actions.

AC-2 - Medium - CCI-001405 - V-239900 - SV-239900r666063_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001405

Version

CASA-ND-000120

Vuln IDs

V-239900

Rule IDs

SV-239900r666063_rule

Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will support account management procedures. When device management accounts are terminated, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.

Checks: C-43133r666061_chk

Review the ASA configuration to determine if it automatically audits account removal. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If account removal is not automatically audited, this is a finding.

Fix: F-43092r666062_fix

Configure the ASA to log account removal using the following commands: ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to enforce approved authorizations for controlling the flow of management information within the Cisco ASA based on information flow control policies.

AC-4 - Medium - CCI-001368 - V-239901 - SV-239901r666066_rule

RMF Control

AC-4

Severity

M

CCI

CCI-001368

Version

CASA-ND-000140

Vuln IDs

V-239901

Rule IDs

SV-239901r666066_rule

A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management information flow is not enforced based on approved authorizations, the network device may become compromised. Information flow control regulates where management information is allowed to travel within a network device. The flow of all management information must be monitored and controlled so it does not introduce any unacceptable risk to the network device or data. Application-specific examples of enforcement occur in systems that employ rule sets or establish configuration settings that restrict information system services or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of management information within the system in accordance with applicable policy.

Checks: C-43134r666064_chk

Review the Cisco ASA configuration to verify that management access is restricted to specific IP address space as shown in the example below. ssh x.x.x.0 255.255.255.0 INSIDE If the Cisco ASA is not configured to enforce approved authorizations for controlling the flow of management information within the device based on control policies, this is a finding.

Fix: F-43093r666065_fix

Configure the Cisco ASA to restrict management access to specific IP addresses via SSH as shown in the example below. ASA(config)# ssh x.x.x.0 255.255.255.0 INSIDE ASA(config)# end

b

The Cisco ASA must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.

AC-8 - Medium - CCI-000048 - V-239902 - SV-239902r666069_rule

RMF Control

AC-8

Severity

M

CCI

CCI-000048

Version

CASA-ND-000160

Vuln IDs

V-239902

Rule IDs

SV-239902r666069_rule

Display of the DoD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users.

Checks: C-43135r666067_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement as shown in the example below. banner login You are accessing a U.S. Government (USG) Information System (IS) that is provided banner login for USG-authorized use only. banner login banner login By using this IS (which includes any device attached to this IS), you consent to the banner login following conditions: banner login banner login -The USG routinely intercepts and monitors communications on this IS for purposes banner login including, but not limited to, penetration testing, COMSEC monitoring, network banner login operations and defense, personnel misconduct (PM), law enforcement (LE), and banner login counterintelligence (CI) investigations. banner login banner login -At any time, the USG may inspect and seize data stored on this IS. banner login banner login -Communications using, or data stored on, this IS are not private, are subject to routine banner login monitoring, interception, and search, and may be disclosed or used for any USG- banner login authorized purpose. banner login banner login -This IS includes security measures (e.g., authentication and access controls) to protect banner login USG interests--not for your personal benefit or privacy. banner login banner login -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI banner login investigative searching or monitoring of the content of privileged communications, or banner login work product, related to personal representation or services by attorneys, banner login psychotherapists, or clergy, and their assistants. Such communications and work product banner login are private and banner login confidential. See User Agreement for details. If the Cisco ASA is not configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device, this is a finding.

Fix: F-43094r666068_fix

ASA(config)# banner login You are accessing a U.S. Government (USG) Information System (IS) that is provided ASA(config)# banner login for USG-authorized use only. ASA(config)# banner login ASA(config)# banner login By using this IS (which includes any device attached to this IS), you consent to the ASA(config)# banner login following conditions: ASA(config)# banner login ASA(config)# banner login -The USG routinely intercepts and monitors communications on this IS for purposes ASA(config)# banner login including, but not limited to, penetration testing, COMSEC monitoring, network ASA(config)# banner login operations and defense, personnel misconduct (PM), law enforcement (LE), and ASA(config)# banner login counterintelligence (CI) investigations. ASA(config)# banner login ASA(config)# banner login -At any time, the USG may inspect and seize data stored on this IS. ASA(config)# banner login ASA(config)# banner login -Communications using, or data stored on, this IS are not private, are subject to routine ASA(config)# banner login monitoring, interception, and search, and may be disclosed or used for any USG- ASA(config)# banner login authorized purpose. ASA(config)# banner login ASA(config)# banner login -This IS includes security measures (e.g., authentication and access controls) to protect ASA(config)# banner login USG interests--not for your personal benefit or privacy. ASA(config)# banner login ASA(config)# banner login -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI ASA(config)# banner login investigative searching or monitoring of the content of privileged communications, or ASA(config)# banner login work product, related to personal representation or services by attorneys, ASA(config)# banner login psychotherapists, or clergy, and their assistants. Such communications and work product ASA(config)# banner login are private and ASA(config)# banner login confidential. See User Agreement for details. ASA(config)# end

b

The Cisco ASA must be configured to protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.

AU-10 - Medium - CCI-000166 - V-239903 - SV-239903r666072_rule

RMF Control

AU-10

Severity

M

CCI

CCI-000166

Version

CASA-ND-000210

Vuln IDs

V-239903

Rule IDs

SV-239903r666072_rule

This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration management process. All configuration changes to the network device are logged. To meet this requirement, the network device must log administrator access and activity.

Checks: C-43136r666070_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands that include the name of the user. The ASA also logs the name of the user entering the enable command. If logging of administrator activity is not configured, this is a finding.

Fix: F-43095r666071_fix

Configure the ASA to log administrator activity as shown below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records when successful/unsuccessful attempts to access privileges occur.

AU-12 - Medium - CCI-000172 - V-239904 - SV-239904r666075_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-000240

Vuln IDs

V-239904

Rule IDs

SV-239904r666075_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter).

Checks: C-43137r666073_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log all login attempts as well as the name of the user entering the enable command. If the Cisco ASA is not configured to generate audit records when successful/unsuccessful attempts to logon, this is a finding.

Fix: F-43096r666074_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to produce audit log records containing sufficient information to establish what type of event occurred.

AU-3 - Medium - CCI-000130 - V-239905 - SV-239905r666078_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000130

Version

CASA-ND-000260

Vuln IDs

V-239905

Rule IDs

SV-239905r666078_rule

It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. Without this capability, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.

Checks: C-43138r666076_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational If the ASA is not configured to generate audit records containing information to establish what type of event occurred, this is a finding.

Fix: F-43097r666077_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to produce audit records containing information to establish when (date and time) the events occurred.

AU-3 - Medium - CCI-000131 - V-239906 - SV-239906r666081_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000131

Version

CASA-ND-000270

Vuln IDs

V-239906

Rule IDs

SV-239906r666081_rule

It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Logging the date and time of each detected event provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. In order to establish and correlate the series of events leading up to an outage or attack, it is imperative the date and time are recorded in all log records.

Checks: C-43139r666079_chk

Verify that the ASA is configured to include the date and time on all log records as shown in the configuration example below. logging timestamp If time stamp is not configured, this is a finding.

Fix: F-43098r666080_fix

Configure the ASA to include the date and time on all log records as shown in the example below. ASA(config)# logging timestamp

b

The Cisco ASA must be configured to produce audit records containing information to establish where the events occurred.

AU-3 - Medium - CCI-000132 - V-239907 - SV-239907r666084_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000132

Version

CASA-ND-000280

Vuln IDs

V-239907

Rule IDs

SV-239907r666084_rule

In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as device hardware components, device software modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the network device provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured device.

Checks: C-43140r666082_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log location (IP address or console) from where configuration commands are entered. If the ASA is not configured to generate audit records containing information to establish where the events occurred, this is a finding.

Fix: F-43099r666083_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to produce audit log records containing information to establish the source of events.

AU-3 - Medium - CCI-000133 - V-239908 - SV-239908r666087_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000133

Version

CASA-ND-000290

Vuln IDs

V-239908

Rule IDs

SV-239908r666087_rule

In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the source of the event. The source may be a component, module, or process within the device or an external session, administrator, or device. Associating information about where the source of the event occurred provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured device.

Checks: C-43141r666085_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log location (IP address or console) from where configuration commands are entered. If the ASA is not configured to generate audit records containing information to establish the source of events, this is a finding.

Fix: F-43100r666086_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to produce audit records that contain information to establish the outcome of the event.

AU-3 - Medium - CCI-000134 - V-239909 - SV-239909r666090_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000134

Version

CASA-ND-000300

Vuln IDs

V-239909

Rule IDs

SV-239909r666090_rule

Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the device after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.

Checks: C-43142r666088_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational If the ASA is not configured to generate audit records containing information to establish the outcome of the event, this is a finding.

Fix: F-43101r666089_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records containing the full-text recording of privileged commands.

AU-3 - Medium - CCI-000135 - V-239910 - SV-239910r666093_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

CASA-ND-000320

Vuln IDs

V-239910

Rule IDs

SV-239910r666093_rule

Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the data and the environment within which it resides). At a minimum, the organization must audit full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.

Checks: C-43143r666091_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational Note: The ASA will log full-text recording of privileged commands. If the Cisco ASA is not configured to generate audit records containing the full-text recording of privileged commands, this is a finding.

Fix: F-43102r666092_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

c

The Cisco ASA must be configured to prohibit the use of all unnecessary and/or non-secure functions, ports, protocols, and/or services.

CM-7 - High - CCI-000382 - V-239911 - SV-239911r666096_rule

RMF Control

CM-7

Severity

H

CCI

CCI-000382

Version

CASA-ND-000430

Vuln IDs

V-239911

Rule IDs

SV-239911r666096_rule

In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused or unnecessary physical and logical ports/protocols on information systems. Network devices are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the network device must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved. Some network devices have capabilities enabled by default; if these capabilities are not necessary, they must be disabled. If a particular capability is used, then it must be documented and approved.

Checks: C-43144r666094_chk

Verify the ASA does not have any unnecessary or non-secure ports, protocols, and services enabled. For example, the following features such as telnet should never be enabled, while other features should only be enabled if required for operations. In the example below, http and telnet service are enabled. http server enable … … … telnet 10.1.22.2 255.255.255.255 INSIDE Note: The command http server enables https and is required for ASDM. If any unnecessary or non-secure ports, protocols, or services are enabled, this is a finding.

Fix: F-43103r666095_fix

Disable features that should not be enabled unless required for operations. ASA(config)# no http server enable ASA(config)# no telnet 10.1.22.2 255.255.255.255 INSIDE ASA(config)# end Note: Telnet must always be disabled.

b

The Cisco ASA must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.

AC-2 - Medium - CCI-001358 - V-239912 - SV-239912r851023_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001358

Version

CASA-ND-000450

Vuln IDs

V-239912

Rule IDs

SV-239912r851023_rule

Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.

Checks: C-43145r666097_chk

Step 1: Review the Cisco ASA configuration to verify that a local account for last resort has been configured with a privilege level that will enable the administrator to troubleshoot connectivity to the authentication server. username LAST_RESORT password $sha512$5000$tb2eaIcI/Q5Q==$ScFJI1ChS4gIjXw== pbkdf2 privilege 15 Step 2: Verify the fallback to use local account has been configured as shown in the example below. user-identity default-domain LOCAL aaa authentication serial console RADIUS_GROUP LOCAL aaa authentication ssh console RADIUS_GROUP LOCAL If the Cisco ASA is not configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable, this is a finding.

Fix: F-43104r666098_fix

Step 1: Configure a local account with the necessary privilege level to troubleshoot network outage and restore operations as shown in the following example. ASA(config)# username LAST_RESORT privilege 15 ASA(config)# username LAST_RESORT password xxxxxxxxxxxxx Step 2: Define the AAA server. ASA(config)# aaa-server RADIUS_GROUP protocol radius ASA(config-aaa-server-group)# exit ASA(config)# aaa-server RADIUS_GROUP (NDM_INTERFACE) host 10.1.48.10 ASA(config-aaa-server-host)# key xxxxxxxxx ASA(config-aaa-server-host)# exit Step 3: Configure the authentication to use an AAA server with the fallback to use the local account if the authentication server is not reachable as shown in the following example. ASA(config)# aaa authentication serial console RADIUS_GROUP LOCAL ASA(config)# aaa authentication ssh console RADIUS_GROUP LOCAL ASA(config)# end

b

The Cisco ASA must be configured to implement replay-resistant authentication mechanisms for network access to privileged accounts.

IA-2 - Medium - CCI-001941 - V-239913 - SV-239913r851024_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001941

Version

CASA-ND-000470

Vuln IDs

V-239913

Rule IDs

SV-239913r851024_rule

A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.

Checks: C-43146r666100_chk

Step 1: Verify that FIPS mode is enabled as shown in the example. fips enable Step 2: Verify only SSH is configured to only use FIPS-compliant ciphers and that Diffie-Hellman Group 14 is used for the key exchange as shown in the example below. ssh version 2 ssh cipher encryption fips ssh key-exchange group dh-group14-sha1 Note: The ASA only supports SSHv2. If the ASA is not configured to implement replay-resistant authentication mechanisms for network access, this is a finding.

Fix: F-43105r666101_fix

Step 1: Enable FIPS mode via the fips enable command. Step 2: Configure SSH to only use FIPS-compliant ciphers and Diffie-Hellman Group 14 for the key exchange. ASA(config)# ssh cipher encryption fips ASA(config)# ssh key-exchange group dh-group14-sha

b

The Cisco ASA must be configured to enforce a minimum 15-character password length.

IA-5 - Medium - CCI-000205 - V-239914 - SV-239914r666105_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000205

Version

CASA-ND-000490

Vuln IDs

V-239914

Rule IDs

SV-239914r666105_rule

Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.

Checks: C-43147r666103_chk

Review the ASA configuration to verify that it is compliant with this requirement as shown in the example below. password-policy minimum-length 15 If the ASA is not configured to enforce a minimum 15-character password length, this is a finding.

Fix: F-43106r666104_fix

Configure the Cisco ASA to enforce password complexity by requiring a minimum 15-character password length as shown in the example below. ASA(config)# password-policy minimum-length 15

b

The Cisco ASA must be configured to enforce password complexity by requiring that at least one uppercase character be used.

IA-5 - Medium - CCI-000192 - V-239915 - SV-239915r666108_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000192

Version

CASA-ND-000520

Vuln IDs

V-239915

Rule IDs

SV-239915r666108_rule

Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.

Checks: C-43148r666106_chk

Review the ASA configuration to verify that it is compliant with this requirement as shown in the example below. password-policy minimum-uppercase 1 If the Cisco ASA is not configured to enforce password complexity by requiring that at least one uppercase character be used, this is a finding.

Fix: F-43107r666107_fix

Configure the Cisco ASA to enforce password complexity by requiring that at least one uppercase character be used as shown in the example below. ASA(config)# password-policy minimum-uppercase 1

b

The Cisco ASA must be configured to enforce password complexity by requiring that at least one lowercase character be used.

IA-5 - Medium - CCI-000193 - V-239916 - SV-239916r666111_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000193

Version

CASA-ND-000530

Vuln IDs

V-239916

Rule IDs

SV-239916r666111_rule

Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.

Checks: C-43149r666109_chk

Review the ASA configuration to verify that it is compliant with this requirement as shown in the example below. password-policy minimum-lowercase 1 If the Cisco ASA is not configured to enforce password complexity by requiring that at least one lowercase character be used, this is a finding.

Fix: F-43108r666110_fix

Configure the Cisco ASA to enforce password complexity by requiring that at least one lowercase character be used as shown in the example below. ASA(config)# password-policy minimum-lowercase 1

b

The Cisco ASA must be configured to enforce password complexity by requiring that at least one numeric character be used.

IA-5 - Medium - CCI-000194 - V-239917 - SV-239917r666114_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000194

Version

CASA-ND-000550

Vuln IDs

V-239917

Rule IDs

SV-239917r666114_rule

Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.

Checks: C-43150r666112_chk

Review the ASA configuration to verify that it is compliant with this requirement as shown in the example below. password-policy minimum-numeric 1 If the Cisco ASA is not configured to enforce password complexity by requiring that at least one numeric character be used, this is a finding.

Fix: F-43109r666113_fix

Configure the Cisco ASA to enforce password complexity by requiring that at least one numeric character be used as shown in the example below. ASA(config)# password-policy minimum-numeric 1

b

The Cisco ASA must be configured to enforce password complexity by requiring that at least one special character be used.

IA-5 - Medium - CCI-001619 - V-239918 - SV-239918r666117_rule

RMF Control

IA-5

Severity

M

CCI

CCI-001619

Version

CASA-ND-000570

Vuln IDs

V-239918

Rule IDs

SV-239918r666117_rule

Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.

Checks: C-43151r666115_chk

Review the ASA configuration to verify that it is compliant with this requirement as shown in the example below. password-policy minimum-special 1 If the Cisco ASA is not configured to enforce password complexity by requiring that at least one special character be used, this is a finding.

Fix: F-43110r666116_fix

Configure the Cisco ASA to enforce password complexity by requiring that at least one special character be used as shown in the example below. ASA(config)# password-policy minimum-special 1

b

The Cisco ASA must be configured to require that when a password is changed, the characters are changed in at least eight of the positions within the password.

IA-5 - Medium - CCI-000195 - V-239919 - SV-239919r666120_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000195

Version

CASA-ND-000580

Vuln IDs

V-239919

Rule IDs

SV-239919r666120_rule

If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.

Checks: C-43152r666118_chk

Review the ASA configuration to verify it is compliant with this requirement as shown in the example below. password-policy minimum-changes 8 If the Cisco router is not configured to require that when a password is changed, the characters are changed in at least eight of the positions within the password, this is a finding.

Fix: F-43111r666119_fix

Configure the ASA to enforce password complexity by requiring that when a password is changed, the characters are changed in at least eight of the positions within the password as shown in the example below. ASA(config)# password-policy minimum-changes 8

c

The Cisco ASA must be configured to terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements.

SC-10 - High - CCI-001133 - V-239920 - SV-239920r666196_rule

RMF Control

SC-10

Severity

H

CCI

CCI-001133

Version

CASA-ND-000690

Vuln IDs

V-239920

Rule IDs

SV-239920r666196_rule

Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.

Checks: C-43153r666121_chk

Review the Cisco ASA configuration to verify all network connections associated with a device management have an idle timeout value set to 10 minutes or less as shown in the following example: http server idle-timeout 10 … … … ssh timeout 10 … … … console timeout 10 If the Cisco ASA is not configured to terminate all network connections associated with a device management after 10 minutes of inactivity, this is a finding.

Fix: F-43112r666122_fix

Set the idle timeout value to 10 minutes or less for console, ssh, and http (if ASDM is used) access. SW1(config)# ssh timeout 10 SW1(config)# console timeout 10 ASA(config)# http server idle-timeout 10 SW1(config)# end

b

The Cisco ASA must be configured to audit the execution of privileged functions.

AC-6 - Medium - CCI-002234 - V-239921 - SV-239921r851025_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002234

Version

CASA-ND-000910

Vuln IDs

V-239921

Rule IDs

SV-239921r851025_rule

Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.

Checks: C-43154r666124_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration example below will log all configuration changes. logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If the Cisco ASA is not configured to log all configuration changes, this is a finding.

Fix: F-43113r666125_fix

Configure the Cisco ASA to log all configuration changes as shown in the following example. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.

AU-4 - Medium - CCI-001849 - V-239922 - SV-239922r851026_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

CASA-ND-000920

Vuln IDs

V-239922

Rule IDs

SV-239922r851026_rule

In order to ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. The value for the organization-defined audit record storage requirement will depend on the amount of storage available on the network device, the anticipated volume of logs, the frequency of transfer from the network device to centralized log servers, and other factors.

Checks: C-43155r666127_chk

Verify the Cisco ASA is configured with a logfile size. The configuration should look like the example below. logging flash-bufferwrap logging flash-minimum-free nnnnnnn logging flash-maximum-allocation nnnnnnn If the Cisco ASA is not configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements, this is a finding.

Fix: F-43114r666128_fix

Configure the buffer size for logging as shown in the example below. ASA(config)# logging flash-maximum-allocation nnnnnnn ASA(config)# logging flash-minimum-free nnnnnnn

b

The Cisco ASA must be configured to generate an immediate real-time alert of all audit failure events requiring real-time alerts.

AU-5 - Medium - CCI-001858 - V-239923 - SV-239923r851027_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001858

Version

CASA-ND-000930

Vuln IDs

V-239923

Rule IDs

SV-239923r851027_rule

It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).

Checks: C-43156r666130_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement as shown in the example below. logging trap critical logging host NDM_INTERFACE 10.1.48.10 Note: The parameter critical can replaced with a lesser severity (i.e., error, warning, notice, informational). A logging list can be used as an alternative to the severity level. If the Cisco ASA is not configured to generate an alert for all audit failure events, this is a finding.

Fix: F-43115r666131_fix

Configure the Cisco ASA to send critical to emergency log messages to the syslog server as shown in the example below. ASA(config)# logging host NDM_INTERFACE 10.1.48.10 ASA(config)# logging trap critical ASA(config)# end Note: The parameter critical can replaced with a lesser severity (i.e., error, warning, notice, informational).

b

The Cisco ASA must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.

AU-8 - Medium - CCI-001893 - V-239924 - SV-239924r877987_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001893

Version

CASA-ND-000940

Vuln IDs

V-239924

Rule IDs

SV-239924r877987_rule

The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions. Multiple time sources provide redundancy by including a secondary source. Time synchronization is usually a hierarchy; clients synchronize time to a local source while that source synchronizes its time to a more accurate source. The network device must utilize an authoritative time server and/or be configured to use redundant authoritative time sources. This requirement is related to the comparison done in CCI-001891. DoD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DoD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source.

Checks: C-43157r666133_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement as shown in the configuration example below. ntp server 10.1.22.2 ntp server 10.1.48.8 prefer Note: For ASAs running on Firepower Chassis hardware, the NTP settings are visible in the FXOS web UI only (not in the ASA CLI or ASDM web UI). If the Cisco ASA is not configured to synchronize its clock with redundant authoritative time sources, this is a finding.

Fix: F-43116r666134_fix

Configure the Cisco ASA to synchronize its clock with redundant authoritative time sources as shown in the example below. ASA(config)# ntp server 10.1.48.8 prefer ASA(config)# ntp server 10.1.22.2 ASA(config)# end

b

The Cisco ASA must be configured to record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.

AU-8 - Medium - CCI-001889 - V-239925 - SV-239925r851029_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001889

Version

CASA-ND-000970

Vuln IDs

V-239925

Rule IDs

SV-239925r851029_rule

Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks.

Checks: C-43158r666136_chk

Verify the ASA is configured to include the time on all log records as shown in the configuration example below. logging timestamp If time stamp is not configured, this is a finding.

Fix: F-43117r666137_fix

Configure the ASA to include the time on all log records as shown in the example below. ASA(config)# logging timestamp

b

The Cisco ASA must be configured to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).

AU-8 - Medium - CCI-001890 - V-239926 - SV-239926r851031_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001890

Version

CASA-ND-000980

Vuln IDs

V-239926

Rule IDs

SV-239926r851031_rule

If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in UTC, a modern continuation of GMT, or local time with an offset from UTC.

Checks: C-43159r851030_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement as shown in the example below. clock timezone EST -5 0 Note: UTC is the default; hence, the command set time zone may not be seen in the configuration. This can be verified using the show clock command. For ASAs running on Firepower Chassis hardware, the NTP settings are visible in the FXOS web UI only (not in the ASA CLI or ASDM web UI). If the configuration is not compliant, this is a finding.

Fix: F-43118r666140_fix

Configure the Cisco ASA to record time stamps for audit records that can be mapped to UTC or GMT as shown in the example below. ASA(config)# clock timezone EST -5 0

b

The Cisco ASA must be configured to authenticate Simple Network Management Protocol (SNMP) messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).

IA-3 - Medium - CCI-001967 - V-239927 - SV-239927r851032_rule

RMF Control

IA-3

Severity

M

CCI

CCI-001967

Version

CASA-ND-001050

Vuln IDs

V-239927

Rule IDs

SV-239927r851032_rule

Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.

Checks: C-43160r666142_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement as shown in the example below. snmp-server group NETOPS v3 priv snmp-server user FWADMIN NETOPS v3 engineID xxxxxxxxxxxx encrypted auth sha xxxxxxxxxxxxxxxx snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN If the Cisco ASA is not configured to authenticate SNMP messages using a FIPS-validated HMAC, this is a finding.

Fix: F-43119r666143_fix

Configure the Cisco ASA to authenticate SNMP messages as shown in the example below. ASA(config)# snmp-server group NETOPS v3 priv ASA(config)# snmp-server user FWADMIN NETOPS v3 auth sha xxxxxxxxxxxxxxx ASA(config)# snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN ASA(config)# end

b

The Cisco ASA must be configured to encrypt Simple Network Management Protocol (SNMP) messages using a FIPS 140-2 approved algorithm.

IA-3 - Medium - CCI-001967 - V-239928 - SV-239928r851033_rule

RMF Control

IA-3

Severity

M

CCI

CCI-001967

Version

CASA-ND-001070

Vuln IDs

V-239928

Rule IDs

SV-239928r851033_rule

Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.

Checks: C-43161r666145_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement as shown in the example below. snmp-server group NETOPS v3 priv snmp-server user FWADMIN NETOPS v3 engineID xxxxxxxxxxxx encrypted auth sha xxxxxxxxxxxx priv aes xxxxxxxxxxxx snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN If the Cisco ASA is not configured to encrypt SNMP messages using a FIPS 140-2 approved algorithm, this is a finding.

Fix: F-43120r666146_fix

Configure the Cisco ASA to encrypt SNMP messages using a FIPS 140-2 approved algorithm as shown in the example below. ASA(config)# snmp-server group NETOPS v3 priv ASA(config)# snmp-server user FWADMIN NETOPS v3 auth sha xxxxxxxxxx priv aes xxxxxxxxxx ASA(config)# snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN ASA(config)# end

b

The Cisco ASA must be configured to authenticate Network Time Protocol sources using authentication that is cryptographically based.

IA-3 - Medium - CCI-001967 - V-239929 - SV-239929r851034_rule

RMF Control

IA-3

Severity

M

CCI

CCI-001967

Version

CASA-ND-001080

Vuln IDs

V-239929

Rule IDs

SV-239929r851034_rule

If Network Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.

Checks: C-43162r666148_chk

Review the Cisco ASA configuration to verify that it is compliant with this requirement as shown in the configuration example below. ntp authentication-key 1 md5 ***** ntp authenticate ntp trusted-key 1 ntp server 10.1.12.2 key 1 prefer ntp server 10.1.48.10 key 1 Note: For ASAs running on Firepower Chassis hardware, the NTP settings are visible in the FXOS web UI only (not in the ASA CLI or ASDM web UI). If the Cisco ASA is not configured to authenticate NTP sources using authentication that is cryptographically based, this is a finding.

Fix: F-43121r666149_fix

Configure the Cisco ASA to authenticate NTP sources using authentication that is cryptographically based as shown in the example below. ASA(config)# ntp authenticate ASA(config)# ntp authentication-key 1 md5 xxxxxxxxxx ASA(config)# ntp trusted-key 1 ASA(config)# ntp server 10.1.12.2 key 1 prefer ASA(config)# ntp server 10.1.48.10 key 1 ASA(config)# end

c

The Cisco ASA must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of non-local maintenance and diagnostic communications.

MA-4 - High - CCI-002890 - V-239930 - SV-239930r851035_rule

RMF Control

MA-4

Severity

H

CCI

CCI-002890

Version

CASA-ND-001140

Vuln IDs

V-239930

Rule IDs

SV-239930r851035_rule

Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised. Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Currently, HMAC is the only FIPS-approved algorithm for generating and verifying message/data authentication codes in accordance with FIPS 198-1. Products that are FIPS 140-2 validated will have an HMAC that meets specification; however, the option must be configured for use as the only message authentication code used for authentication to cryptographic modules. Separate requirements for configuring applications and protocols used by each application (e.g., SNMPv3, SSHv2, NTP, HTTPS, and other protocols and applications that require server/client authentication) are required to implement this requirement. Where SSH is used, the SSHv2 protocol suite is required because it includes Layer 7 protocols such as SCP and SFTP, which can be used for secure file transfers.

Checks: C-43163r666151_chk

SSH Example Step 1: Verify that FIPS mode is enabled as shown in the example below. fips enable Step 2: Verify that SSH is configured to only use FIPS-compliant ciphers and that Diffie-Hellman Group 14 is used for the key exchange as shown in the example below. ssh version 2 ssh cipher encryption fips ssh key-exchange group dh-group14-sha1 Note: The ASA only supports SSHv2. SNMP Example snmp-server group NETOPS v3 auth snmp-server user FWADMIN NETOPS v3 engineID xxxxxxxxxxxx encrypted auth sha xxxxxxxxxxxxxxxx snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN If the ASA is not configured to implement cryptographic mechanisms to protect the integrity of remote maintenance sessions using a FIPS 140-2 approved algorithm, this is a finding.

Fix: F-43122r666152_fix

SSH Example Step 1: Enable FIPS mode via the fips enable command. Step 2: Configure SSH to only use FIPS-compliant ciphers and Diffie-Hellman Group 14 for the key exchange. ASA(config)# ssh cipher encryption fips ASA(config)# ssh key-exchange group dh-group14-sha SNMP Example ASA(config)# snmp-server group NETOPS v3 auth ASA(config)# snmp-server user FWADMIN NETOPS v3 auth sha xxxxxxxxxxxxxxx ASA(config)# snmp-server host NDM_INTERFACE 10.1.48.10 version 3 FWADMIN ASA(config)# end

c

The Cisco ASA must be configured to implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions.

MA-4 - High - CCI-003123 - V-239931 - SV-239931r851036_rule

RMF Control

MA-4

Severity

H

CCI

CCI-003123

Version

CASA-ND-001150

Vuln IDs

V-239931

Rule IDs

SV-239931r851036_rule

This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents of those sessions will be susceptible to eavesdropping, potentially putting sensitive data (including administrator passwords) at risk of compromise and potentially allowing hijacking of maintenance sessions.

Checks: C-43164r666154_chk

Step 1: Verify FIPS mode is enabled as shown in the example below. fips enable Step 2: Verify that only SSH is configured to only use FIPS-compliant ciphers and that Diffie-Hellman Group 14 is used for the key exchange as shown in the example below. ssh version 2 ssh cipher encryption fips ssh key-exchange group dh-group14-sha1 Note: The ASA only supports SSHv2. If the ASA is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm, this is a finding.

Fix: F-43123r666155_fix

Step 1: Enable FIPS mode via the fips enable command. Step 2: Configure SSH to only use FIPS-compliant ciphers and Diffie-Hellman Group 14 for the key exchange. ASA(config)# ssh cipher encryption fips ASA(config)# ssh key-exchange group dh-group14-sha

b

The Cisco ASA must be configured to protect against known types of Denial of Service (DoS) attacks by enabling the Threat Detection feature.

SC-5 - Medium - CCI-002385 - V-239932 - SV-239932r851037_rule

RMF Control

SC-5

Severity

M

CCI

CCI-002385

Version

CASA-ND-001180

Vuln IDs

V-239932

Rule IDs

SV-239932r851037_rule

DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. The security safeguards cannot be defined at the DoD level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (for example, firewalls performing packet filtering to block DoS attacks).

Checks: C-43165r666157_chk

Review the ASA configuration and verify the Threat Detection feature is enabled as shown in the example below. threat-detection basic-threat If the Cisco ASA does not have the Threat Detection feature enabled, this is a finding.

Fix: F-43124r666158_fix

Configure the Cisco ASA to protect against known types of DoS attacks by enabling the Threat Detection feature. ASA(config)# threat-detection basic-threat ASA(config)# end

b

The Cisco ASA must be configured to generate audit records when successful/unsuccessful attempts to modify administrator privileges occur.

AU-12 - Medium - CCI-000172 - V-239933 - SV-239933r666162_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001200

Vuln IDs

V-239933

Rule IDs

SV-239933r666162_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43166r666160_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If the Cisco ASA is not configured to generate log records when administrator privileges are modified, this is a finding.

Fix: F-43125r666161_fix

Configure the Cisco ASA to generate log records when account privileges are modified as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records when successful/unsuccessful attempts to delete administrator privileges occur.

AU-12 - Medium - CCI-000172 - V-239934 - SV-239934r666165_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001210

Vuln IDs

V-239934

Rule IDs

SV-239934r666165_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43167r666163_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If the Cisco ASA is not configured to generate log records when administrator privileges are deleted, this is a finding.

Fix: F-43126r666164_fix

Configure the Cisco ASA to generate log records when administrator privileges are deleted as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records when successful/unsuccessful logon attempts occur.

AU-12 - Medium - CCI-000172 - V-239935 - SV-239935r666168_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001220

Vuln IDs

V-239935

Rule IDs

SV-239935r666168_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43168r666166_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log all login attempts. If the Cisco ASA is not configured to generate audit records when successful/unsuccessful attempts to logon, this is a finding.

Fix: F-43127r666167_fix

Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records for privileged activities or other system-level access.

AU-12 - Medium - CCI-000172 - V-239936 - SV-239936r666171_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001230

Vuln IDs

V-239936

Rule IDs

SV-239936r666171_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43169r666169_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log all EXEC-mode commands. If the Cisco ASA is not configured to generate log records for privileged activities, this is a finding.

Fix: F-43128r666170_fix

Configure the Cisco ASA to generate log records for privileged activities as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records showing starting and ending time for administrator access to the system.

AU-12 - Medium - CCI-000172 - V-239937 - SV-239937r666174_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001240

Vuln IDs

V-239937

Rule IDs

SV-239937r666174_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43170r666172_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging timestamp logging buffered informational Note: The ASA will log all login attempts as well as log the administrator’s name and time executing the enable command. The ASA will also log the time when the administrator logs out. If the Cisco ASA is not configured to generate log records showing starting and ending time for administrator access to the system, this is a finding.

Fix: F-43129r666173_fix

Configure the ASA to log session start and ending per admin session as shown in the example below. ASA(config)# logging enable ASA(config)# logging timestamp ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to generate audit records when concurrent logons from different workstations occur.

AU-12 - Medium - CCI-000172 - V-239938 - SV-239938r666177_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

CASA-ND-001250

Vuln IDs

V-239938

Rule IDs

SV-239938r666177_rule

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Checks: C-43171r666175_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The configuration should look similar to the example below. logging enable logging buffered informational Note: The ASA will log all login attempts including the IP address of the workstation. If the Cisco ASA is not configured to generate log records when concurrent logons from different workstations occur, this is a finding.

Fix: F-43130r666176_fix

Configure the Cisco ASA to log all logon attempts as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end

b

The Cisco ASA must be configured to offload audit records onto a different system or media than the system being audited.

AU-4 - Medium - CCI-001851 - V-239939 - SV-239939r851038_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

CASA-ND-001260

Vuln IDs

V-239939

Rule IDs

SV-239939r851038_rule

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Offloading is a common process in information systems with limited audit storage capacity.

Checks: C-43172r666178_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement as shown in the example below. logging trap notifications logging host NDM_INTERFACE 10.1.48.10 6/1514 Note: A logging list can be used as an alternative to the severity level. If the Cisco ASA is not configured to offload log records onto a different system than the system being audited, this is a finding.

Fix: F-43131r666179_fix

Configure the Cisco ASA to send log records to a syslog server as shown in the example below. ASA(config)# logging host NDM_INTERFACE 10.1.48.10 6/1514 ASA(config)# logging trap notifications ASA(config)# end

c

The Cisco ASA must be configured to use an authentication server to authenticate users prior to granting administrative access.

CM-6 - High - CCI-000370 - V-239940 - SV-239940r877988_rule

RMF Control

CM-6

Severity

H

CCI

CCI-000370

Version

CASA-ND-001310

Vuln IDs

V-239940

Rule IDs

SV-239940r877988_rule

Centralized management of authentication settings increases the security of remote and non-local access methods. This control is particularly important protection against the insider threat. With robust centralized management, audit records for administrator account access to the organization's network devices can be more readily analyzed for trends and anomalies. The alternative method of defining administrator accounts on each device exposes the device configuration to remote access authentication attacks and system administrators with multiple authenticators for each network device.

Checks: C-43173r666181_chk

Review the Cisco ASA configuration to verify the device is configured to use an authentication server as primary source for authentication. Step 1: Verify that an AAA group is configured for login authentication for both in-band and console access methods. aaa authentication serial console RADIUS_GROUP LOCAL aaa authentication ssh console RADIUS_GROUP LOCAL Step 2: Verify that an AAA group and server has been defined for the group referenced in the above example. aaa-server RADIUS_GROUP protocol radius aaa-server RADIUS_GROUP (NDM_INTERFACE) host 10.1.48.10 key ***** If the Cisco ASA is not configured to use an authentication server for the purpose of authenticating users prior to granting administrative access, this is a finding.

Fix: F-43132r666182_fix

Configure the Cisco ASA to use an authentication server as shown in the following example. Step 1: Define the authentication group and protocol. ASA(config)# aaa-server RADIUS_GROUP protocol radius Step 2: Define the authentication server. ASA(config)# aaa-server RADIUS_GROUP (NDM_INTERFACE) host 10.1.48.10 ASA(config-aaa-server-host)# key bobby ASA(config-aaa-server-host)# exit Step 3: Use the AAA server for login authentication for both in-band and console access methods. ASA(config)# aaa authentication serial console RADIUS_GROUP LOCAL ASA(config)# aaa authentication ssh console RADIUS_GROUP LOCAL ASA(config)# end

b

The Cisco ASA must be configured to conduct backups of system-level information contained in the information system when changes occur.

CP-9 - Medium - CCI-000537 - V-239941 - SV-239941r877989_rule

RMF Control

CP-9

Severity

M

CCI

CCI-000537

Version

CASA-ND-001350

Vuln IDs

V-239941

Rule IDs

SV-239941r877989_rule

System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the execution and operation of the device. Information system backup is a critical step in ensuring system integrity and availability. If the system fails and there is no backup of the system-level information, a denial of service condition is possible for all who utilize this critical network component. This control requires the network device to support the organizational central backup process for system-level information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups.

Checks: C-43174r666184_chk

Review the Cisco ASA configuration to verify it is compliant with this requirement. The example configuration below will send the configuration to an SCP server when a configuration change occurs. event manager applet BACKUP_CONFIG event syslog pattern "SYSLOG_CONFIG_I" action 1 cli command "copy startup-config scp://userx:xxxxxxx@10.1.48.10//opt/config_backup" action 2 syslog priority informational msg "Configuration backup was executed" Note: Tools such as Cisco Security Manager, Cisco Prime Infrastructure, Firemon, or Tripwire can be used to back up the configuration. If the Cisco ASA is not configured to conduct backups of the configuration when changes occur, this is a finding.

Fix: F-43133r666185_fix

Configure the Cisco ASA to send the configuration to an SCP server when a configuration change occurs as shown in the example below. ASA(config)# event manager applet BACKUP_CONFIG ASA(config-applet)# event syslog pattern "SYSLOG_CONFIG_I" ASA(config-applet)# action 1 cli command " copy startup-config scp://userx:xxxxxxx@10.1.48.10//opt/config_backup” ASA(config-applet)# action 2 syslog priority informational msg "Configuration backup was executed" ASA(config-applet)# end

b

The Cisco ASA must be configured to obtain its public key certificates from an appropriate certificate policy through an approved service provider.

SC-17 - Medium - CCI-001159 - V-239942 - SV-239942r877990_rule

RMF Control

SC-17

Severity

M

CCI

CCI-001159

Version

CASA-ND-001370

Vuln IDs

V-239942

Rule IDs

SV-239942r877990_rule

For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice.

Checks: C-43175r666187_chk

If PKI certificates are not implemented on the ASA, this requirement is not applicable. Step 1: Review the ASA configuration to determine if a CA trust point has been configured as shown in the example below. Step 2: Verify the CA is a DoD or DoD-approved service provider by entering the following command. show crypto ca certificates The output will list the following information for each certificate: Associated Trustpoints: (will map to a configured trustpoint from Step 1) Common Name (CN) of the issuer Organization Unit (OU) of the issuer Organization (O) of the issuer Validity Date If the ASA is not configured to obtain its public key certificates from a DoD or DoD-approved service provider, this is a finding.

Fix: F-43134r666188_fix

Ensure certificate requests are only sent to DoD or DoD-approved service providers.

c

The Cisco ASA must be configured to send log data to a central log server for the purpose of forwarding alerts to organization-defined personnel and/or the firewall administrator.

AU-4 - High - CCI-001851 - V-239943 - SV-239943r863234_rule

RMF Control

AU-4

Severity

H

CCI

CCI-001851

Version

CASA-ND-001410

Vuln IDs

V-239943

Rule IDs

SV-239943r863234_rule

The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, are important in showing whether someone is an internal employee or an outside threat. The ISSM or ISSO may designate the firewall/system administrator or other authorized personnel to receive the alert within the specified time, validate the alert, and then forward only validated alerts to the ISSM and ISSO.

Checks: C-43176r666190_chk

Verify the ASA is configured to send logs to a syslog server. The configuration should look similar to the example below. logging trap notifications logging host NDM_INTERFACE 10.1.48.10 6/1514 Note: A logging list can be used as an alternative to the severity level. If the ASA is not configured to send log data to the syslog server, this is a finding.

Fix: F-43135r666191_fix

Configure the ASA to send log messages to the syslog server as shown in the example below. ASA(config)# logging host NDM_INTERFACE 10.1.48.10 6/1514 ASA(config)# logging trap notifications ASA(config)# end

c

The Cisco ASA must be running an operating system release that is currently supported by Cisco Systems.

SA-22 - High - CCI-003376 - V-239944 - SV-239944r877991_rule

RMF Control

SA-22

Severity

H

CCI

CCI-003376

Version

CASA-ND-001420

Vuln IDs

V-239944

Rule IDs

SV-239944r877991_rule

Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.

Checks: C-43177r666193_chk

Verify the ASA is in compliance with this requirement by having the ASA administrator enter the following command. show version Verify the release is still supported by Cisco. All releases supported by Cisco can be found at the following URL: https://www.cisco.com/c/en/us/products/security/asa-firepower-services/eos-eol-notice-listing.html If the ASA is not running a supported release, this is a finding.

Fix: F-43136r666194_fix

Upgrade the ASA to a supported release.

Content changes 1

Checks: C-43129r666049_chk

Fix: F-43088r666050_fix

Generate Mitigation Statement:

Checks: C-43130r666052_chk

Fix: F-43089r666053_fix

Generate Mitigation Statement:

Checks: C-43131r666055_chk

Fix: F-43090r666056_fix

Generate Mitigation Statement:

Checks: C-43132r666058_chk

Fix: F-43091r666059_fix

Generate Mitigation Statement:

Checks: C-43133r666061_chk

Fix: F-43092r666062_fix

Generate Mitigation Statement:

Checks: C-43134r666064_chk

Fix: F-43093r666065_fix

Generate Mitigation Statement:

Checks: C-43135r666067_chk

Fix: F-43094r666068_fix

Generate Mitigation Statement:

Checks: C-43136r666070_chk

Fix: F-43095r666071_fix

Generate Mitigation Statement:

Checks: C-43137r666073_chk

Fix: F-43096r666074_fix

Generate Mitigation Statement:

Checks: C-43138r666076_chk

Fix: F-43097r666077_fix

Generate Mitigation Statement:

Checks: C-43139r666079_chk

Fix: F-43098r666080_fix

Generate Mitigation Statement:

Checks: C-43140r666082_chk

Fix: F-43099r666083_fix

Generate Mitigation Statement:

Checks: C-43141r666085_chk

Fix: F-43100r666086_fix

Generate Mitigation Statement:

Checks: C-43142r666088_chk

Fix: F-43101r666089_fix

Generate Mitigation Statement:

Checks: C-43143r666091_chk

Fix: F-43102r666092_fix

Generate Mitigation Statement:

Checks: C-43144r666094_chk

Fix: F-43103r666095_fix

Generate Mitigation Statement:

Checks: C-43145r666097_chk

Fix: F-43104r666098_fix

Generate Mitigation Statement:

Checks: C-43146r666100_chk

Fix: F-43105r666101_fix

Generate Mitigation Statement:

Checks: C-43147r666103_chk

Fix: F-43106r666104_fix

Generate Mitigation Statement:

Checks: C-43148r666106_chk

Fix: F-43107r666107_fix

Generate Mitigation Statement:

Checks: C-43149r666109_chk

Fix: F-43108r666110_fix

Generate Mitigation Statement:

Checks: C-43150r666112_chk

Fix: F-43109r666113_fix

Generate Mitigation Statement:

Checks: C-43151r666115_chk

Fix: F-43110r666116_fix

Generate Mitigation Statement:

Checks: C-43152r666118_chk

Fix: F-43111r666119_fix

Generate Mitigation Statement:

Checks: C-43153r666121_chk

Fix: F-43112r666122_fix

Generate Mitigation Statement:

Checks: C-43154r666124_chk

Fix: F-43113r666125_fix

Generate Mitigation Statement:

Checks: C-43155r666127_chk