Central Log Server Security Requirements Guide V1R3

b

The Central Log Server must be configured to protect the data sent from hosts and devices from being altered in a way that may prevent the attribution of an action to an individual (or process acting on behalf of an individual).

AU-10 - Medium - CCI-000166 - V-81105 - SV-95819r1_rule

RMF Control

AU-10

Severity

M

CCI

CCI-000166

Version

SRG-APP-000080-AU-000010

Vuln IDs

V-81105

Rule IDs

SV-95819r1_rule

Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual). The records stored by the Central Log Server must be protected against such alteration as removing the identifier. A hash is one way of performing this function. The server must not allow the removal of identifiers or date/time, or it must severely restrict the ability to do so. Additionally, the log administrator access and activity with the user account information.

Checks: C-80759r1_chk

Examine the configuration. Verify the system is configured with a hash or other method that protects the data against alteration of the log information sent from hosts and devices. Verify the Central Log Server is configured to log all changes to the machine data. If the Central Log Server is not 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, this is a finding.

Fix: F-87877r1_fix

Configure the Central Log Server to use a hash or other method that protects the data against alteration of the log information sent from hosts and devices. Configure the Central Log Server to not allow alterations to the machine data.

a

The Central Log Server must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage.

AU-12 - Low - CCI-000174 - V-81107 - SV-95821r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-000174

Version

SRG-APP-000086-AU-000020

Vuln IDs

V-81107

Rule IDs

SV-95821r1_rule

If the application is not configured to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is significantly degraded. Centralized log aggregation must also include logs from databases and servers (e.g., Windows) that do not natively send logs using the syslog protocol.

Checks: C-80761r1_chk

Examine the documentation that lists the scope of coverage for the specific log server being reviewed. Verify the system is configured to aggregate log records from organization-defined devices and hosts within its scope of coverage. If the Central Log Server is not configured to aggregate log records from organization-defined devices and hosts within its scope of coverage, this is a finding.

Fix: F-87879r1_fix

For each log server, configure the server to aggregate log records from organization-defined devices and hosts within its scope of coverage.

a

Time stamps recorded on the log records in the Central Log Server must be configured to synchronize to within one second of the host server or, if NTP is configured directly in the log server, the NTP time source must be the same as the host and devices within its scope of coverage.

AU-12 - Low - CCI-000174 - V-81109 - SV-95823r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-000174

Version

SRG-APP-000086-AU-000030

Vuln IDs

V-81109

Rule IDs

SV-95823r1_rule

If the application is not configured to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is significantly degraded. If the SIEM or other Central Log Server is out of sync with the host and devices for which it stores event logs, this may impact the accuracy of the records stored. Log records are time correlated if the time stamps in the individual log records can be reliably related to the time stamps in other log records to achieve a time ordering of the records within an organization-defined level of tolerance. This requirement applies only to applications that compile system-wide log records for multiple systems or system components. Note: The actual configuration and security requirements for NTP is handled in the host OS or NDM STIGs that are also required as part of a Central Log Server review.

Checks: C-80763r1_chk

Examine the time stamp that indicates when the Central Log Server received the log records. Verify the time is synchronized to within one second of the host server. If an NTP client is configured within the Central Log Server application, verify it is configured to use the same NTP time source as the host and devices within its scope of coverage. If time stamps recorded on the log records in the Central Log Server are not configured to synchronize to within one second of the host server or the log server application is not configured to use the same NTP time source as the host and devices within its scope of coverage, this is a finding.

Fix: F-87881r1_fix

Configure the Central Log Server such that time stamps on the log records are synchronized to within one second of the host server. If applicable, configure the Central Log Server NTP client to use the same NTP time source as the host and devices within its scope of coverage.

b

Where multiple log servers are installed in the enclave, each log server must be configured to aggregate log records to a central aggregation server or other consolidated events repository.

AU-12 - Medium - CCI-000174 - V-81111 - SV-95825r1_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000174

Version

SRG-APP-000086-AU-000390

Vuln IDs

V-81111

Rule IDs

SV-95825r1_rule

Log servers (e.g., syslog servers) are often used on network segments to consolidate from the devices and hosts on that network segment. However, this does not achieve compliance with the DoD requirement for a centralized enclave log server. To comply with this requirement, create a central log server that aggregates multiple log servers or use another method to ensure log analysis and management is centrally managed and available to enterprise forensics and analysis tools. This server is often called a log aggregator, SIEM, or events server.

Checks: C-80765r1_chk

Examine the network architecture and documentation. If the log server being reviewed is one of multiple log servers in the enclave or on a network segment, verify that an aggregation server exists and that the log server under review is configured to send records received from the host and devices to the aggregation server or centralized SIEM/events sever. Where multiple log servers are installed in the enclave, if each log server is not configured to send log records to a central aggregation server or other consolidated events repository, this is a finding.

Fix: F-87883r1_fix

Where multiple log servers are installed in the enclave, configure each log server to forward logs to a consolidated aggregation server.

a

The Central Log Server log records must be configured to use the syslog protocol or another industry standard format (e.g., Windows event protocol) that can be used by typical analysis tools.

AU-12 - Low - CCI-001353 - V-81113 - SV-95827r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-001353

Version

SRG-APP-000088-AU-000040

Vuln IDs

V-81113

Rule IDs

SV-95827r1_rule

Without a standardized format for log records, the ability to perform forensic analysis may be more difficult. Standardization facilitates production of event information that can be more readily analyzed and correlated. Log information that is normalized to common standards promotes interoperability and exchange of such information between dissimilar devices and information systems. If logging mechanisms within applications that send records to the centralized audit system do not conform to standardized formats, the audit system may convert the records into a standardized format when compiling system-wide audit trails. Thus, although the application and other system components should send the information in a standardized format, ultimately the audit aggregation server is responsible for ensuring the records are compiled to meet this requirement.

Checks: C-80767r1_chk

Examine the configuration. Verify log records are configured to use the syslog protocol or another industry standard format (e.g., Windows event protocol) that can be used by a typical analysis tools. If the Central Log Server log records are not configured to use the syslog protocol or another industry standard format (e.g., Windows event protocol) that can be used by typical analysis tools, this is a finding.

Fix: F-87885r1_fix

Configure the Central Log Server log records to use the syslog protocol or another industry standard format (e.g., Windows event protocol) that can be used by typical analysis tools.

b

The Central Log Server must be configured to retain the DoD-defined attributes of the log records sent by the devices and hosts.

AU-12 - Medium - CCI-000169 - V-81115 - SV-95829r1_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000169

Version

SRG-APP-000089-AU-000400

Vuln IDs

V-81115

Rule IDs

SV-95829r1_rule

Log records can be generated from various components within the application (e.g., process, module). Certain specific application functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating log records. DoD has defined a list of information or attributes that must be included in the log record, including date, time, source, destination, module, severity level (category of information), etc. Other log record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.

Checks: C-80769r1_chk

Examine the configuration. Verify the Central Log Server retains the DoD-defined attributes of the log records sent by the devices and hosts. If the Central Log Server is not configured to retain the DoD-defined attributes of the log records sent by the devices and hosts, this is a finding.

Fix: F-87887r1_fix

Configure the Central Log Server to retain the DoD-defined attributes of the log records sent by the devices and hosts.

a

The Central Log Server must be configured to allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be retained.

AU-12 - Low - CCI-000171 - V-81117 - SV-95831r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-000171

Version

SRG-APP-000090-AU-000070

Vuln IDs

V-81117

Rule IDs

SV-95831r1_rule

Without restricting which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating log records.

Checks: C-80771r1_chk

Examine the configuration. Verify the system is configured to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be retained. If the Central Log Server is not configured to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be retained, this is a finding.

Fix: F-87889r1_fix

Configure the Central Log Server to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be retained.

a

The Central Log Server must be configured to perform analysis of log records across multiple devices and hosts in the enclave that can be reviewed by authorized individuals.

AU-6 - Low - CCI-000154 - V-81119 - SV-95833r1_rule

RMF Control

AU-6

Severity

L

CCI

CCI-000154

Version

SRG-APP-000111-AU-000150

Vuln IDs

V-81119

Rule IDs

SV-95833r1_rule

Successful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If the application does not provide the ability to centrally review the application logs, forensic analysis is negatively impacted. Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and event notification difficult to implement and manage, particularly when the system or application has multiple logging components written to different locations or systems. Automated mechanisms for centralized reviews and analyses include, for example, Security Information and Event Management (SIEM) products.

Checks: C-80775r1_chk

Examine the configuration. Verify the system is configured to perform analysis of log records across multiple devices and hosts in the enclave that can be reviewed by authorized individuals. If the Central Log Server is not configured to perform analysis of log records across multiple devices and hosts in the enclave that can be reviewed by authorized individuals, this is a finding.

Fix: F-87891r1_fix

Configure the Central Log Server to perform analysis of log records across multiple devices and hosts in the enclave that can be reviewed by authorized individuals.

a

The Central Log Server must be configured to perform on-demand filtering of the log records for events of interest based on organization-defined criteria.

AU-7 - Low - CCI-000158 - V-81121 - SV-95835r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-000158

Version

SRG-APP-000115-AU-000160

Vuln IDs

V-81121

Rule IDs

SV-95835r1_rule

The ability to specify the event criteria that are of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded. Events of interest can be identified by the content of specific log record fields including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required; for example, locations selectable by general networking location (e.g., by network or subnetwork) or by specific information system component. This requires applications to be configured to customize log record reports based on organization-defined criteria. Summary reports provide oversight for security devices, helping to identify when a device is not detecting or blocking to the extent one would expect. A simple “top 10” list of what was detected and blocked, with a count by severity, can help prioritize security responses. Operational reports detailing the source hosts for any given malware can then direct remediation responses.

Checks: C-80777r1_chk

Examine the configuration. Verify the system is configured to perform on-demand filtering of the log records for events of interest based on organization-defined criteria. If the Central Log Server is not configured to perform on-demand filtering of the log records for events of interest based on organization-defined criteria, this is a finding.

Fix: F-87893r1_fix

Configure the Central Log Server to perform on-demand filtering of the log records for events of interest based on organization-defined criteria.

a

The Central Log Server must be configured to use internal system clocks to generate time stamps for log records.

AU-8 - Low - CCI-000159 - V-81123 - SV-95837r1_rule

RMF Control

AU-8

Severity

L

CCI

CCI-000159

Version

SRG-APP-000116-AU-000270

Vuln IDs

V-81123

Rule IDs

SV-95837r1_rule

Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. If the internal clock is not used, the system may not be able to provide time stamps for log messages. Additionally, externally generated time stamps may not be accurate. Applications can use the capability of an operating system or purpose-built module for this purpose.

Checks: C-80779r1_chk

Examine the configuration. Verify the Central Log Server uses internal system clocks to generate time stamps for log records. If the Central Log Server is not configured to use internal system clocks to generate time stamps for log records, this is a finding.

Fix: F-87895r1_fix

Configure the Central Log Server to use internal system clocks to generate time stamps for log records.

a

The Central Log Server must be configured to back up the log records repository at least every seven days onto a different system or system component other than the system or component being audited.

AU-9 - Low - CCI-001348 - V-81125 - SV-95839r1_rule

RMF Control

AU-9

Severity

L

CCI

CCI-001348

Version

SRG-APP-000125-AU-000300

Vuln IDs

V-81125

Rule IDs

SV-95839r1_rule

Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up log records to a different system or onto separate media than the system being audited on an organizationally defined frequency helps to ensure that in the event of a catastrophic system failure, the log records will be retained. This helps to ensure that a compromise of the information system being audited does not also result in a compromise of the log records. This requirement only applies to applications that have a native backup capability for log records. Operating system backup requirements cover applications that do not provide native backup functions.

Checks: C-80783r1_chk

Examine the configuration. Verify the Central Log Server log records repository is backed up at least every seven days onto a different system or system component other than the system or component being audited. If the Central Log Server is not configured to back up the log records repository at least every seven days onto a different system or system component other than the system or component being audited, this is a finding.

Fix: F-87899r1_fix

Configure the Central Log Server to back up the log records repository at least every seven days onto a different system or system component other than the system or component being audited.

a

The Central Log Server system backups must be stored on media capable of guaranteeing file integrity for a minimum of five years.

AU-9 - Low - CCI-001348 - V-81127 - SV-95841r1_rule

RMF Control

AU-9

Severity

L

CCI

CCI-001348

Version

SRG-APP-000125-AU-000310

Vuln IDs

V-81127

Rule IDs

SV-95841r1_rule

If backups are not properly processed, protected, and stored on appropriate media, recovery from a system failure or implementation of a contingency plan would not include the data necessary to fully recover in the time required to ensure continued mission support.

Checks: C-80785r1_chk

Examine the configuration. Verify the Central Log Server system is backed up to media capable of guaranteeing file integrity for a minimum of five years. If the Central Log Server system backups are not stored on appropriate media capable of guaranteeing file integrity for a minimum of five years, this is a finding.

Fix: F-87901r1_fix

Configure the Central Log Server system to back up to media capable of guaranteeing file integrity for a minimum of five years.

b

The Central Log Server must be configured to perform audit reduction that supports on-demand reporting requirements.

AU-7 - Medium - CCI-001876 - V-81129 - SV-95843r1_rule

RMF Control

AU-7

Severity

M

CCI

CCI-001876

Version

SRG-APP-000181-AU-000200

Vuln IDs

V-81129

Rule IDs

SV-95843r1_rule

The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports. This requirement is specific to applications with audit reduction capabilities; however, applications need to support on-demand audit review and analysis.

Checks: C-80787r1_chk

Examine the configuration. Verify the system is configured to perform audit reduction that supports on-demand reporting requirements. If the Central Log Server is not configured to perform audit reduction that supports on-demand reporting requirements, this is a finding.

Fix: F-87903r1_fix

Configure the Central Log Server to perform audit reduction that supports on-demand reporting requirements.

a

For devices and hosts within its scope of coverage, the Central Log Server must be configured to notify the System Administrator (SA) and Information System Security Officer (ISSO) when account modification events are received.

AC-2 - Low - CCI-001684 - V-81131 - SV-95845r1_rule

RMF Control

AC-2

Severity

L

CCI

CCI-001684

Version

SRG-APP-000292-AU-000420

Vuln IDs

V-81131

Rule IDs

SV-95845r1_rule

When application accounts are modified, user accessibility is affected. Accounts are used for identifying individual users or for identifying the application processes themselves. Sending notification of account modification events to the SA and ISSO is one method for mitigating this risk. Such a function greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. Notification may be configured to be sent by the device, SNMP server, or the Central Log Server. The best practice is for these notifications to be sent by a robust events management server.

Checks: C-80789r1_chk

Note: This is not applicable (NA) if notifications are performed by another device. Examine the configuration. Verify the Central Log Server is configured to notify the SA and ISSO when account modification events are received for all devices and hosts within its scope of coverage. If the Central Log Server is not configured to notify the SA and ISSO when account modification events are received for all devices and hosts within its scope of coverage, this is a finding.

Fix: F-87905r1_fix

Configure the Central Log Server to notify the SA and ISSO when account modification events are received for all devices and hosts within its scope of coverage.

a

For devices and hosts within its scope of coverage, the Central Log Server must notify the System Administrator (SA) and Information System Security Officer (ISSO) when events indicating account disabling actions are received.

AC-2 - Low - CCI-001685 - V-81133 - SV-95847r1_rule

RMF Control

AC-2

Severity

L

CCI

CCI-001685

Version

SRG-APP-000293-AU-000430

Vuln IDs

V-81133

Rule IDs

SV-95847r1_rule

When application accounts are disabled, user accessibility is affected. Accounts are used for identifying individual users or for identifying the application processes themselves. Sending notification of account disabling events to the SA and ISSO is one method for mitigating this risk. Such a function greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. Notification may be configured to be sent by the device, SNMP server, or Central Log Server. The best practice is for these notifications to be sent by a robust events management server.

Checks: C-80791r1_chk

Note: This is not applicable (NA) if notifications are performed by another device. Examine the configuration. Verify the Central Log Server is configured to notify the SA and ISSO when events indicating account disabling actions are received for all devices and hosts within its scope of coverage. If the Central Log Server does not notify the SA and ISSO when events indicating account disabling actions are received, this is a finding.

Fix: F-87907r1_fix

Configure the Central Log Server to notify the SA and ISSO when events indicating account disabling actions are received for all devices and hosts within its scope of coverage.

a

For devices and hosts within its scope of coverage, the Central Log Server must notify the System Administrator (SA) and Information System Security Officer (ISSO) when events indicating account removal actions are received.

AC-2 - Low - CCI-001686 - V-81135 - SV-95849r1_rule

RMF Control

AC-2

Severity

L

CCI

CCI-001686

Version

SRG-APP-000294-AU-000440

Vuln IDs

V-81135

Rule IDs

SV-95849r1_rule

When application accounts are removed, user accessibility is affected. Accounts are used for identifying users or for identifying the application processes themselves. Sending notification of account removal events to the SA and ISSO is one method for mitigating this risk. Such a function greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. Notification may be configured to be sent by the device, SNMP server, or Central Log Server. The best practice is for these notifications to be sent by a robust events management server.

Checks: C-80793r1_chk

Note: This is not applicable (NA) if notifications are performed by another device. Examine the configuration. Verify the Central Log Server is configured to notify the SA and ISSO when events indicating account removal actions are received for all devices and hosts within its scope of coverage. If the Central Log Server does not notify the SA and ISSO when events indicating account removal actions are received, this is a finding.

Fix: F-87909r1_fix

Configure the Central Log Server to notify the SA and ISSO when events indicating account removal actions are received for all devices and hosts within its scope of coverage.

a

The System Administrator (SA) and Information System Security Manager (ISSM) must configure the retention of the log records based on criticality level, event type, and/or retention period, at a minimum.

AU-12 - Low - CCI-001914 - V-81137 - SV-95851r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-001914

Version

SRG-APP-000353-AU-000050

Vuln IDs

V-81137

Rule IDs

SV-95851r1_rule

If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to respond effectively and important forensic information may be lost. The organization must define and document log retention requirements for each device and host and then configure the Central Log Sever to comply with the required retention period. This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed; for example, in near real time, within minutes, or within hours.

Checks: C-80795r1_chk

Examine the configuration. Verify the SA and ISSM have been assigned the privileges needed to allow these roles to change the level and type of log records that are retained in the centralized repository based on any selectable event criteria. Verify the retention configuration for each host and device is in compliance with the documented organization criteria, including the identified criticality level, event type, and/or retention period. If the Central Log Server is not configured to allow the SA and ISSM to change the retention of the log records, this is a finding. If the retention is not in compliance with the organization’s documentation, this is a finding.

Fix: F-87911r1_fix

Configure the Central Log Server with the privileges needed to allow the SA and ISSM to change the level and type of log records that are retained in the centralized repository based on any selectable event criteria. Based on the documented requirements for each application, configure the events server to retain log records based on criticality level, type of event, and/or retention period, at a minimum.

a

The Central Log Server must be configured so changes made to the level and type of log records stored in the centralized repository must take effect immediately without the need to reboot or restart the application.

AU-12 - Low - CCI-001914 - V-81139 - SV-95853r1_rule

RMF Control

AU-12

Severity

L

CCI

CCI-001914

Version

SRG-APP-000353-AU-000060

Vuln IDs

V-81139

Rule IDs

SV-95853r1_rule

If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to respond effectively and important forensic information may be lost. This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. Organizations can establish time thresholds in which audit actions are changed; for example, in near real time, within minutes, or within hours.

Checks: C-80799r1_chk

Examine the configuration. Verify the system is configured so changes made to the level and type of log records stored in the centralized repository take effect immediately without the need to reboot or restart the application. If the Central Log Server is not configured so changes made to the level and type of log records stored in the centralized repository must take effect immediately without the need to reboot or restart the application, this is a finding.

Fix: F-87913r1_fix

Configure the Central Log Server so changes made to the level and type of log records stored in the centralized repository must take effect immediately without the need to reboot or restart the application.

a

The Central Log Server must be configured to allow selection, capture, and view of all events related to a user session, host, or device when required by authorized users.

AU-14 - Low - CCI-001919 - V-81141 - SV-95855r1_rule

RMF Control

AU-14

Severity

L

CCI

CCI-001919

Version

SRG-APP-000354-AU-000080

Vuln IDs

V-81141

Rule IDs

SV-95855r1_rule

If the system is not configured to select a user session to capture and view or produce a report, investigations into suspicious or harmful events would be hampered by the volume of information captured. The volume of information captured may also adversely impact the operation for the network. This only includes auditable events. The Central Log Server (i.e., SIEM, syslog server) should be able to correlate across multiple devices and hosts within its span of control to provide an aggregated view of the single user's activity.

Checks: C-80801r1_chk

Examine the configuration. Verify the system is configured to allow selection, capture, and view of all events related to a user session, host, or device when required by authorized users. If the Central Log Server is not configured to allow selection, capture, and view of all events related to a user session, host, or device when required by authorized users, this is a finding.

Fix: F-87915r1_fix

Configure the Central Log Server to allow selection, capture, and view of all events related to a user session, host, or device when required by authorized users.

a

The Central Log Server must be configured for centralized management of the events repository for the purposes of configuration, analysis, and reporting.

AU-3 - Low - CCI-001844 - V-81143 - SV-95857r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-001844

Version

SRG-APP-000356-AU-000090

Vuln IDs

V-81143

Rule IDs

SV-95857r1_rule

If the application is not configured to centrally manage the content captured in the log records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The content captured in log records must be managed from a central location (necessitating automation). Centralized management of log records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. Application components requiring centralized audit log management must be configured to support centralized management.

Checks: C-80803r1_chk

Examine the configuration. Verify that centralized management of the events repository is enabled and configured for all hosts and devices within the scope of coverage. If the Central Log Server is not enabled to allow centralized management of the events repository for the purposes of configuration, analysis, and reporting, this is a finding.

Fix: F-87917r1_fix

Configure access for management tools used by administrators at management workstations, particularly those used for remote access. This often uses user access profiles or remote access configuration to enable secure and authorized access to the Central Log Server. Enable management from one or more management workstations or a secure browser. Verify remote communications from the management station using a secure, approved version of the protocol (e.g., TLS). Limit access based on user role, location, or remote device wherever possible.

b

The Central Log Server must be configured to off-load log records onto a different system or media than the system being audited.

AU-4 - Medium - CCI-001851 - V-81145 - SV-95859r1_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

SRG-APP-000358-AU-000100

Vuln IDs

V-81145

Rule IDs

SV-95859r1_rule

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Although this may be part of the operating system function, for the enterprise events management system, this is most often a function managed through the application since it is a critical function and requires the use of a large amount of external storage.

Checks: C-80807r1_chk

Note: This is not applicable (NA) if an external application or operating system manages this function. Examine the configuration. Verify the system is configured to off-load log records onto a different system or media than the system being audited. If the Central Log Server is not configured to off-load log records onto a different system or media than the system being audited, this is a finding.

Fix: F-87921r1_fix

Configure the Central Log Server to off-load log records onto a different system or media than the system being audited.

a

The Central Log Server must be configured to send an immediate alert to the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated log record storage volume reaches 75 percent of the repository maximum log record storage capacity.

AU-5 - Low - CCI-001855 - V-81147 - SV-95861r1_rule

RMF Control

AU-5

Severity

L

CCI

CCI-001855

Version

SRG-APP-000359-AU-000120

Vuln IDs

V-81147

Rule IDs

SV-95861r1_rule

If security personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion. Although this may be part of the operating system function, for the enterprise events management system, this is most often a function managed through the application since it is a critical function and requires the use of a large amount of external storage.

Checks: C-80809r1_chk

Note: This is not applicable (NA) if an external application or operating system manages this function. Examine the configuration. Verify the system is configured to send an immediate warning to the SA and ISSO (at a minimum) when allocated log record storage volume reaches 75 percent of the repository's maximum log record storage capacity. If the Central Log Server is not configured to send an immediate alert to the SA and ISSO (at a minimum) when allocated log record storage volume reaches 75 percent of repository maximum log record storage capacity, this is a finding.

Fix: F-87923r1_fix

Configure the Central Log Server to send an immediate alert to the SA, ISSO, and other authorized personnel when allocated log record storage volume reaches 75 percent of repository maximum log record storage capacity.

a

For the host and devices within its scope of coverage, the Central Log Server must be configured to send a real-time alert to the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) of all audit failure events, such as loss of communications with hosts and devices, or if log records are no longer being received.

AU-5 - Low - CCI-001858 - V-81149 - SV-95863r1_rule

RMF Control

AU-5

Severity

L

CCI

CCI-001858

Version

SRG-APP-000360-AU-000130

Vuln IDs

V-81149

Rule IDs

SV-95863r1_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 function and application 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). User-configurable controls on the Central Log Server help avoid generating excessive numbers of alert messages. Define realistic alerting limits and thresholds to avoid creating excessive numbers of alerts for noncritical events. This requirement must be mapped to the severity levels used by the system to denote a failure, active attack, attack involving multiple systems, and other critical notifications, at a minimum. However, note that the IDS/IDPS and other monitoring systems may already be configured for direct notification of many types of critical security alerts.

Checks: C-80811r1_chk

Examine the configuration. Verify the system is configured to send an alert to the SA and ISSO, within seconds or less, when communication is lost with any host or device within the scope of coverage that may indicate an audit failure. Verify the system is configured to send an alert if hosts and devices stop sending log records to the Central Log Server. If the Central Log Server is not configured to send a real-time alert to the SA and ISSO (at a minimum) of all audit failure events, this is a finding.

Fix: F-87925r1_fix

For the host and devices within its scope of coverage, configure the Central Log Server to send an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events such as loss of communications with hosts and devices, or if log records are no longer being received.

a

The Central Log Server must be configured to send an immediate alert to the System Administrator (SA) or Information System Security Officer (ISSO) if communication with the host and devices within its scope of coverage is lost.

AU-5 - Low - CCI-001861 - V-81151 - SV-95865r1_rule

RMF Control

AU-5

Severity

L

CCI

CCI-001861

Version

SRG-APP-000361-AU-000140

Vuln IDs

V-81151

Rule IDs

SV-95865r1_rule

If the system were to continue processing after audit failure, actions could be taken on the system that could not be tracked and recorded for later forensic analysis. To perform this function, some type of heartbeat configuration with all of the devices and hosts must be configured. Because of the importance of ensuring mission/business continuity, organizations may determine that the nature of the audit failure is not so severe that it warrants a complete shutdown of the application supporting the core organizational missions/business operations. In those instances, partial application shutdowns or operating in a degraded mode may be viable alternatives. This requirement applies to each audit data storage repository (i.e., distinct information system component where log records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.

Checks: C-80813r1_chk

Examine the configuration. Verify the system is configured to send an immediate alert to the SA or ISSO if communication with the host and devices within its scope of coverage is lost. If the Central Log Server is not configured to send an immediate alert to the SA or ISSO if communication with the host and devices within its scope of coverage is lost, this is a finding.

Fix: F-87927r1_fix

Configure the Central Log Server to send an immediate alert to the SA or ISSO if communication with the host and devices within its scope of coverage is lost.

a

The Central Log Server must be configured to perform on-demand sorting of log records for events of interest based on the content of organization-defined audit fields within log records.

AU-7 - Low - CCI-001886 - V-81153 - SV-95867r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001886

Version

SRG-APP-000362-AU-000170

Vuln IDs

V-81153

Rule IDs

SV-95867r1_rule

The ability to sort the log records to better view events of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded. This requires applications to be configured to sort log record reports based on organization-defined criteria.

Checks: C-80815r1_chk

Examine the configuration. Verify the system is configured to perform on-demand sorting of log records for events of interest based on the content of organization-defined audit fields within log records. If the Central Log Server is not configured to perform on-demand sorting of log records for events of interest based on the content of organization-defined audit fields within log records, this is a finding.

Fix: F-87929r1_fix

Configure the Central Log Server to perform on-demand sorting of log records for events of interest based on the content of organization-defined audit fields within log records.

a

The Central Log Server must be configured to perform on-demand searches of log records for events of interest based on the content of organization-defined audit fields within log records.

AU-7 - Low - CCI-001887 - V-81155 - SV-95869r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001887

Version

SRG-APP-000363-AU-000180

Vuln IDs

V-81155

Rule IDs

SV-95869r1_rule

The ability to search the log records to better view events of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded. This requires applications to provide the capability to search log record reports based on organization-defined criteria.

Checks: C-80817r1_chk

Examine the configuration. Verify the Central Log Server performs on-demand searches of log records for events of interest based on the content of organization-defined audit fields within log records. If the Central Log Server is not configured to perform on-demand searches of log records for events of interest based on the content of organization-defined audit fields within log records, this is a finding.

Fix: F-87969r1_fix

Configure the Central Log Server to perform on-demand searches of log records for events of interest based on the content of organization-defined audit fields within log records.

b

The Central Log Server must be configured to perform audit reduction that supports on-demand audit review and analysis.

AU-7 - Medium - CCI-001875 - V-81157 - SV-95871r1_rule

RMF Control

AU-7

Severity

M

CCI

CCI-001875

Version

SRG-APP-000364-AU-000190

Vuln IDs

V-81157

Rule IDs

SV-95871r1_rule

The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Audit reduction is a technique used to reduce the volume of log records to facilitate a manual review. Audit reduction does not alter original log records. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports. This requirement is specific to applications with audit reduction capabilities; however, applications need to support on-demand audit review and analysis.

Checks: C-80819r1_chk

Examine the configuration. Verify the system performs audit reduction that supports on-demand audit review and analysis. If the Central Log Server is not configured to perform audit reduction that supports on-demand audit review and analysis, this is a finding.

Fix: F-87931r1_fix

Configure the Central Log Server to perform audit reduction that supports on-demand audit review and analysis.

a

The Central Log Server must be configured to perform audit reduction that supports after-the-fact investigations of security incidents.

AU-7 - Low - CCI-001877 - V-81159 - SV-95873r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001877

Version

SRG-APP-000365-AU-000210

Vuln IDs

V-81159

Rule IDs

SV-95873r1_rule

If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies. Audit reduction capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools. This requirement is specific to applications with audit reduction capabilities.

Checks: C-80821r1_chk

Examine the configuration. Verify the Central Log Server performs audit reduction that supports after-the-fact investigations of security incidents. If the Central Log Server is not configured to perform audit reduction that supports after-the-fact investigations of security incidents, this is a finding.

Fix: F-87933r1_fix

Configure the Central Log Server to perform audit reduction that supports after-the-fact investigations of security incidents.

a

The Central Log Server must be configured to generate on-demand audit review and analysis reports.

AU-7 - Low - CCI-001878 - V-81161 - SV-95875r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001878

Version

SRG-APP-000366-AU-000220

Vuln IDs

V-81161

Rule IDs

SV-95875r1_rule

The report generation capability must support on-demand review and analysis to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective. Audit reduction and report generation capabilities do not always reside on the same information system or within the same organizational entities conducting auditing activities. The audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in log records. The report generation capability provided by the information system can generate customizable reports. Time ordering of log records can be a significant issue if the granularity of the timestamp in the record is insufficient. This requirement is specific to applications with report generation capabilities; however, applications need to support on-demand audit review and analysis.

Checks: C-80823r1_chk

Examine the configuration. Verify the Central Log Server generates on-demand audit review and analysis reports. If the Central Log Server is not configured to generate on-demand audit review and analysis reports, this is a finding.

Fix: F-87935r1_fix

Configure the Central Log Server to generate on-demand audit review and analysis reports.

a

The Central Log Server must be configured to generate reports that support on-demand reporting requirements.

AU-7 - Low - CCI-001879 - V-81163 - SV-95877r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001879

Version

SRG-APP-000367-AU-000230

Vuln IDs

V-81163

Rule IDs

SV-95877r1_rule

The report generation capability must support on-demand reporting to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents The report generation capability provided by the application must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective. This requirement is specific to applications with report generation capabilities; however, applications need to support on-demand reporting requirements.

Checks: C-80827r1_chk

Examine the configuration. Verify the Central Log Server generates reports that support on-demand reporting requirements. If the Central Log Server is not configured to generate reports that support on-demand reporting requirements, this is a finding.

Fix: F-87939r1_fix

Configure the Central Log Server to generate reports that support on-demand reporting requirements.

a

The Central Log Server must be configured to generate reports that support after-the-fact investigations of security incidents.

AU-7 - Low - CCI-001880 - V-81165 - SV-95879r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001880

Version

SRG-APP-000368-AU-000240

Vuln IDs

V-81165

Rule IDs

SV-95879r1_rule

If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies. The report generation capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools. This requirement is specific to applications with report generation capabilities; however, applications need to support on-demand reporting requirements.

Checks: C-80829r1_chk

Examine the configuration. Verify the Central Log Server generates reports that support after-the-fact investigations of security incidents. If the Central Log Server is not configured to generate reports that support after-the-fact investigations of security incidents, this is a finding.

Fix: F-87941r1_fix

Configure the Central Log Server to generate reports that support after-the-fact investigations of security incidents.

a

The Central Log Server must be configured to perform audit reduction that does not alter original content or time ordering of log records.

AU-7 - Low - CCI-001881 - V-81167 - SV-95881r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001881

Version

SRG-APP-000369-AU-000250

Vuln IDs

V-81167

Rule IDs

SV-95881r1_rule

If the audit reduction capability alters the content or time ordering of log records, the integrity of the log records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this. Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. This requirement is specific to applications with audit reduction capabilities; however, applications need to support on-demand audit review and analysis.

Checks: C-80831r1_chk

Examine the configuration. Verify the Central Log Server performs audit reduction that does not alter original content or time ordering of log records. If the Central Log Server is not configured to perform audit reduction that does not alter original content or time ordering of log records, this is a finding.

Fix: F-87943r1_fix

Configure the Central Log Server to perform audit reduction that does not alter original content or time ordering of log records.

a

The Central Log Server must be configured to generate reports that do not alter original content or time ordering of log records.

AU-7 - Low - CCI-001882 - V-81169 - SV-95883r1_rule

RMF Control

AU-7

Severity

L

CCI

CCI-001882

Version

SRG-APP-000370-AU-000260

Vuln IDs

V-81169

Rule IDs

SV-95883r1_rule

If the audit report generation capability alters the original content or time ordering of log records, the integrity of the log records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this. The report generation capability provided by the application can generate customizable reports. This requirement is specific to applications with audit reduction capabilities; however, applications need to support on-demand audit review and analysis.

Checks: C-80833r1_chk

Examine the configuration. Verify the Central Log Server generates reports that do not alter original content or time ordering of log records. If the Central Log Server is not configured to generate reports that do not alter original content or time ordering of log records, this is a finding.

Fix: F-87945r1_fix

Configure the Central Log Server to generate reports that do not alter original content or time ordering of log records.

a

Upon receipt of the log record from hosts and devices, the Central Log Server must be configured to record time stamps of the time of receipt that can be mapped to Coordinated Universal Time (UTC).

AU-8 - Low - CCI-001890 - V-81171 - SV-95885r1_rule

RMF Control

AU-8

Severity

L

CCI

CCI-001890

Version

SRG-APP-000374-AU-000290

Vuln IDs

V-81171

Rule IDs

SV-95885r1_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 Greenwich Mean Time (GMT), or local time with an offset from UTC.

Checks: C-80835r1_chk

Examine the log records stored on the events server. Verify the Central Log Server records time stamps of the time the record was received from the host or device. Verify the time stamp is mapped to UTC. If the Central Log Server is not configured to record time stamps of the time the record was received or the time stamp is not mapped to UTC, this is a finding.

Fix: F-87947r1_fix

Configure the Central Log Server to record time stamps of the time the record was received from the host or device. Verify the time stamp is mapped to UTC.

a

The Central Log Server must be configured to record time stamps for when log records are received by the log server that meet a granularity of one second for a minimum degree of precision.

AU-8 - Low - CCI-001889 - V-81173 - SV-95887r1_rule

RMF Control

AU-8

Severity

L

CCI

CCI-001889

Version

SRG-APP-000375-AU-000280

Vuln IDs

V-81173

Rule IDs

SV-95887r1_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. Note: The actual configuring and security requirements for NTP is handled in the host OS or NDM STIGs that are also required as part of a Central Log Server review.

Checks: C-80837r1_chk

Examine the configuration. Verify the Central Log Server records time stamps for when log records are received by the log server that meet a granularity of one second for a minimum degree of precision. If the Central Log Server is not configured to record time stamps for when log records are received by the log server that meet a granularity of one second for a minimum degree of precision, this is a finding.

Fix: F-87949r1_fix

Configure the Central Log Server to record time stamps for when log records are received by the log server that meet a granularity of one second for a minimum degree of precision.

a

The Central Log Server must be configured to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum.

AU-4 - Low - CCI-001851 - V-81177 - SV-95891r1_rule

RMF Control

AU-4

Severity

L

CCI

CCI-001851

Version

SRG-APP-000515-AU-000110

Vuln IDs

V-81177

Rule IDs

SV-95891r1_rule

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Although this may be part of the operating system function, for the enterprise events management system, this is most often a function managed through the application since it is a critical function and requires the use of a large amount of external storage.

Checks: C-80841r1_chk

Note: This is not applicable (NA) if an external application or operating system manages this function. Examine the configuration. Verify the system is configured to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum. If the Central Log Server is not configured to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum, this is a finding.

Fix: F-87953r1_fix

Configure the Central Log Server to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum.

b

The Central Log Server must be configured to retain the identity of the original source host or device where the event occurred as part of the log record.

CM-6 - Medium - CCI-000366 - V-81179 - SV-95893r1_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000330

Vuln IDs

V-81179

Rule IDs

SV-95893r1_rule

In this case the information producer is the device based on IP address or some other identifier of the device producing the information. The source of the record must be bound to the record using cryptographic means. Some events servers allow the administrator to retain only portions of the record sent by devices and hosts. This requirement applies to log aggregation servers with the role of fulfilling the DoD requirement for a central log repository. The syslog, SIEM, or other event servers must retain this information with each log record to support incident investigations.

Checks: C-80845r1_chk

Examine the configuration. Verify the Central Log Server is configured to include the identity of the original source host or device where the event occurred as part of each aggregated log record. If the Central Log Server is not configured to include the identity of the original source host or device where the event occurred as part of the aggregated log record, this is a finding.

Fix: F-87955r1_fix

Configure the Central Log Server to include the identity of the original source host or device as part of each aggregated log record.

b

The Central Log Server that aggregates log records from hosts and devices must be configured to use TCP for transmission.

CM-6 - Medium - CCI-000366 - V-81181 - SV-95895r2_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000340

Vuln IDs

V-81181

Rule IDs

SV-95895r2_rule

If the default UDP protocol is used for communication between the hosts and devices to the Central Log Server, then log records that do not reach the log server are not detected as a data loss. The use of TCP to transport log records to the log servers improves delivery reliability, adds data integrity, and gives the option to encrypt the traffic if the log server communication is not protected using a management network (preferred) or VPN based on mission requirements.

Checks: C-80847r2_chk

Examine the configuration. Verify the Central Log Server is configured to use TCP. If the Central Log Server is not configured to use TCP, this is a finding.

Fix: F-87957r2_fix

Configure the Central Log Server that aggregates log records from hosts and devices to use TCP for transmission.

b

The Central Log Server must be configured to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when an attack is detected on multiple devices and hosts within its scope of coverage.

CM-6 - Medium - CCI-000366 - V-81183 - SV-95897r1_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000350

Vuln IDs

V-81183

Rule IDs

SV-95897r1_rule

Notification may be configured to be sent by the device, SNMP server, or Central Log Server. The best practice is for these notifications to be sent by a robust events management server. This is a function provided by most enterprise-level SIEMs. If the Central Log Server does not provide this function, it must forward the log records to a log server that does.

Checks: C-80849r1_chk

Note: This is not applicable (NA) if the Central Log Server (e.g., syslog, SIEM) does not perform analysis. This is NA if notifications are performed by another device. Examine the configuration. Verify the Central Log Server is configured to notify the SA and ISSO, at a minimum, when an attack is detected on multiple devices and hosts within its scope of coverage. If the Central Log Server is not configured to notify the SA and ISSO, at a minimum, when an attack is detected on multiple devices and hosts within its scope of coverage, this is a finding.

Fix: F-87959r1_fix

Configure the Central Log Server to notify the SA and ISSO, at a minimum, when an attack is detected on multiple devices and hosts within its scope of coverage.

b

The Central Log Server must be configured to automatically create trouble tickets for organization-defined threats and events of interest as they are detected in real time (within seconds).

CM-6 - Medium - CCI-000366 - V-81185 - SV-95899r1_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000360

Vuln IDs

V-81185

Rule IDs

SV-95899r1_rule

In most Central Log Server products today, log review (threat detection), can be automated by creating correlation content matching the organizational-defined Events of Interest (e.g., account change actions, privilege command use, and other AU and AC family controls) to automatically notify or automatically create trouble tickets for threats as they are detected in real time. Auditors have repeatedly expressed a strong preference for automated ticketing. They are also more likely to follow up on the threat and action items needed to address the detected issues if the ticketing process is automated. This is a function provided by most enterprise-level SIEMs. If the Central Log Server does not provide this function, it must forward the log records to a log server that does.

Checks: C-80851r1_chk

Note: This is not applicable (NA) if the Central Log Server (e.g., syslog) does not perform analysis. Examine the configuration. Verify the Central Log Server automatically creates trouble tickets for organization-defined threats and events of interest as they are detected in real time (within seconds). If the Central Log Server is not configured to automatically create trouble tickets for organization-defined threats and events of interest as they are detected in real time (within seconds), this is a finding.

Fix: F-87961r1_fix

Configure the Central Log Server to automatically create trouble tickets for organization-defined threats and events of interest as they are detected in real time (within seconds).

b

For devices and hosts within the scope of coverage, the Central Log Server must be configured to automatically aggregate events that indicate account actions.

CM-6 - Medium - CCI-000366 - V-81187 - SV-95901r1_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000370

Vuln IDs

V-81187

Rule IDs

SV-95901r1_rule

If the Central Log Server is configured to filter or remove account log records transmitted by devices and hosts within its scope of coverage, forensic analysis tools will be less effective at detecting and reporting on important attack vectors. A comprehensive account management process must include capturing log records for the creation of user accounts and notification of administrators and/or application owners. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. This requirement addresses the concern that the Central Log Server may be configured to filter out certain levels of information, which may result in the discarding of DoD-required accounting actions addressed in the AC-2 (4) controls such as creation, modification, deletion, and removal of privileged accounts.

Checks: C-80853r1_chk

Examine the configuration. Verify the Central Log Server automatically aggregates events that indicate account actions for each device and host within its scope of coverage. If the Central Log Server is not configured to automatically aggregate events that indicate account actions for each device and host within its scope of coverage, this is a finding.

Fix: F-87963r1_fix

Configure the Central Log Server to automatically aggregate events that indicate account actions for each device and host within its scope of coverage.

b

The Central Log Server must be configured with the organization-defined severity or criticality levels of each event that is being sent from individual devices or hosts.

CM-6 - Medium - CCI-000366 - V-81189 - SV-95903r2_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000380

Vuln IDs

V-81189

Rule IDs

SV-95903r2_rule

This supports prioritization functions, which is a major reason why centralized management is a requirement in DoD. This includes different features that help highlight the important events over less critical security events. This may be accomplished by correlating security events with vulnerability data or other asset information. Prioritization algorithms often use severity information provided by the original log source as well. The criticality levels used by the site and the actions that are taken based on the levels established for each system are documented in the SSP. These levels and actions can only be leveraged for alerts, notifications, and reports which correlate asset information if they are configured in the Central Log Server.

Checks: C-80857r2_chk

Obtain the site’s SSP to see which criticality levels are used for each system within the scope of the Central Log Server. Examine the configuration of the Central Log Server. Verify the Central Log Server is configured with the organization-defined severity or criticality levels of each event that is being sent from individual devices or hosts. If the Central Log Server is not configured with the organization-defined severity or criticality levels of each event that is being sent from individual devices or hosts, this is a finding.

Fix: F-87965r1_fix

Configure the Central Log Server with the organization-defined severity or criticality levels of each event that is being sent from individual devices or hosts.

b

Analysis, viewing, and indexing functions, services, and applications used as part of the Central Log Server must be configured to comply with DoD-trusted path and access requirements.

CM-6 - Medium - CCI-000366 - V-81191 - SV-95905r1_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-AU-000410

Vuln IDs

V-81191

Rule IDs

SV-95905r1_rule

Analysis, viewing, and indexing functions, services, and applications, such as analysis tools and other vendor-provided applications, must be secured. Software used to perform additional functions, which resides on the server, must also be secured or could provide a vector for unauthorized access to the events repository.

Checks: C-80859r1_chk

Examine the configuration. Verify analysis, viewing, and indexing functions, services, and applications used with the Central Log Server are configured to comply with DoD-trusted path and access requirements. If analysis, viewing, and indexing functions, services, and applications used with the Central Log Server are not configured to comply with DoD-trusted path and access requirements, this is a finding.

Fix: F-87967r1_fix

Configure all analysis, viewing, and indexing functions, services, and applications used with the Central Log Server to comply with DoD-trusted path and access requirements.

c

The Central Log Server must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

IA-2 - High - CCI-000764 - V-81281 - SV-95995r1_rule

RMF Control

IA-2

Severity

H

CCI

CCI-000764

Version

SRG-APP-000148-AU-002270

Vuln IDs

V-81281

Rule IDs

SV-95995r1_rule

To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses.

Checks: C-80981r1_chk

Examine the configuration. Verify that individual user accounts are defined within the application. Each account must have a separate identifier. If an authentication server may be used for login, ensure the application audit logs containing management and configuration actions, identify the individual performing each action. If the Central Log Server is not configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users), this is a finding.

Fix: F-88063r1_fix

For systems where individual users access, configure and/or manage the system, configure the Central Log Server application so each user is explicitly identified and authenticated. While an authentication server, is often used for logon, this requirement must include instructions for integrating the authentication server so that they system requires unique identification and authentication. Note: Group accounts are not permitted for logon to the Central Log Server.

c

For accounts using password authentication, the Central Log Server must be configured to store only cryptographic representations of passwords.

IA-5 - High - CCI-000196 - V-81283 - SV-95997r1_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000196

Version

SRG-APP-000171-AU-002540

Vuln IDs

V-81283

Rule IDs

SV-95997r1_rule

Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read and easily compromised. Use of passwords for authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include: - When the user does not use a CAC and is not a current DoD employee, member of the military, or DoD contractor. - When a user has been officially designated as temporarily unable to present a CAC for some reason (lost, damaged, not yet issued, broken card reader) (i.e., Temporary Exception User) and to satisfy urgent organizational needs must be temporarily permitted to use user ID/password authentication until the problem with CAC use has been remedied. - When the application is publicly available and or hosting publicly releasable data requiring some degree of need-to-know protection. If the password is already encrypted and not a plaintext password, this meets this requirement. Implementation of this requirement requires configuration of a FIPS-approved cipher block algorithm and block cipher modes for encryption. This method uses a one-way hashing encryption algorithm with a salt value to validate a user's password without having to store the actual password. Performance and time required to access are factors that must be considered, and the one-way hash is the most feasible means of securing the password and providing an acceptable measure of password security. Verifying the user knows a password is performed using a password verifier. In its simplest form, a password verifier is a computational function that is capable of creating a hash of a password and determining if the value provided by the user matches the hash. A more secure version of verifying a user knowing a password is to store the result of an iterating hash function and a large random salt value as follows: H0 = H(pwd, H(salt)) Hn = H(Hn-1,H(salt)) In the above, "n" is a cryptographically-strong random [*3] number. "Hn" is stored along with the salt. When the application wishes to verify that the user knows a password, it simply repeats the process and compares "Hn" with the stored "Hn". A salt is essentially a fixed-length cryptographically strong random value. Another method is using a keyed-hash message authentication code (HMAC). HMAC calculates a message authentication code via a cryptographic hash function used in conjunction with an encryption key. The key must be protected as with any private key.

Checks: C-80983r1_chk

Examine the configuration. Verify the Central Log Server is configured to store only cryptographic representations of passwords. If the Central Log Server is not configured to store only cryptographic representations of passwords, this is a finding.

Fix: F-88065r1_fix

Configure the Central Log Server to store only cryptographic representations of passwords.

c

For accounts using password authentication, the Central Log Server must use FIPS-validated SHA-1 or later protocol to protect the integrity of the password authentication process.

IA-5 - High - CCI-000197 - V-81285 - SV-95999r1_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000197

Version

SRG-APP-000172-AU-002550

Vuln IDs

V-81285

Rule IDs

SV-95999r1_rule

Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. The information system must specify the hash algorithm used for authenticating passwords. Implementation of this requirement requires configuration of FIPS-approved cipher block algorithm and block cipher modes for encryption. This requirement applies to all accounts, including authentication server; Authorization, Authentication, and Accounting (AAA); and local accounts such as the root account and the account of last resort. This requirement only applies to components where this is specific to the function of the device (e.g., TLS VPN or ALG). This does not apply to authentication for the purpose of configuring the device itself (management).

Checks: C-80985r1_chk

Examine the configuration. Verify the Central Log Server is configured to use FIPS-validated SHA-1 or later protocol to protect the integrity of the password authentication process. If the Central Log Server is not configured to use FIPS-validated SHA-1 or later protocol to protect the integrity of the password authentication process, this is a finding.

Fix: F-88067r1_fix

Configure the Central Log Server to use FIPS-validated SHA-1 or later protocol to protect the integrity of the password authentication process.

c

The Central Log Server, when utilizing PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.

IA-5 - High - CCI-000185 - V-81287 - SV-96001r1_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000185

Version

SRG-APP-000175-AU-002630

Vuln IDs

V-81287

Rule IDs

SV-96001r1_rule

Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. This requirement verifies that a certification path to an accepted trust anchor is used to for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.

Checks: C-80987r1_chk

Examine the configuration. Verify the Central Log Server is configured to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. If the Central Log Server is not configured to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor, this is a finding.

Fix: F-88069r1_fix

Configure the Central Log Server to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.

c

The Central Log Server, when using PKI-based authentication, must enforce authorized access to the corresponding private key.

IA-5 - High - CCI-000186 - V-81289 - SV-96003r1_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000186

Version

SRG-APP-000176-AU-002640

Vuln IDs

V-81289

Rule IDs

SV-96003r1_rule

If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.

Checks: C-80989r1_chk

If not using PKI-based authentication this is NA. Examine the configuration. Verify the Central Log Server is configured to enforce authorized access to the corresponding private key when using PKI-based authentication. If the Central Log Server is not configured to enforce authorized access to the corresponding private key when using PKI-based authentication, this is a finding.

Fix: F-88071r1_fix

If using PKI-based authentication, configure the Central Log Server to enforce authorized access to the corresponding private key.

c

The Central Log Server must obfuscate authentication information during the authentication process so that the authentication is not visible.

IA-6 - High - CCI-000206 - V-81291 - SV-96005r1_rule

RMF Control

IA-6

Severity

H

CCI

CCI-000206

Version

SRG-APP-000178-AU-002660

Vuln IDs

V-81291

Rule IDs

SV-96005r1_rule

To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. For example, displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.

Checks: C-80993r1_chk

Examine the configuration. Verify the Central Log Server is configured to obfuscate authentication information during the authentication process so that the authentication is not visible. If the Central Log Server is not configured to obfuscate authentication information during the authentication process so that the authentication is not visible, this is a finding.

Fix: F-88073r1_fix

Configure the Central Log Server to obfuscate authentication information during the authentication process so that the authentication is not visible to protect the information from possible exploitation/use by unauthorized individuals.

c

The Central Log Server must use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only).

IA-7 - High - CCI-000803 - V-81295 - SV-96009r1_rule

RMF Control

IA-7

Severity

H

CCI

CCI-000803

Version

SRG-APP-000179-AU-002670

Vuln IDs

V-81295

Rule IDs

SV-96009r1_rule

Without cryptographic integrity protections, information can be altered by unauthorized users without detection. To protect the integrity of the authenticator and authentication mechanism used for the cryptographic module used by the Central Log Server must be configured to use one of the following hash functions for hashing the password or other authenticator in accordance with SP 800-131Ar1: SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256, SHA3-224, SHA3-256, SHA3-384, and SHA3-512. Applications also include HMAC, KDFs, Random Bit Generation, and hash-only applications (e.g., hashing passwords and using SHA-1 or higher to compute a checksum). For digital signature verification, SP800-131Ar1 allows SHA-1 for legacy use where needed.

Checks: C-80995r1_chk

Examine the configuration. Verify the Central Log Server is configured to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only). If the Central Log Server is not configured to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only), this is a finding.

Fix: F-88077r1_fix

Configure the Central Log Server to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only).

c

The Central Log Server must be configured to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

AC-3 - High - CCI-000213 - V-81297 - SV-96011r1_rule

RMF Control

AC-3

Severity

H

CCI

CCI-000213

Version

SRG-APP-000033-AU-001610

Vuln IDs

V-81297

Rule IDs

SV-96011r1_rule

To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. This requirement is applicable to access control enforcement applications (e.g., authentication servers) and other applications that perform information and system access control functions.

Checks: C-80999r1_chk

Verify the Central Log Server user accounts are configured for granular permissions to separate and control access levels of accounts used to access the application. Users should not have access permissions that are not relevant to their role. If the Central Log Server is not configured to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies, this is a finding.

Fix: F-88081r1_fix

Configure the Central Log Server with granular permissions to separate and control access levels of accounts used to access the application.

c

The Central Log Server must be configured to protect the confidentiality and integrity of transmitted information.

SC-8 - High - CCI-002418 - V-81301 - SV-96015r1_rule

RMF Control

SC-8

Severity

H

CCI

CCI-002418

Version

SRG-APP-000439-AU-004310

Vuln IDs

V-81301

Rule IDs

SV-96015r1_rule

Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distributed or can allow access to data non-locally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, applications need to leverage transmission protection mechanisms, such as TLS, SSL VPNs, or IPSEC. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.

Checks: C-81001r1_chk

Examine the configuration. Verify the Central Log Server is configured to use transmission protection mechanisms, such as TLS, SSL VPNs, or IPsec along with integrity protections such as FIPS 140-2 validated digital signature and hash function. If the Central Log Server is not configured to protect the confidentiality and integrity of transmitted information, this is a finding.

Fix: F-88083r1_fix

Configure the Central Log Server to use transmission protection mechanisms, such as TLS, SSL VPNs, or IPsec along with integrity protections such as FIPS 140-2 validated digital signature and hash function.

c

The Central Log Server must implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and/or to protect unclassified information requiring confidentiality and cryptographic protection.

SC-13 - High - CCI-002450 - V-81303 - SV-96017r1_rule

RMF Control

SC-13

Severity

H

CCI

CCI-002450

Version

SRG-APP-000514-AU-002890

Vuln IDs

V-81303

Rule IDs

SV-96017r1_rule

FIPS 140-2 precludes the use of unvalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as providing no protection to the information or data. In effect, the data would be considered unprotected plaintext. If the agency specifies that the information or data be cryptographically protected, then FIPS 140-2 is applicable. In essence, if cryptography is required, it must be validated. Cryptographic modules that have been approved for classified use may be used in lieu of modules that have been validated against the FIPS 140-2 standard.

Checks: C-81005r1_chk

Examine the configuration. Verify the Central Log Server is configured to implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and/or to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If the Central Log Server is not configured to implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and/or to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards, this is a finding.

Fix: F-88085r1_fix

Configure the Central Log Server to implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and/or to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

b

The Central Log Server must use multifactor authentication for network access to privileged user accounts.

IA-2 - Medium - CCI-000765 - V-81307 - SV-96021r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000765

Version

SRG-APP-000149-AU-002280

Vuln IDs

V-81307

Rule IDs

SV-96021r1_rule

Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) something a user is (e.g., biometric). A privileged account is defined as an information system account with authorizations of a privileged user. Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the Internet).

Checks: C-81007r3_chk

Examine the configuration. Verify the Central Log Server is configured to require DoD PKI or another multifactor authentication method for logon via the network for all privileged accounts. If the account of last resort is used for logon via the network (not recommended), then verify it is configured to require multifactor authentication method. If the Central Log Server is not configured to use multifactor authentication for network access to privileged user accounts, this is a finding.

Fix: F-88089r1_fix

This requirement applies to all privileged accounts used for access to the system via network access. For systems where individual users access, configure and/or manage the system, configure the Central Log server application to use DoD PKI (preferred) or another multifactor authentication solution for network access to logon to the Central Log Server. If the account of last resort is used for logon via the network (not recommended), then configure the account to require multifactor authentication method.

b

The Central Log Server must use multifactor authentication for network access to non-privileged user accounts.

IA-2 - Medium - CCI-000766 - V-81309 - SV-96023r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000766

Version

SRG-APP-000150-AU-002320

Vuln IDs

V-81309

Rule IDs

SV-96023r1_rule

To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses two or more factors to achieve authentication. Factors include: (i) Something you know (e.g., password/PIN); (ii) Something you have (e.g., cryptographic identification device, token); or (iii) Something you are (e.g., biometric). A non-privileged account is any information system account with authorizations of a non-privileged user. Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection. Applications integrating with the DoD Active Directory and utilize the DoD CAC are examples of compliant multifactor authentication solutions.

Checks: C-81011r2_chk

Examine the configuration. Verify the Central Log Server is configured to require DoD PKI or another multifactor authentication method for logon via the network for all non-privileged accounts. If the Central Log Server is not configured to use multifactor authentication for network access to non-privileged user accounts, this is a finding.

Fix: F-88091r1_fix

This requirement applies to all non-privileged accounts used for access to the system via network access. For systems where individual users access, configure and/or manage the system, configure the Central Log Server to use DoD PKI (preferred) or another multifactor authentication solution for network access to logon to the Central Log Server.

b

The Central Log Server must use multifactor authentication for local access using privileged user accounts.

IA-2 - Medium - CCI-000767 - V-81313 - SV-96027r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000767

Version

SRG-APP-000151-AU-002330

Vuln IDs

V-81313

Rule IDs

SV-96027r1_rule

To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication is defined as: using two or more factors to achieve authentication. Factors include: (i) Something a user knows (e.g., password/PIN); (ii) Something a user has (e.g., cryptographic identification device, token); or (iii) Something a user is (e.g., biometric). A privileged account is defined as an information system account with authorizations of a privileged user. Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Applications integrating with the DoD Active Directory and utilize the DoD CAC are examples of compliant multifactor authentication solutions.

Checks: C-81013r4_chk

Examine the configuration. Verify the Central Log Server is configured to require DoD PKI or another multifactor authentication method for local logon. If the Central Log Server is not configured to use multifactor authentication for local access using privileged accounts, this is a finding.

Fix: F-88095r1_fix

This requirement applies to all privileged user accounts used for local logon to the application. For systems where individual users access, configure and/or manage the system, configure the Central Log Server to use DoD PKI (preferred) or another multifactor authentication solution for local logon to the Central Log Server.

b

The Central Log Server must be configured to use multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.

IA-2 - Medium - CCI-001936 - V-81315 - SV-96029r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001936

Version

SRG-APP-000154-AU-002360

Vuln IDs

V-81315

Rule IDs

SV-96029r1_rule

Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards, such as the U.S. Government Personal Identity Verification card and the DoD common access card. A privileged account is any information system account with authorizations of a privileged user. Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection.

Checks: C-81015r1_chk

Examine the configuration. Verify the Central Log Server is configured to use DoD PKI or another form of multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. If the Central Log Server is not configured to use multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access, this is a finding.

Fix: F-88097r1_fix

This requirement applies to all privileged user accounts used for network logon to the application. Configure the Central Log Server to use DoD PKI or another form of multifactor authentication for network access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.

b

The Central Log Server must use FIPS-validated SHA-1 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts.

IA-2 - Medium - CCI-001941 - V-81317 - SV-96031r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001941

Version

SRG-APP-000156-AU-002380

Vuln IDs

V-81317

Rule IDs

SV-96031r1_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. Anti-replay is a cryptographically based mechanism; thus, it must use FIPS-approved algorithms. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Note that the anti-replay service is implicit when data contains monotonically increasing sequence numbers and data integrity is assured. Use of DoD PKI is inherently compliant with this requirement for user and device access. Use of Transport Layer Security (TLS), including application protocols, such as HTTPS and DNSSEC, that use TLS/SSL as the underlying security protocol is also complaint. Configure the information system to use the hash message authentication code (HMAC) algorithm for authentication services to Kerberos, SSH, web management tool, and any other access method.

Checks: C-81017r1_chk

Examine the configuration. Verify the Central Log Server is configured to use FIPS-validated SHA-1 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts. If the Central Log Server does not use FIPS-validated SHA-1 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts, this is a finding.

Fix: F-88099r1_fix

This requirement applies to all privileged user accounts used for network logon to the application. Configure the Central Log Server to use FIPS-validated SHA-1 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts.

b

The Central Log Server must disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity.

IA-4 - Medium - CCI-000795 - V-81319 - SV-96033r1_rule

RMF Control

IA-4

Severity

M

CCI

CCI-000795

Version

SRG-APP-000163-AU-002470

Vuln IDs

V-81319

Rule IDs

SV-96033r1_rule

Inactive identifiers pose a risk to systems and applications. Attackers that are able to exploit an inactive identifier can potentially obtain and maintain undetected access to the application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need to track periods of inactivity and disable application identifiers after 35 days of inactivity. Management of user identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). It is commonly the case that a user account is the name of an information system account associated with an individual. To avoid having to build complex user management capabilities directly into their application, wise developers leverage the underlying OS or other user account management infrastructure (AD, LDAP) that is already in place within the organization and meets organizational user account management requirements.

Checks: C-81021r1_chk

Examine the configuration. Verify the Central Log Server is configured to disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity. If the Central Log Server does not disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity, this is a finding.

Fix: F-88101r1_fix

For local accounts (except for the account of last resort), configure the Central Log Server to disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity.

b

The Central Log Server must be configured to enforce a minimum 15-character password length.

IA-5 - Medium - CCI-000205 - V-81321 - SV-96035r1_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000205

Version

SRG-APP-000164-AU-002480

Vuln IDs

V-81321

Rule IDs

SV-96035r1_rule

The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. 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-81023r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce a minimum 15-character password length. If the Central Log Server is not configured to enforce a minimum 15-character password length, this is a finding.

Fix: F-88105r1_fix

Configure the Central Log Server to enforce a minimum 15-character password length.

b

The Central Log Server must be configured to accept the DoD CAC credential to support identity management and personal authentication.

IA-2 - Medium - CCI-001953 - V-81323 - SV-96037r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001953

Version

SRG-APP-000391-AU-002290

Vuln IDs

V-81323

Rule IDs

SV-96037r1_rule

The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary component of layered protection for national security systems. If the application cannot meet this requirement, the risk may be mitigated through use of an authentication server.

Checks: C-81025r3_chk

Examine the configuration. Verify the Central Log Server is configured to accept the DoD CAC credential to support identity management and personal authentication. If the Central Log Server cannot be configured to accept the DoD CAC credential to support identity management and personal authentication, this is a finding.

Fix: F-88107r1_fix

Configure the Central Log Server to accept the DoD CAC credential to support identity management and personal authentication.

b

The Central Log Server must be configured to electronically verify the DoD CAC credential.

IA-2 - Medium - CCI-001954 - V-81327 - SV-96041r1_rule

RMF Control

IA-2

Severity

M

CCI

CCI-001954

Version

SRG-APP-000392-AU-002300

Vuln IDs

V-81327

Rule IDs

SV-96041r1_rule

The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary component of layered protection for national security systems.

Checks: C-81031r2_chk

Examine the configuration. Verify the Central Log Server is configured to accept the DoD CAC credentials to support identity management and personal authentication. If the Central Log Server cannot be configured to accept the DoD CAC credentials to support identity management and personal authentication, this is a finding.

Fix: F-88111r1_fix

Configure the Central Log Server to accept the DoD CAC credentials to support identity management and personal authentication.

b

For locally created accounts in the application, the Central Log Server must be configured to allow the use of a temporary password for system logons with an immediate change to a permanent password.

IA-5 - Medium - CCI-002041 - V-81331 - SV-96045r1_rule

RMF Control

IA-5

Severity

M

CCI

CCI-002041

Version

SRG-APP-000397-AU-002590

Vuln IDs

V-81331

Rule IDs

SV-96045r1_rule

Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon. Temporary passwords are typically used to allow access to applications when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts that allow the users to log on, yet force them to change the password once they have successfully authenticated. The risk can be mitigated by allowing only the account of last resort to be configured locally. This requirement does not apply to that account.

Checks: C-81035r1_chk

Examine the configuration. Verify the Central Log Server is configured to allow the use of a temporary password for system logons with an immediate change to a permanent password. If the Central Log Server is not configured to allow the use of a temporary password for system logons with an immediate change to a permanent password, this is a finding.

Fix: F-88115r1_fix

Configure the Central Log Server to allow the use of a temporary password for system logons with an immediate change to a permanent password.

a

The Central Log Server must be configured to prohibit password reuse for a minimum of five generations.

IA-5 - Low - CCI-000200 - V-81335 - SV-96049r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000200

Version

SRG-APP-000165-AU-002580

Vuln IDs

V-81335

Rule IDs

SV-96049r1_rule

Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. To meet password policy requirements, passwords need to be changed at specific policy-based intervals. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.

Checks: C-81039r1_chk

Examine the configuration. Verify the Central Log Server is configured to prohibit password reuse for a minimum of five generations. If the Central Log Server is not configured to prohibit password reuse for a minimum of five generations, this is a finding.

Fix: F-88119r1_fix

Configure the Central Log Server to prohibit password reuse for a minimum of five generations.

a

The Central Log Server must be configured to enforce password complexity by requiring that at least one upper-case character be used.

IA-5 - Low - CCI-000192 - V-81337 - SV-96051r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000192

Version

SRG-APP-000166-AU-002490

Vuln IDs

V-81337

Rule IDs

SV-96051r1_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 is, the greater the number of possible combinations that need to be tested before the password is compromised.

Checks: C-81043r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce password complexity by requiring that at least one upper-case character be used. If the Central Log Server is not configured to enforce password complexity by requiring that at least one upper-case character be used, this is a finding.

Fix: F-88121r1_fix

Configure the Central Log Server to enforce password complexity by requiring that at least one upper-case character be used.

a

The Central Log Server must be configured to enforce password complexity by requiring that at least one lower-case character be used.

IA-5 - Low - CCI-000193 - V-81339 - SV-96053r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000193

Version

SRG-APP-000167-AU-002500

Vuln IDs

V-81339

Rule IDs

SV-96053r1_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.

Checks: C-81045r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce password complexity by requiring that at least one lower-case character be used. If the Central Log Server is not configured to enforce password complexity by requiring that at least one lower-case character be used, this is a finding.

Fix: F-88123r1_fix

Configure the Central Log Server to enforce password complexity by requiring that at least one lower-case character be used.

a

The Central Log Server must be configured to enforce password complexity by requiring that at least one numeric character be used.

IA-5 - Low - CCI-000194 - V-81345 - SV-96059r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000194

Version

SRG-APP-000168-AU-002510

Vuln IDs

V-81345

Rule IDs

SV-96059r1_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.

Checks: C-81053r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce password complexity by requiring that at least one numeric character be used. If the Central Log Server is not configured to enforce password complexity by requiring that at least one numeric character be used, this is a finding.

Fix: F-88131r1_fix

Configure the Central Log Server to enforce password complexity by requiring that at least one numeric character be used.

a

The Central Log Server must be configured to enforce password complexity by requiring that at least one special character be used.

IA-5 - Low - CCI-001619 - V-81349 - SV-96063r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-001619

Version

SRG-APP-000169-AU-002520

Vuln IDs

V-81349

Rule IDs

SV-96063r1_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 in determining 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. Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.

Checks: C-81057r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce password complexity by requiring that at least one special character be used. If the Central Log Server is not configured to enforce password complexity by requiring that at least one special character be used, this is a finding.

Fix: F-88135r1_fix

Configure the Central Log Server to enforce password complexity by requiring that at least one special character be used.

a

The Central Log Server must be configured to require the change of at least 8 of the total number of characters when passwords are changed.

IA-5 - Low - CCI-000195 - V-81353 - SV-96067r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000195

Version

SRG-APP-000170-AU-002530

Vuln IDs

V-81353

Rule IDs

SV-96067r1_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.

Checks: C-81061r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce password complexity by requiring the change of at least 8 of the total number of characters when passwords are changed. If the Central Log Server is not configured to require the change of at least 8 of the total number of characters when passwords are changed, this is a finding.

Fix: F-88139r1_fix

Configure the Central Log Server to require the change of at least 8 of the total number of characters when passwords are changed.

a

The Central Log Server must be configured to enforce 24 hours/1 day as the minimum password lifetime.

IA-5 - Low - CCI-000198 - V-81355 - SV-96069r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000198

Version

SRG-APP-000173-AU-002560

Vuln IDs

V-81355

Rule IDs

SV-96069r1_rule

Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. Restricting this setting limits the user's ability to change their password. Passwords need to be changed at specific policy based intervals; however, if the application allows the user to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.

Checks: C-81065r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce 24 hours/1 day as the minimum password lifetime. If the Central Log Server is not configured to enforce 24 hours/1 day as the minimum password lifetime, this is a finding.

Fix: F-88141r1_fix

Configure the Central Log Server to enforce 24 hours/1 day as the minimum password lifetime.

a

The Central Log Server must be configured to enforce a 60-day maximum password lifetime restriction.

IA-5 - Low - CCI-000199 - V-81359 - SV-96073r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000199

Version

SRG-APP-000174-AU-002570

Vuln IDs

V-81359

Rule IDs

SV-96073r1_rule

Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the system and/or application passwords could be compromised. This requirement does not include emergency administration accounts that are meant for access to the application in case of failure. These accounts are not required to have maximum password lifetime restrictions.

Checks: C-81067r1_chk

Examine the configuration. Verify the Central Log Server is configured to enforce a 60-day maximum password lifetime restriction. If the Central Log Server is not configured to enforce a 60-day maximum password lifetime restriction, this is a finding.

Fix: F-88145r1_fix

Configure the Central Log Server to enforce a 60-day maximum password lifetime restriction.

a

The Central Log Server must map the authenticated identity to the individual user or group account for PKI-based authentication.

IA-5 - Low - CCI-000187 - V-81363 - SV-96077r1_rule

RMF Control

IA-5

Severity

L

CCI

CCI-000187

Version

SRG-APP-000177-AU-002650

Vuln IDs

V-81363

Rule IDs

SV-96077r1_rule

Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.

Checks: C-81073r1_chk

Examine the configuration. Verify the Central Log Server is configured to map the authenticated identity to the individual user or group account for PKI-based authentication. If the Central Log Server is not configured to map the authenticated identity to the individual user or group account for PKI-based authentication, this is a finding.

Fix: F-88149r1_fix

Configure the Central Log Server to map the authenticated identity to the individual user or group account for PKI-based authentication.

b

The Central Log Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

AC-12 - Medium - CCI-002361 - V-100015 - SV-109119r1_rule

RMF Control

AC-12

Severity

M

CCI

CCI-002361

Version

SRG-APP-000295-AU-000190

Vuln IDs

V-100015

Rule IDs

SV-109119r1_rule

Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. This capability is typically reserved for specific application system functionality where the system owner, data owner, or organization requires additional assurance. Based upon requirements and events specified by the data or application owner, the application developer must incorporate logic into the application that will provide a control mechanism that disconnects users upon the defined event trigger. The methods for incorporating this requirement will be determined and specified on a case by case basis during the application design and development stages.

Checks: C-98865r1_chk

Examine the configuration. Verify that the Central Log Server is configured to automatically terminate a user session after organization-defined conditions or trigger events. If the Central Log Server is not configured to automatically terminate a user session after organization-defined conditions or trigger events, this is a finding.

Fix: F-105699r1_fix

Configure the Central Log Server to automatically terminate a user session after organization-defined conditions or trigger events.

b

The Central Log Server must provide a logout capability for user initiated communication session.

AC-12 - Medium - CCI-002363 - V-100017 - SV-109121r1_rule

RMF Control

AC-12

Severity

M

CCI

CCI-002363

Version

SRG-APP-000296-AU-000560

Vuln IDs

V-100017

Rule IDs

SV-109121r1_rule

If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web-based services. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions.

Checks: C-98867r1_chk

Examine the configuration. Verify that the Central Log Server provides a logout capability for user initiated sessions. If the Central Log Server does not provide a logout capability for user initiated sessions, this is a finding.

Fix: F-105701r1_fix

Configure the Central Log Server to provide a logout capability for user initiated sessions.

a

The Central Log Server must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.

AC-12 - Low - CCI-002364 - V-100019 - SV-109123r1_rule

RMF Control

AC-12

Severity

L

CCI

CCI-002364

Version

SRG-APP-000297-AU-000570

Vuln IDs

V-100019

Rule IDs

SV-109123r1_rule

If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated. Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web-based services. Logout messages for web page access, for example, can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions including, for example, file transfer protocol (FTP) sessions, information systems typically send logout messages as final messages prior to terminating sessions.

Checks: C-98869r1_chk

Examine the configuration. Verify that the Central Log Server is configured to display an explicit logout message to users indicating the reliable termination of authenticated sessions. If the Central Log Server is not configured to display an explicit logout message to users, it is a finding.

Fix: F-105703r1_fix

Configure the Central Log Server to display an explicit logout message to users indicating the reliable termination of authenticated sessions.

a

The Central Log Server must notify system administrators and ISSO when accounts are created.

AC-2 - Low - CCI-001683 - V-100021 - SV-109125r1_rule

RMF Control

AC-2

Severity

L

CCI

CCI-001683

Version

SRG-APP-000291-AU-000200

Vuln IDs

V-100021

Rule IDs

SV-109125r1_rule

Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Sending notification of account creation events to the system administrator and ISSO is one method for mitigating this risk. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.

Checks: C-98871r1_chk

Examine the configuration. Verify that the Central Log Server is configured to notify system administrators and the ISSO when accounts are created. If the Central Log Server is not configured to notify system administrators and ISSO when accounts are created, this is a finding.

Fix: F-105705r1_fix

Configure the Central Log Server to notify system administrators and the ISSO when accounts are created.

b

The Central Log Server must automatically audit account creation.

AC-2 - Medium - CCI-000018 - V-100025 - SV-109129r1_rule

RMF Control

AC-2

Severity

M

CCI

CCI-000018

Version

SRG-APP-000026-AU-000580

Vuln IDs

V-100025

Rule IDs

SV-109129r1_rule

Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail documents the creation of application user accounts and, as required, notifies administrators and/or application owners exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/auditing mechanisms meeting or exceeding access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.

Checks: C-98875r1_chk

Examine the configuration. Verify that the Central Log Server is configured to automatically audit account creation. If the Central Log Server is not configured to automatically audit account creation, this is a finding.

Fix: F-105709r1_fix

Configure the Central Log Server to automatically audit account creation.

b

The Central Log Server must automatically audit account modification.

AC-2 - Medium - CCI-001403 - V-100027 - SV-109131r1_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001403

Version

SRG-APP-000027-AU-000590

Vuln IDs

V-100027

Rule IDs

SV-109131r1_rule

Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply modify an existing account. Auditing of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail documents the creation of application user accounts and, as required, notifies administrators and/or application owners exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/auditing mechanisms meeting or exceeding access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.

Checks: C-98877r1_chk

Examine the configuration. Verify that the Central Log Server is configured to automatically audit account modification. If the Central Log Server is not configured to automatically audit account modification, this is a finding.

Fix: F-105711r1_fix

Configure the Central Log Server to automatically audit account modification.

b

The Central Log Server must automatically audit account disabling actions.

AC-2 - Medium - CCI-001404 - V-100029 - SV-109133r1_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001404

Version

SRG-APP-000028-AU-000600

Vuln IDs

V-100029

Rule IDs

SV-109133r1_rule

When application accounts are disabled, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to disable authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account disabling actions provides logging that can be used for forensic purposes. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/audit mechanisms meeting or exceeding access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.

Checks: C-98879r1_chk

Examine the configuration. Verify that the Central Log Server is configured to automatically audit account disabling. If the Central Log Server is not configured to automatically audit account disabling, this is a finding.

Fix: F-105713r1_fix

Configure the Central Log Server to automatically audit account disabling.

b

The Central Log Server must automatically audit account removal actions.

AC-2 - Medium - CCI-001405 - V-100031 - SV-109135r1_rule

RMF Control

AC-2

Severity

M

CCI

CCI-001405

Version

SRG-APP-000029-AU-000610

Vuln IDs

V-100031

Rule IDs

SV-109135r1_rule

When application accounts are removed, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to remove authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account removal actions provides logging that can be used for forensic purposes. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/audit mechanisms meeting or exceeding access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.

Checks: C-98881r1_chk

Examine the configuration. Verify that the Central Log Server is configured to automatically audit account removal. If the Central Log Server is not configured to automatically audit account removal, this is a finding.

Fix: F-105715r1_fix

Configure the Central Log Server to automatically audit account removal.

b

The Central Log Server must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.

AC-7 - Medium - CCI-000044 - V-100033 - SV-109137r1_rule

RMF Control

AC-7

Severity

M

CCI

CCI-000044

Version

SRG-APP-000065-AU-000240

Vuln IDs

V-100033

Rule IDs

SV-109137r1_rule

By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.

Checks: C-98883r1_chk

Examine the configuration. Verify that the Central Log Server is configured to lock out the account after 3 consecutive invalid attempts during a 15 minute period. If the Central Log Server is not configured to lock out the account after 3 consecutive invalid attempts in 15 minutes, this is a finding.

Fix: F-105717r1_fix

Configure the Central Log Server to lock out the account after 3 consecutive invalid attempts during a 15 minute period.

b

The Central Log Server must automatically lock the account until the locked account is released by an administrator when three unsuccessful login attempts in 15 minutes are exceeded.

AC-7 - Medium - CCI-002238 - V-100035 - SV-109139r1_rule

RMF Control

AC-7

Severity

M

CCI

CCI-002238

Version

SRG-APP-000345-AU-000400

Vuln IDs

V-100035

Rule IDs

SV-109139r1_rule

By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.

Checks: C-98885r1_chk

Examine the configuration. Verify that the Central Log Server is configured to lock out the account until released by an administrator when 3 consecutive invalid attempts during a 15 minute period is exceeded. If the Central Log Server is not configured to lock out the account until released by an administrator when 3 consecutive invalid attempts in 15 minutes is exceeded, this is a finding.

Fix: F-105719r1_fix

Configure the Central Log Server to lock out the account until released by an administrator when 3 consecutive invalid attempts during a 15 minute period is exceeded.

a

The Central Log Server must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the Central Log Server.

AC-8 - Low - CCI-000048 - V-100037 - SV-109141r1_rule

RMF Control

AC-8

Severity

L

CCI

CCI-000048

Version

SRG-APP-000068-AU-000035

Vuln IDs

V-100037

Rule IDs

SV-109141r1_rule

Display of the DoD-approved use notification before granting access to the application 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 and are not required when such human interfaces do not exist. The banner must be formatted in accordance with DTM-08-060. Use the following verbiage for applications that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

Checks: C-98887r1_chk

Examine the configuration. Verify that the Central Log Server is configured to display the Mandatory DoD Notice and Consent Banner before granting access to the Central Log Server. If the Central Log Server is not configured to display the Mandatory DoD Notice and Consent Banner, this is a finding.

Fix: F-105721r1_fix

Configure the Central Log Server to display the Mandatory DoD Notice and Consent Banner before granting access to the Central Log Server.

a

The Central Log Server must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.

AC-8 - Low - CCI-000050 - V-100039 - SV-109143r1_rule

RMF Control

AC-8

Severity

L

CCI

CCI-000050

Version

SRG-APP-000069-AU-000420

Vuln IDs

V-100039

Rule IDs

SV-109143r1_rule

The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. To establish acceptance of the application usage policy, a click-through banner at application logon is required. The application must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".

Checks: C-98889r1_chk

Examine the configuration. Verify that the Central Log Server is configured to retain the Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions. If the Central Log Server is not configured to retain the Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions, this is a finding.

Fix: F-105723r1_fix

Configure the Central Log Server to retain the Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions.

b

The Central Log Server must generate audit records when successful/unsuccessful logon attempts occur.

AU-12 - Medium - CCI-000172 - V-100041 - SV-109145r1_rule

RMF Control

AU-12

Severity

M

CCI

CCI-000172

Version

SRG-APP-000503-AU-000280

Vuln IDs

V-100041

Rule IDs

SV-109145r1_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-98891r1_chk

Examine the configuration. Verify that the Central Log Server generates audit records when successful/unsuccessful logon attempts occur. If the Central Log Server is not configured to generate audit records when successful/unsuccessful logon attempts occur, this is a finding.

Fix: F-105725r1_fix

Configure the Central Log Server to generate audit records when successful/unsuccessful logon attempts occur.

a

The Central Log Server must initiate session auditing upon startup.

AU-14 - Low - CCI-001464 - V-100043 - SV-109147r1_rule

RMF Control

AU-14

Severity

L

CCI

CCI-001464

Version

SRG-APP-000092-AU-000670

Vuln IDs

V-100043

Rule IDs

SV-109147r1_rule

If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.

Checks: C-98893r1_chk

Examine the configuration. Verify that the Central Log Server initiates session logging upon startup. If the Central Log Server is not configured to initiate session logging upon startup, this is a finding.

Fix: F-105727r1_fix

Configure the Central Log Server to initiate session logging upon startup.

a

The Central Log Server must produce audit records containing information to establish what type of events occurred.

AU-3 - Low - CCI-000130 - V-100045 - SV-109149r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-000130

Version

SRG-APP-000095-AU-000680

Vuln IDs

V-100045

Rule IDs

SV-109149r1_rule

Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. 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 application.

Checks: C-98895r1_chk

Examine the configuration. Verify that the Central Log Server produces audit records containing information to establish what type of events occurred. If the Central Log Server is not configured to produce audit records containing information to establish what type of events occurred, this is a finding.

Fix: F-105729r1_fix

Configure the Central Log Server to produce audit records containing information to establish what type of events occurred.

a

The Central Log Server must produce audit records containing information to establish when (date and time) the events occurred.

AU-3 - Low - CCI-000131 - V-100047 - SV-109151r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-000131

Version

SRG-APP-000096-AU-000690

Vuln IDs

V-100047

Rule IDs

SV-109151r1_rule

Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time). 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 application.

Checks: C-98897r1_chk

Examine the configuration. Verify that the Central Log Server produces audit records containing information to establish when the events occurred. If the Central Log Server is not configured to produce audit records containing information to establish when the events occurred, this is a finding.

Fix: F-105731r1_fix

Configure the Central Log Server to produce audit records containing information to establish when the events occurred.

a

The Central Log Server must produce audit records containing information to establish where the events occurred.

AU-3 - Low - CCI-000132 - V-100049 - SV-109153r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-000132

Version

SRG-APP-000097-AU-000700

Vuln IDs

V-100049

Rule IDs

SV-109153r1_rule

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. 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 application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-98899r1_chk

Examine the configuration. Verify that the Central Log Server produces audit records containing information to establish where the events occurred. If the Central Log Server is not configured to produce audit records containing information to establish where the events occurred, this is a finding.

Fix: F-105733r1_fix

Configure the Central Log Server to produce audit records containing information to establish where the events occurred.

a

The Central Log Server must produce audit records containing information to establish the source of the events.

AU-3 - Low - CCI-000133 - V-100051 - SV-109155r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-000133

Version

SRG-APP-000098-AU-000710

Vuln IDs

V-100051

Rule IDs

SV-109155r1_rule

Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of the event. In the case of centralized logging, the source would be the application name accompanied by the host or client name. 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, particularly in the case of centralized logging. Associating information about the source of the event within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-98901r1_chk

Examine the configuration. Verify that the Central Log Server produces audit records containing information to establish the source of the events. If the Central Log Server is not configured to produce audit records containing information to establish the source of the events, this is a finding.

Fix: F-105735r1_fix

Configure the Central Log Server to produce audit records containing information to establish the source of the events.

a

The Central Log Server must produce audit records that contain information to establish the outcome of the events.

AU-3 - Low - CCI-000134 - V-100053 - SV-109157r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-000134

Version

SRG-APP-000099-AU-000720

Vuln IDs

V-100053

Rule IDs

SV-109157r1_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 information system 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-98903r1_chk

Examine the configuration. Verify that the Central Log Server produces audit records containing information to establish the outcome of the events. If the Central Log Server is not configured to produce audit records containing information to establish the outcome of the events, this is a finding.

Fix: F-105737r1_fix

Configure the Central Log Server to produce audit records containing information to establish the outcome of the events.

a

The Central Log Server must generate audit records containing information that establishes the identity of any individual or process associated with the event.

AU-3 - Low - CCI-001487 - V-100055 - SV-109159r1_rule

RMF Control

AU-3

Severity

L

CCI

CCI-001487

Version

SRG-APP-000100-AU-000730

Vuln IDs

V-100055

Rule IDs

SV-109159r1_rule

Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Event identifiers (if authenticated or otherwise known) include, but are not limited to, user database tables, primary key values, user names, or process identifiers.

Checks: C-98905r1_chk

The Central Log Server must generate audit records containing information that establishes the identity of any individual or process associated with the event.

Fix: F-105739r1_fix

Configure the Central Log Server to produce audit records containing information to establish the identity of the individual or process associated with the event.

b

The Central Log Server must protect audit information from any type of unauthorized read access.

AU-9 - Medium - CCI-000162 - V-100057 - SV-109161r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000162

Version

SRG-APP-000118-AU-000100

Vuln IDs

V-100057

Rule IDs

SV-109161r1_rule

If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage. To ensure the veracity of audit data, the information system and/or the application must protect audit information from any and all unauthorized access. This includes read, write, and copy access. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Commonly employed methods for protecting audit information include least privilege permissions as well as restricting the location and number of log file repositories. Additionally, applications with user interfaces to audit records should not allow for the unfettered manipulation of or access to those records via the application. If the application provides access to the audit data, the application becomes accountable for ensuring audit information is protected from unauthorized access. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

Checks: C-98907r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit information from any unauthorized read access. If the Central Log Server is not configured to protect audit information from any unauthorized read access, this is a finding.

Fix: F-105741r1_fix

Configure the Central Log Server to protect audit information from unauthorized read access.

b

The Central Log Server must protect audit information from unauthorized modification.

AU-9 - Medium - CCI-000163 - V-100059 - SV-109163r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000163

Version

SRG-APP-000119-AU-000110

Vuln IDs

V-100059

Rule IDs

SV-109163r1_rule

If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions, and limiting log data locations. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

Checks: C-98909r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit information from any unauthorized modification. If the Central Log Server is not configured to protect audit information from any unauthorized modification, this is a finding.

Fix: F-105743r1_fix

Configure the Central Log Server to protect audit information from unauthorized modification.

b

The Central Log Server must protect audit information from unauthorized deletion.

AU-9 - Medium - CCI-000164 - V-100061 - SV-109165r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000164

Version

SRG-APP-000120-AU-000120

Vuln IDs

V-100061

Rule IDs

SV-109165r1_rule

If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files receive the proper file system permissions utilizing file system protections, restricting access, and backing up log data to ensure log data is retained. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Audit information may include data from other applications or be included with the audit application itself.

Checks: C-98911r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit information from unauthorized deletion. If the Central Log Server is not configured to protect audit information from unauthorized deletion, this is a finding.

Fix: F-105745r1_fix

Configure the Central Log Server to protect audit information from unauthorized deletion.

b

The Central Log Server must protect audit tools from unauthorized access.

AU-9 - Medium - CCI-001493 - V-100063 - SV-109167r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001493

Version

SRG-APP-000121-AU-000130

Vuln IDs

V-100063

Rule IDs

SV-109167r1_rule

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Checks: C-98913r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit tools from unauthorized access. If the Central Log Server is not configured to protect audit tools from unauthorized access, this is a finding.

Fix: F-105747r1_fix

Configure the Central Log Server to protect audit tools from unauthorized access.

b

The Central Log Server must protect audit tools from unauthorized modification.

AU-9 - Medium - CCI-001494 - V-100065 - SV-109169r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001494

Version

SRG-APP-000122-AU-000140

Vuln IDs

V-100065

Rule IDs

SV-109169r1_rule

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the modification of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Checks: C-98915r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit tools from unauthorized modification. If the Central Log Server is not configured to protect audit tools from unauthorized modification, this is a finding.

Fix: F-105749r1_fix

Configure the Central Log Server to protect audit tools from unauthorized modification.

b

The Central Log Server must protect audit tools from unauthorized deletion.

AU-9 - Medium - CCI-001495 - V-100067 - SV-109171r1_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001495

Version

SRG-APP-000123-AU-000150

Vuln IDs

V-100067

Rule IDs

SV-109171r1_rule

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Checks: C-98917r1_chk

Examine the configuration. Verify that the Central Log Server is configured to protect audit tools from unauthorized deletion. If the Central Log Server is not configured to protect audit tools from unauthorized deletion, this is a finding.

Fix: F-105751r1_fix

Configure the Central Log Server to protect audit tools from unauthorized deletion.

b

The Central Log Server must be configured to disable non-essential capabilities.

CM-7 - Medium - CCI-000381 - V-100069 - SV-109173r1_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000381

Version

SRG-APP-000141-AU-000090

Vuln IDs

V-100069

Rule IDs

SV-109173r1_rule

It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. Applications 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 (e.g., key missions, functions). Examples of non-essential capabilities include, but are not limited to, advertising software or browser plug-ins not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.

Checks: C-98919r1_chk

Examine the configuration. Verify that the Central Log Server is configured to disable non-essential capabilities. If the Central Log Server is not configured to disable non-essential capabilities, this is a finding.

Fix: F-105753r1_fix

Configure the Central Log Server to disable non-essential capabilities.

a

The Central Log Server must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.

IA-11 - Low - CCI-002038 - V-100071 - SV-109175r1_rule

RMF Control

IA-11

Severity

L

CCI

CCI-002038

Version

SRG-APP-000389-AU-000180

Vuln IDs

V-100071

Rule IDs

SV-109175r1_rule

Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user reauthenticate. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances. (i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) When the execution of privileged functions occurs; (v) After a fixed period of time; or (vi) Periodically. Within the DoD, the minimum circumstances requiring reauthentication are privilege escalation and role changes.

Checks: C-98923r1_chk

Examine the configuration. Verify the Central Log Server requires users to reauthenticate when situations require reauthentication. If the Central Log Server is not configured to reauthenticate when necessary, this is a finding.

Fix: F-105757r1_fix

Configure the Central Log Server to reauthenticate users when situations require reauthentication.

c

The Central Log Server must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (non-legacy use).

IA-7 - High - CCI-000803 - V-100073 - SV-109177r1_rule

RMF Control

IA-7

Severity

H

CCI

CCI-000803

Version

SRG-APP-000610-AU-000050

Vuln IDs

V-100073

Rule IDs

SV-109177r1_rule

Without cryptographic integrity protections, information can be altered by unauthorized users without detection. To protect the integrity of the authenticator and authentication mechanism used for the cryptographic module used by the network device, the application, operating system, or protocol must be configured to use one of the following hash functions for hashing the password or other authenticator in accordance with SP 800-131Ar1: SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256, SHA3-224, SHA3-256, SHA3-384, and SHA3-512. For digital signature verification, SP800-131Ar1 allows SHA-1 for legacy use where needed.

Checks: C-98925r1_chk

Examine the configuration. Verify the Central Log Server is configured to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only). If the Central Log Server is not configured to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification (legacy use only), this is a finding.

Fix: F-105759r1_fix

Configure the Central Log Server to use FIPS-validated SHA-1 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification.

b

The Central Log Server must only allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions.

SC-23 - Medium - CCI-002470 - V-100075 - SV-109179r1_rule

RMF Control

SC-23

Severity

M

CCI

CCI-002470

Version

SRG-APP-000427-AU-000040

Vuln IDs

V-100075

Rule IDs

SV-109179r1_rule

Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DoD-approved CA, trust of this CA has not been established. The DoD will only accept PKI certificates obtained from a DoD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of TLS certificates. This requirement focuses on communications protection for the application session rather than for the network packet. This requirement applies to applications that utilize communications sessions. This includes, but is not limited to, web-based applications and Service-Oriented Architectures (SOA).

Checks: C-98927r1_chk

Examine the configuration. Verify the Central Log Server is configured to only allow the use of DoD PKI certificate authorities. If the Central Log Server is not configured to only allow DoD PKI certificate authorities, this is a finding.

Fix: F-105761r1_fix

Configure the Central Log Server to only allow the use of DoD PKI certificate authorities.

Added rules 30

Checks: C-80759r1_chk

Fix: F-87877r1_fix

Generate Mitigation Statement:

Checks: C-80761r1_chk

Fix: F-87879r1_fix

Generate Mitigation Statement:

Checks: C-80763r1_chk

Fix: F-87881r1_fix

Generate Mitigation Statement:

Checks: C-80765r1_chk

Fix: F-87883r1_fix

Generate Mitigation Statement:

Checks: C-80767r1_chk

Fix: F-87885r1_fix

Generate Mitigation Statement:

Checks: C-80769r1_chk

Fix: F-87887r1_fix

Generate Mitigation Statement:

Checks: C-80771r1_chk

Fix: F-87889r1_fix

Generate Mitigation Statement:

Checks: C-80775r1_chk

Fix: F-87891r1_fix

Generate Mitigation Statement:

Checks: C-80777r1_chk

Fix: F-87893r1_fix

Generate Mitigation Statement:

Checks: C-80779r1_chk

Fix: F-87895r1_fix

Generate Mitigation Statement:

Checks: C-80783r1_chk

Fix: F-87899r1_fix

Generate Mitigation Statement:

Checks: C-80785r1_chk

Fix: F-87901r1_fix

Generate Mitigation Statement:

Checks: C-80787r1_chk

Fix: F-87903r1_fix

Generate Mitigation Statement:

Checks: C-80789r1_chk

Fix: F-87905r1_fix

Generate Mitigation Statement:

Checks: C-80791r1_chk

Fix: F-87907r1_fix

Generate Mitigation Statement:

Checks: C-80793r1_chk

Fix: F-87909r1_fix

Generate Mitigation Statement:

Checks: C-80795r1_chk

Fix: F-87911r1_fix

Generate Mitigation Statement:

Checks: C-80799r1_chk

Fix: F-87913r1_fix

Generate Mitigation Statement:

Checks: C-80801r1_chk

Fix: F-87915r1_fix

Generate Mitigation Statement:

Checks: C-80803r1_chk

Fix: F-87917r1_fix

Generate Mitigation Statement:

Checks: C-80807r1_chk

Fix: F-87921r1_fix

Generate Mitigation Statement:

Checks: C-80809r1_chk

Fix: F-87923r1_fix

Generate Mitigation Statement:

Checks: C-80811r1_chk

Fix: F-87925r1_fix

Generate Mitigation Statement:

Checks: C-80813r1_chk

Fix: F-87927r1_fix

Generate Mitigation Statement:

Checks: C-80815r1_chk

Fix: F-87929r1_fix

Generate Mitigation Statement:

Checks: C-80817r1_chk

Fix: F-87969r1_fix

Generate Mitigation Statement:

Checks: C-80819r1_chk