Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Central Log Server Security Requirements Guide

V2R1 · · · Released 23 Jul 2021 · 101 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Requirements Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V1R4 · 24 Jul 2020 +101 −102

Comparison against the immediately-prior release (V1R4). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 101

  • V-206447 High 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.
  • V-206448 Medium 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).
  • V-206449 Low The Central Log Server must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage.
  • V-206450 Low 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.
  • V-206451 Medium 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.
  • V-206452 Low 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.
  • V-206453 Medium The Central Log Server must be configured to retain the DoD-defined attributes of the log records sent by the devices and hosts.
  • V-206454 Low 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.
  • V-206455 Low 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.
  • V-206456 Low 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.
  • V-206457 Low The Central Log Server must be configured to use internal system clocks to generate time stamps for log records.
  • V-206458 Low 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.
  • V-206459 Low The Central Log Server system backups must be retained for a minimum of 5 years for SAMLI and a minimum of 7 days for non-SAMI on media capable of guaranteeing file integrity for the minimum applicable information retention period.
  • V-206460 High The Central Log Server must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
  • V-206461 Medium The Central Log Server must use multifactor authentication for network access to privileged user accounts.
  • V-206462 Medium The Central Log Server must use multifactor authentication for network access to non-privileged user accounts.
  • V-206463 Medium The Central Log Server must use multifactor authentication for local access using privileged user accounts.
  • V-206464 Medium 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.
  • V-206465 Medium 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.
  • V-206466 Medium The Central Log Server must disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity.
  • V-206467 Medium The Central Log Server must be configured to enforce a minimum 15-character password length.
  • V-206468 Low The Central Log Server must be configured to prohibit password reuse for a minimum of five generations.
  • V-206469 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one upper-case character be used.
  • V-206470 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one lower-case character be used.
  • V-206471 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one numeric character be used.
  • V-206472 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one special character be used.
  • V-206473 Low 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.
  • V-206474 High For accounts using password authentication, the Central Log Server must be configured to store only cryptographic representations of passwords.
  • V-206475 High 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.
  • V-206476 Low The Central Log Server must be configured to enforce 24 hours/1 day as the minimum password lifetime.
  • V-206477 Low The Central Log Server must be configured to enforce a 60-day maximum password lifetime restriction.
  • V-206478 High 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.
  • V-206479 High The Central Log Server, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
  • V-206480 Low The Central Log Server must map the authenticated identity to the individual user or group account for PKI-based authentication.
  • V-206481 High The Central Log Server must obfuscate authentication information during the authentication process so that the authentication is not visible.
  • V-206482 High 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).
  • V-206483 Medium The Central Log Server must be configured to perform audit reduction that supports on-demand reporting requirements.
  • V-206484 Low 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.
  • V-206485 Low 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.
  • V-206486 Low 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.
  • V-206490 Low The Central Log Server must be configured for centralized management of the events repository for the purposes of configuration, analysis, and reporting.
  • V-206491 Medium The Central Log Server must be configured to off-load log records onto a different system or media than the system being audited.
  • V-206492 Low 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.
  • V-206493 Low 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.
  • V-206494 Low 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.
  • V-206495 Low 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.
  • V-206496 Low 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.
  • V-206497 Medium The Central Log Server must be configured to perform audit reduction that supports on-demand audit review and analysis.
  • V-206498 Low The Central Log Server must be configured to perform audit reduction that supports after-the-fact investigations of security incidents.
  • V-206499 Low The Central Log Server must be configured to generate on-demand audit review and analysis reports.
  • V-206500 Low The Central Log Server must be configured to generate reports that support on-demand reporting requirements.
  • V-206501 Low The Central Log Server must be configured to generate reports that support after-the-fact investigations of security incidents.
  • V-206502 Low The Central Log Server must be configured to perform audit reduction that does not alter original content or time ordering of log records.
  • V-206503 Low The Central Log Server must be configured to generate reports that do not alter original content or time ordering of log records.
  • V-206504 Low 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).
  • V-206505 Low 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.
  • V-206506 Medium The Central Log Server must be configured to accept the DoD CAC credential to support identity management and personal authentication.
  • V-206507 Medium The Central Log Server must be configured to electronically verify the DoD CAC credential.
  • V-206508 Medium 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.
  • V-206509 High The Central Log Server must be configured to protect the confidentiality and integrity of transmitted information.
  • V-206510 High 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.
  • V-206511 Low The Central Log Server must be configured to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum.
  • V-206512 Medium 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.
  • V-206513 Medium The Central Log Server that aggregates log records from hosts and devices must be configured to use TCP for transmission.
  • V-206514 Medium 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.
  • V-206515 Medium 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).
  • V-206516 Medium For devices and hosts within the scope of coverage, the Central Log Server must be configured to automatically aggregate events that indicate account actions.
  • V-206517 Medium 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.
  • V-206518 Medium 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.
  • V-221900 Medium The Central Log Server must automatically audit account creation.
  • V-221901 Medium The Central Log Server must automatically audit account modification.
  • V-221902 Medium The Central Log Server must automatically audit account disabling actions.
  • V-221903 Medium The Central Log Server must automatically audit account removal actions.
  • V-221904 Medium The Central Log Server must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
  • V-221905 Low The Central Log Server must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the Central Log Server.
  • V-221906 Low 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.
  • V-221907 Low The Central Log Server must initiate session auditing upon startup.
  • V-221908 Low The Central Log Server must produce audit records containing information to establish what type of events occurred.
  • V-221909 Low The Central Log Server must produce audit records containing information to establish when (date and time) the events occurred.
  • V-221910 Low The Central Log Server must produce audit records containing information to establish where the events occurred.
  • V-221911 Low The Central Log Server must produce audit records containing information to establish the source of the events.
  • V-221912 Low The Central Log Server must produce audit records that contain information to establish the outcome of the events.
  • V-221913 Low The Central Log Server must generate audit records containing information that establishes the identity of any individual or process associated with the event.
  • V-221914 Medium The Central Log Server must protect audit information from any type of unauthorized read access.
  • V-221915 Medium The Central Log Server must protect audit information from unauthorized modification.
  • V-221916 Medium The Central Log Server must protect audit information from unauthorized deletion.
  • V-221917 Medium The Central Log Server must protect audit tools from unauthorized access.
  • V-221918 Medium The Central Log Server must protect audit tools from unauthorized modification.
  • V-221919 Medium The Central Log Server must protect audit tools from unauthorized deletion.
  • V-221920 Medium The Central Log Server must be configured to disable non-essential capabilities.
  • V-221921 Low The Central Log Server must notify system administrators and ISSO when accounts are created.
  • V-221922 Medium The Central Log Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
  • V-221923 Medium The Central Log Server must provide a logout capability for user initiated communication session.
  • V-221924 Low The Central Log Server must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.
  • V-221925 Medium 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.
  • V-221926 Low The Central Log Server must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.
  • V-221927 Medium The Central Log Server must only allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions.
  • V-221928 Medium The Central Log Server must generate audit records when successful/unsuccessful logon attempts occur.
  • V-221929 High The Central Log Server must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (non-legacy use).
  • V-241819 Low 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.
  • V-241820 Low 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.

Removed rules 102

  • V-100015 Medium The Central Log Server must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
  • V-100017 Medium The Central Log Server must provide a logout capability for user initiated communication session.
  • V-100019 Low The Central Log Server must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.
  • V-100021 Low The Central Log Server must notify system administrators and ISSO when accounts are created.
  • V-100025 Medium The Central Log Server must automatically audit account creation.
  • V-100027 Medium The Central Log Server must automatically audit account modification.
  • V-100029 Medium The Central Log Server must automatically audit account disabling actions.
  • V-100031 Medium The Central Log Server must automatically audit account removal actions.
  • V-100033 Medium The Central Log Server must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
  • V-100035 Medium 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.
  • V-100037 Low The Central Log Server must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the Central Log Server.
  • V-100039 Low 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.
  • V-100041 Medium The Central Log Server must generate audit records when successful/unsuccessful logon attempts occur.
  • V-100043 Low The Central Log Server must initiate session auditing upon startup.
  • V-100045 Low The Central Log Server must produce audit records containing information to establish what type of events occurred.
  • V-100047 Low The Central Log Server must produce audit records containing information to establish when (date and time) the events occurred.
  • V-100049 Low The Central Log Server must produce audit records containing information to establish where the events occurred.
  • V-100051 Low The Central Log Server must produce audit records containing information to establish the source of the events.
  • V-100053 Low The Central Log Server must produce audit records that contain information to establish the outcome of the events.
  • V-100055 Low The Central Log Server must generate audit records containing information that establishes the identity of any individual or process associated with the event.
  • V-100057 Medium The Central Log Server must protect audit information from any type of unauthorized read access.
  • V-100059 Medium The Central Log Server must protect audit information from unauthorized modification.
  • V-100061 Medium The Central Log Server must protect audit information from unauthorized deletion.
  • V-100063 Medium The Central Log Server must protect audit tools from unauthorized access.
  • V-100065 Medium The Central Log Server must protect audit tools from unauthorized modification.
  • V-100067 Medium The Central Log Server must protect audit tools from unauthorized deletion.
  • V-100069 Medium The Central Log Server must be configured to disable non-essential capabilities.
  • V-100071 Low The Central Log Server must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.
  • V-100073 High The Central Log Server must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (non-legacy use).
  • V-100075 Medium The Central Log Server must only allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions.
  • V-81105 Medium 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).
  • V-81107 Low The Central Log Server must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage.
  • V-81109 Low 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.
  • V-81111 Medium 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.
  • V-81113 Low 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.
  • V-81115 Medium The Central Log Server must be configured to retain the DoD-defined attributes of the log records sent by the devices and hosts.
  • V-81117 Low 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.
  • V-81119 Low 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.
  • V-81121 Low 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.
  • V-81123 Low The Central Log Server must be configured to use internal system clocks to generate time stamps for log records.
  • V-81125 Low 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.
  • V-81127 Low The Central Log Server system backups must be retained for a minimum of 5 years for SAML and a minimum of 7 days for on media capable of guaranteeing file integrity for a minimum of five years (SAML) and 7 days (non-SAML).
  • V-81129 Medium The Central Log Server must be configured to perform audit reduction that supports on-demand reporting requirements.
  • V-81131 Low 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.
  • V-81133 Low 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.
  • V-81135 Low 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.
  • V-81137 Low 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.
  • V-81139 Low 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.
  • V-81141 Low 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.
  • V-81143 Low The Central Log Server must be configured for centralized management of the events repository for the purposes of configuration, analysis, and reporting.
  • V-81145 Medium The Central Log Server must be configured to off-load log records onto a different system or media than the system being audited.
  • V-81147 Low 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.
  • V-81149 Low 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.
  • V-81151 Low 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.
  • V-81153 Low 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.
  • V-81155 Low 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.
  • V-81157 Medium The Central Log Server must be configured to perform audit reduction that supports on-demand audit review and analysis.
  • V-81159 Low The Central Log Server must be configured to perform audit reduction that supports after-the-fact investigations of security incidents.
  • V-81161 Low The Central Log Server must be configured to generate on-demand audit review and analysis reports.
  • V-81163 Low The Central Log Server must be configured to generate reports that support on-demand reporting requirements.
  • V-81165 Low The Central Log Server must be configured to generate reports that support after-the-fact investigations of security incidents.
  • V-81167 Low The Central Log Server must be configured to perform audit reduction that does not alter original content or time ordering of log records.
  • V-81169 Low The Central Log Server must be configured to generate reports that do not alter original content or time ordering of log records.
  • V-81171 Low 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).
  • V-81173 Low 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.
  • V-81177 Low The Central Log Server must be configured to off-load interconnected systems in real time and off-load standalone systems weekly, at a minimum.
  • V-81179 Medium 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.
  • V-81181 Medium The Central Log Server that aggregates log records from hosts and devices must be configured to use TCP for transmission.
  • V-81183 Medium 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.
  • V-81185 Medium 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).
  • V-81187 Medium For devices and hosts within the scope of coverage, the Central Log Server must be configured to automatically aggregate events that indicate account actions.
  • V-81189 Medium 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.
  • V-81191 Medium 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.
  • V-81281 High The Central Log Server must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
  • V-81283 High For accounts using password authentication, the Central Log Server must be configured to store only cryptographic representations of passwords.
  • V-81285 High 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.
  • V-81287 High 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.
  • V-81289 High The Central Log Server, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
  • V-81291 High The Central Log Server must obfuscate authentication information during the authentication process so that the authentication is not visible.
  • V-81295 High 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).
  • V-81297 High 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.
  • V-81301 High The Central Log Server must be configured to protect the confidentiality and integrity of transmitted information.
  • V-81303 High 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.
  • V-81307 Medium The Central Log Server must use multifactor authentication for network access to privileged user accounts.
  • V-81309 Medium The Central Log Server must use multifactor authentication for network access to non-privileged user accounts.
  • V-81313 Medium The Central Log Server must use multifactor authentication for local access using privileged user accounts.
  • V-81315 Medium 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.
  • V-81317 Medium 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.
  • V-81319 Medium The Central Log Server must disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity.
  • V-81321 Medium The Central Log Server must be configured to enforce a minimum 15-character password length.
  • V-81323 Medium The Central Log Server must be configured to accept the DoD CAC credential to support identity management and personal authentication.
  • V-81327 Medium The Central Log Server must be configured to electronically verify the DoD CAC credential.
  • V-81331 Medium 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.
  • V-81335 Low The Central Log Server must be configured to prohibit password reuse for a minimum of five generations.
  • V-81337 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one upper-case character be used.
  • V-81339 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one lower-case character be used.
  • V-81345 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one numeric character be used.
  • V-81349 Low The Central Log Server must be configured to enforce password complexity by requiring that at least one special character be used.
  • V-81353 Low 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.
  • V-81355 Low The Central Log Server must be configured to enforce 24 hours/1 day as the minimum password lifetime.
  • V-81359 Low The Central Log Server must be configured to enforce a 60-day maximum password lifetime restriction.
  • V-81363 Low The Central Log Server must map the authenticated identity to the individual user or group account for PKI-based authentication.
Sort by
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-206447 - SV-206447r395499_rule
RMF Control
AC-3
Severity
H
CCI
CCI-000213
Version
SRG-APP-000033-AU-001610
Vuln IDs
  • V-206447
  • V-81297
Rule IDs
  • SV-206447r395499_rule
  • SV-96011
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-6707r285585_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-6707r285586_fix

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

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-206448 - SV-206448r395691_rule
RMF Control
AU-10
Severity
M
CCI
CCI-000166
Version
SRG-APP-000080-AU-000010
Vuln IDs
  • V-206448
  • V-81105
Rule IDs
  • SV-206448r395691_rule
  • SV-95819
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-6708r285588_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-6708r285589_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-206449 - SV-206449r395700_rule
RMF Control
AU-12
Severity
L
CCI
CCI-000174
Version
SRG-APP-000086-AU-000020
Vuln IDs
  • V-206449
  • V-81107
Rule IDs
  • SV-206449r395700_rule
  • SV-95821
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-6709r285591_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-6709r285592_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-206450 - SV-206450r395700_rule
RMF Control
AU-12
Severity
L
CCI
CCI-000174
Version
SRG-APP-000086-AU-000030
Vuln IDs
  • V-206450
  • V-81109
Rule IDs
  • SV-206450r395700_rule
  • SV-95823
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-6710r285594_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-6710r285595_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-206451 - SV-206451r395700_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000174
Version
SRG-APP-000086-AU-000390
Vuln IDs
  • V-206451
  • V-81111
Rule IDs
  • SV-206451r395700_rule
  • SV-95825
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-6711r285597_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-6711r285598_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-206452 - SV-206452r395703_rule
RMF Control
AU-12
Severity
L
CCI
CCI-001353
Version
SRG-APP-000088-AU-000040
Vuln IDs
  • V-206452
  • V-81113
Rule IDs
  • SV-206452r395703_rule
  • SV-95827
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-6712r285600_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-6712r285601_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-206453 - SV-206453r395706_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
SRG-APP-000089-AU-000400
Vuln IDs
  • V-206453
  • V-81115
Rule IDs
  • SV-206453r395706_rule
  • SV-95829
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-6713r285603_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-6713r285604_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-206454 - SV-206454r395709_rule
RMF Control
AU-12
Severity
L
CCI
CCI-000171
Version
SRG-APP-000090-AU-000070
Vuln IDs
  • V-206454
  • V-81117
Rule IDs
  • SV-206454r395709_rule
  • SV-95831
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-6714r285606_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-6714r285607_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-206455 - SV-206455r395808_rule
RMF Control
AU-6
Severity
L
CCI
CCI-000154
Version
SRG-APP-000111-AU-000150
Vuln IDs
  • V-206455
  • V-81119
Rule IDs
  • SV-206455r395808_rule
  • SV-95833
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-6715r285609_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-6715r285610_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-206456 - SV-206456r395814_rule
RMF Control
AU-7
Severity
L
CCI
CCI-000158
Version
SRG-APP-000115-AU-000160
Vuln IDs
  • V-206456
  • V-81121
Rule IDs
  • SV-206456r395814_rule
  • SV-95835
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-6716r285612_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-6716r285613_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-206457 - SV-206457r395817_rule
RMF Control
AU-8
Severity
L
CCI
CCI-000159
Version
SRG-APP-000116-AU-000270
Vuln IDs
  • V-206457
  • V-81123
Rule IDs
  • SV-206457r395817_rule
  • SV-95837
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-6717r285615_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-6717r285616_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-206458 - SV-206458r395838_rule
RMF Control
AU-9
Severity
L
CCI
CCI-001348
Version
SRG-APP-000125-AU-000300
Vuln IDs
  • V-206458
  • V-81125
Rule IDs
  • SV-206458r395838_rule
  • SV-95839
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-6718r285618_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-6718r285619_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 retained for a minimum of 5 years for SAMLI and a minimum of 7 days for non-SAMI on media capable of guaranteeing file integrity for the minimum applicable information retention period.
AU-11 - Low - CCI-000167 - V-206459 - SV-206459r767007_rule
RMF Control
AU-11
Severity
L
CCI
CCI-000167
Version
SRG-APP-000125-AU-000310
Vuln IDs
  • V-206459
  • V-81127
Rule IDs
  • SV-206459r767007_rule
  • SV-95841
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-6719r767005_chk

Review the SSP, backup media documentation, and system backup 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 does not retain backups for a minimum of five years for SAMI and a minimum of seven days for non-SAMI, this is a finding. If the Central Log Server system backups are not stored on appropriate media capable of guaranteeing file integrity for a minimum of five years for systems retaining SAMI, this is a finding.

Fix: F-6719r767006_fix

Configure the Central Log Server to retain backups of system information for a minimum of five years for SAMI and a minimum of seven days for non-SAMI. Select backup media that guarantees file integrity for a minimum of five years for systems retaining SAMI. Document the required retention period in the SSP.

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-206460 - SV-206460r395859_rule
RMF Control
IA-2
Severity
H
CCI
CCI-000764
Version
SRG-APP-000148-AU-002270
Vuln IDs
  • V-206460
  • V-81281
Rule IDs
  • SV-206460r395859_rule
  • SV-95995
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-6720r285624_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-6720r285625_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.

b
The Central Log Server must use multifactor authentication for network access to privileged user accounts.
IA-2 - Medium - CCI-000765 - V-206461 - SV-206461r397438_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000765
Version
SRG-APP-000149-AU-002280
Vuln IDs
  • V-206461
  • V-81307
Rule IDs
  • SV-206461r397438_rule
  • SV-96021
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-6721r285627_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-6721r285628_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-206462 - SV-206462r397441_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000766
Version
SRG-APP-000150-AU-002320
Vuln IDs
  • V-206462
  • V-81309
Rule IDs
  • SV-206462r397441_rule
  • SV-96023
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-6722r285630_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-6722r285631_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-206463 - SV-206463r397444_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000767
Version
SRG-APP-000151-AU-002330
Vuln IDs
  • V-206463
  • V-81313
Rule IDs
  • SV-206463r397444_rule
  • SV-96027
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-6723r285633_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-6723r285634_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-206464 - SV-206464r397453_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001936
Version
SRG-APP-000154-AU-002360
Vuln IDs
  • V-206464
  • V-81315
Rule IDs
  • SV-206464r397453_rule
  • SV-96029
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-6724r285636_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-6724r285637_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-206465 - SV-206465r397459_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001941
Version
SRG-APP-000156-AU-002380
Vuln IDs
  • V-206465
  • V-81317
Rule IDs
  • SV-206465r397459_rule
  • SV-96031
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-6725r285639_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-6725r285640_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-206466 - SV-206466r397498_rule
RMF Control
IA-4
Severity
M
CCI
CCI-000795
Version
SRG-APP-000163-AU-002470
Vuln IDs
  • V-206466
  • V-81319
Rule IDs
  • SV-206466r397498_rule
  • SV-96033
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-6726r285642_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-6726r285643_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-206467 - SV-206467r397501_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000205
Version
SRG-APP-000164-AU-002480
Vuln IDs
  • V-206467
  • V-81321
Rule IDs
  • SV-206467r397501_rule
  • SV-96035
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-6727r285645_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-6727r285646_fix

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

a
The Central Log Server must be configured to prohibit password reuse for a minimum of five generations.
IA-5 - Low - CCI-000200 - V-206468 - SV-206468r397504_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000200
Version
SRG-APP-000165-AU-002580
Vuln IDs
  • V-206468
  • V-81335
Rule IDs
  • SV-206468r397504_rule
  • SV-96049
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-6728r285648_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-6728r285649_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-206469 - SV-206469r397507_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000192
Version
SRG-APP-000166-AU-002490
Vuln IDs
  • V-206469
  • V-81337
Rule IDs
  • SV-206469r397507_rule
  • SV-96051
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-6729r285651_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-6729r285652_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-206470 - SV-206470r397510_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000193
Version
SRG-APP-000167-AU-002500
Vuln IDs
  • V-206470
  • V-81339
Rule IDs
  • SV-206470r397510_rule
  • SV-96053
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-6730r285654_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-6730r285655_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-206471 - SV-206471r397513_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000194
Version
SRG-APP-000168-AU-002510
Vuln IDs
  • V-206471
  • V-81345
Rule IDs
  • SV-206471r397513_rule
  • SV-96059
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-6731r285657_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-6731r285658_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-206472 - SV-206472r397516_rule
RMF Control
IA-5
Severity
L
CCI
CCI-001619
Version
SRG-APP-000169-AU-002520
Vuln IDs
  • V-206472
  • V-81349
Rule IDs
  • SV-206472r397516_rule
  • SV-96063
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-6732r285660_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-6732r285661_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-206473 - SV-206473r397519_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000195
Version
SRG-APP-000170-AU-002530
Vuln IDs
  • V-206473
  • V-81353
Rule IDs
  • SV-206473r397519_rule
  • SV-96067
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-6733r285663_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-6733r285664_fix

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

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-206474 - SV-206474r397522_rule
RMF Control
IA-5
Severity
H
CCI
CCI-000196
Version
SRG-APP-000171-AU-002540
Vuln IDs
  • V-206474
  • V-81283
Rule IDs
  • SV-206474r397522_rule
  • SV-95997
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-6734r285666_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-6734r285667_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-206475 - SV-206475r397525_rule
RMF Control
IA-5
Severity
H
CCI
CCI-000197
Version
SRG-APP-000172-AU-002550
Vuln IDs
  • V-206475
  • V-81285
Rule IDs
  • SV-206475r397525_rule
  • SV-95999
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-6735r285669_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-6735r285670_fix

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

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-206476 - SV-206476r397588_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000198
Version
SRG-APP-000173-AU-002560
Vuln IDs
  • V-206476
  • V-81355
Rule IDs
  • SV-206476r397588_rule
  • SV-96069
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-6736r285672_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-6736r285673_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-206477 - SV-206477r397591_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000199
Version
SRG-APP-000174-AU-002570
Vuln IDs
  • V-206477
  • V-81359
Rule IDs
  • SV-206477r397591_rule
  • SV-96073
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-6737r285675_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-6737r285676_fix

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

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-206478 - SV-206478r397594_rule
RMF Control
IA-5
Severity
H
CCI
CCI-000185
Version
SRG-APP-000175-AU-002630
Vuln IDs
  • V-206478
  • V-81287
Rule IDs
  • SV-206478r397594_rule
  • SV-96001
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-6738r285678_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-6738r285679_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-206479 - SV-206479r397597_rule
RMF Control
IA-5
Severity
H
CCI
CCI-000186
Version
SRG-APP-000176-AU-002640
Vuln IDs
  • V-206479
  • V-81289
Rule IDs
  • SV-206479r397597_rule
  • SV-96003
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-6739r285681_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-6739r285682_fix

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

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-206480 - SV-206480r397600_rule
RMF Control
IA-5
Severity
L
CCI
CCI-000187
Version
SRG-APP-000177-AU-002650
Vuln IDs
  • V-206480
  • V-81363
Rule IDs
  • SV-206480r397600_rule
  • SV-96077
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-6740r285684_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-6740r285685_fix

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

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-206481 - SV-206481r397603_rule
RMF Control
IA-6
Severity
H
CCI
CCI-000206
Version
SRG-APP-000178-AU-002660
Vuln IDs
  • V-206481
  • V-81291
Rule IDs
  • SV-206481r397603_rule
  • SV-96005
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-6741r285687_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-6741r285688_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-206482 - SV-206482r397606_rule
RMF Control
IA-7
Severity
H
CCI
CCI-000803
Version
SRG-APP-000179-AU-002670
Vuln IDs
  • V-206482
  • V-81295
Rule IDs
  • SV-206482r397606_rule
  • SV-96009
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-6742r285690_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-6742r285691_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).

b
The Central Log Server must be configured to perform audit reduction that supports on-demand reporting requirements.
AU-7 - Medium - CCI-001876 - V-206483 - SV-206483r397612_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001876
Version
SRG-APP-000181-AU-000200
Vuln IDs
  • V-206483
  • V-81129
Rule IDs
  • SV-206483r397612_rule
  • SV-95843
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-6743r285693_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-6743r285694_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-206484 - SV-206484r399514_rule
RMF Control
AC-2
Severity
L
CCI
CCI-001684
Version
SRG-APP-000292-AU-000420
Vuln IDs
  • V-206484
  • V-81131
Rule IDs
  • SV-206484r399514_rule
  • SV-95845
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-6744r285696_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-6744r285697_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-206485 - SV-206485r399517_rule
RMF Control
AC-2
Severity
L
CCI
CCI-001685
Version
SRG-APP-000293-AU-000430
Vuln IDs
  • V-206485
  • V-81133
Rule IDs
  • SV-206485r399517_rule
  • SV-95847
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-6745r285699_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-6745r285700_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-206486 - SV-206486r399520_rule
RMF Control
AC-2
Severity
L
CCI
CCI-001686
Version
SRG-APP-000294-AU-000440
Vuln IDs
  • V-206486
  • V-81135
Rule IDs
  • SV-206486r399520_rule
  • SV-95849
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-6746r285702_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-6746r285703_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 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-206490 - SV-206490r401227_rule
RMF Control
AU-3
Severity
L
CCI
CCI-001844
Version
SRG-APP-000356-AU-000090
Vuln IDs
  • V-206490
  • V-81143
Rule IDs
  • SV-206490r401227_rule
  • SV-95857
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-6750r285711_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-6750r285712_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-206491 - SV-206491r399880_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001851
Version
SRG-APP-000358-AU-000100
Vuln IDs
  • V-206491
  • V-81145
Rule IDs
  • SV-206491r399880_rule
  • SV-95859
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-6751r285714_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-6751r285715_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-206492 - SV-206492r399883_rule
RMF Control
AU-5
Severity
L
CCI
CCI-001855
Version
SRG-APP-000359-AU-000120
Vuln IDs
  • V-206492
  • V-81147
Rule IDs
  • SV-206492r399883_rule
  • SV-95861
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-6752r285717_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-6752r285718_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-206493 - SV-206493r399886_rule
RMF Control
AU-5
Severity
L
CCI
CCI-001858
Version
SRG-APP-000360-AU-000130
Vuln IDs
  • V-206493
  • V-81149
Rule IDs
  • SV-206493r399886_rule
  • SV-95863
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-6753r285720_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-6753r285721_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-206494 - SV-206494r399889_rule
RMF Control
AU-5
Severity
L
CCI
CCI-001861
Version
SRG-APP-000361-AU-000140
Vuln IDs
  • V-206494
  • V-81151
Rule IDs
  • SV-206494r399889_rule
  • SV-95865
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-6754r285723_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-6754r285724_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-206495 - SV-206495r399892_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001886
Version
SRG-APP-000362-AU-000170
Vuln IDs
  • V-206495
  • V-81153
Rule IDs
  • SV-206495r399892_rule
  • SV-95867
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-6755r285726_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-6755r285727_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-206496 - SV-206496r399895_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001887
Version
SRG-APP-000363-AU-000180
Vuln IDs
  • V-206496
  • V-81155
Rule IDs
  • SV-206496r399895_rule
  • SV-95869
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-6756r285729_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-6756r285730_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-206497 - SV-206497r399898_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001875
Version
SRG-APP-000364-AU-000190
Vuln IDs
  • V-206497
  • V-81157
Rule IDs
  • SV-206497r399898_rule
  • SV-95871
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-6757r285732_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-6757r285733_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-206498 - SV-206498r399901_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001877
Version
SRG-APP-000365-AU-000210
Vuln IDs
  • V-206498
  • V-81159
Rule IDs
  • SV-206498r399901_rule
  • SV-95873
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-6758r285735_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-6758r285736_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-206499 - SV-206499r399904_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001878
Version
SRG-APP-000366-AU-000220
Vuln IDs
  • V-206499
  • V-81161
Rule IDs
  • SV-206499r399904_rule
  • SV-95875
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-6759r285738_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-6759r285739_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-206500 - SV-206500r399907_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001879
Version
SRG-APP-000367-AU-000230
Vuln IDs
  • V-206500
  • V-81163
Rule IDs
  • SV-206500r399907_rule
  • SV-95877
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-6760r285741_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-6760r285742_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-206501 - SV-206501r399910_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001880
Version
SRG-APP-000368-AU-000240
Vuln IDs
  • V-206501
  • V-81165
Rule IDs
  • SV-206501r399910_rule
  • SV-95879
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-6761r285744_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-6761r285745_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-206502 - SV-206502r399913_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001881
Version
SRG-APP-000369-AU-000250
Vuln IDs
  • V-206502
  • V-81167
Rule IDs
  • SV-206502r399913_rule
  • SV-95881
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-6762r285747_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-6762r285748_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-206503 - SV-206503r399916_rule
RMF Control
AU-7
Severity
L
CCI
CCI-001882
Version
SRG-APP-000370-AU-000260
Vuln IDs
  • V-206503
  • V-81169
Rule IDs
  • SV-206503r399916_rule
  • SV-95883
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-6763r285750_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-6763r285751_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-206504 - SV-206504r399928_rule
RMF Control
AU-8
Severity
L
CCI
CCI-001890
Version
SRG-APP-000374-AU-000290
Vuln IDs
  • V-206504
  • V-81171
Rule IDs
  • SV-206504r399928_rule
  • SV-95885
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-6764r285753_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-6764r285754_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-206505 - SV-206505r399931_rule
RMF Control
AU-8
Severity
L
CCI
CCI-001889
Version
SRG-APP-000375-AU-000280
Vuln IDs
  • V-206505
  • V-81173
Rule IDs
  • SV-206505r399931_rule
  • SV-95887
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-6765r285756_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-6765r285757_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.

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-206506 - SV-206506r400039_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001953
Version
SRG-APP-000391-AU-002290
Vuln IDs
  • V-206506
  • V-81323
Rule IDs
  • SV-206506r400039_rule
  • SV-96037
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-6766r285759_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-6766r285760_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-206507 - SV-206507r400042_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001954
Version
SRG-APP-000392-AU-002300
Vuln IDs
  • V-206507
  • V-81327
Rule IDs
  • SV-206507r400042_rule
  • SV-96041
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-6767r285762_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-6767r285763_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-206508 - SV-206508r400114_rule
RMF Control
IA-5
Severity
M
CCI
CCI-002041
Version
SRG-APP-000397-AU-002590
Vuln IDs
  • V-206508
  • V-81331
Rule IDs
  • SV-206508r400114_rule
  • SV-96045
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-6768r285765_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-6768r285766_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.

c
The Central Log Server must be configured to protect the confidentiality and integrity of transmitted information.
SC-8 - High - CCI-002418 - V-206509 - SV-206509r400474_rule
RMF Control
SC-8
Severity
H
CCI
CCI-002418
Version
SRG-APP-000439-AU-004310
Vuln IDs
  • V-206509
  • V-81301
Rule IDs
  • SV-206509r400474_rule
  • SV-96015
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-6769r285768_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-6769r285769_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-206510 - SV-206510r400876_rule
RMF Control
SC-13
Severity
H
CCI
CCI-002450
Version
SRG-APP-000514-AU-002890
Vuln IDs
  • V-206510
  • V-81303
Rule IDs
  • SV-206510r400876_rule
  • SV-96017
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-6770r285771_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-6770r285772_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.

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-206511 - SV-206511r400879_rule
RMF Control
AU-4
Severity
L
CCI
CCI-001851
Version
SRG-APP-000515-AU-000110
Vuln IDs
  • V-206511
  • V-81177
Rule IDs
  • SV-206511r400879_rule
  • SV-95891
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-6771r285774_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-6771r285775_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-206512 - SV-206512r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000330
Vuln IDs
  • V-206512
  • V-81179
Rule IDs
  • SV-206512r401224_rule
  • SV-95893
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-6772r285777_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-6772r285778_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-206513 - SV-206513r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000340
Vuln IDs
  • V-206513
  • V-81181
Rule IDs
  • SV-206513r401224_rule
  • SV-95895
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-6773r285780_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-6773r285781_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-206514 - SV-206514r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000350
Vuln IDs
  • V-206514
  • V-81183
Rule IDs
  • SV-206514r401224_rule
  • SV-95897
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-6774r285783_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-6774r285784_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-206515 - SV-206515r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000360
Vuln IDs
  • V-206515
  • V-81185
Rule IDs
  • SV-206515r401224_rule
  • SV-95899
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-6775r285786_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-6775r285787_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-206516 - SV-206516r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000370
Vuln IDs
  • V-206516
  • V-81187
Rule IDs
  • SV-206516r401224_rule
  • SV-95901
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-6776r285789_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-6776r285790_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-206517 - SV-206517r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000380
Vuln IDs
  • V-206517
  • V-81189
Rule IDs
  • SV-206517r401224_rule
  • SV-95903
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-6777r285792_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-6777r285793_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-206518 - SV-206518r401224_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-APP-000516-AU-000410
Vuln IDs
  • V-206518
  • V-81191
Rule IDs
  • SV-206518r401224_rule
  • SV-95905
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-6778r285795_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-6778r285796_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.

b
The Central Log Server must automatically audit account creation.
AC-2 - Medium - CCI-000018 - V-221900 - SV-221900r420044_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000018
Version
SRG-APP-000026-AU-000580
Vuln IDs
  • V-221900
  • V-100025
Rule IDs
  • SV-221900r420044_rule
  • SV-109129
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-23615r420042_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-23604r420043_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-221901 - SV-221901r420047_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001403
Version
SRG-APP-000027-AU-000590
Vuln IDs
  • V-221901
  • V-100027
Rule IDs
  • SV-221901r420047_rule
  • SV-109131
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-23616r420045_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-23605r420046_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-221902 - SV-221902r420050_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001404
Version
SRG-APP-000028-AU-000600
Vuln IDs
  • V-221902
  • V-100029
Rule IDs
  • SV-221902r420050_rule
  • SV-109133
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-23617r420048_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-23606r420049_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-221903 - SV-221903r420053_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001405
Version
SRG-APP-000029-AU-000610
Vuln IDs
  • V-221903
  • V-100031
Rule IDs
  • SV-221903r420053_rule
  • SV-109135
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-23618r420051_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-23607r420052_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-221904 - SV-221904r420056_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
SRG-APP-000065-AU-000240
Vuln IDs
  • V-221904
  • V-100033
Rule IDs
  • SV-221904r420056_rule
  • SV-109137
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-23619r420054_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-23608r420055_fix

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

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-221905 - SV-221905r420059_rule
RMF Control
AC-8
Severity
L
CCI
CCI-000048
Version
SRG-APP-000068-AU-000035
Vuln IDs
  • V-221905
  • V-100037
Rule IDs
  • SV-221905r420059_rule
  • SV-109141
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-23620r420057_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-23609r420058_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-221906 - SV-221906r420062_rule
RMF Control
AC-8
Severity
L
CCI
CCI-000050
Version
SRG-APP-000069-AU-000420
Vuln IDs
  • V-221906
  • V-100039
Rule IDs
  • SV-221906r420062_rule
  • SV-109143
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-23621r420060_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-23610r420061_fix

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

a
The Central Log Server must initiate session auditing upon startup.
AU-14 - Low - CCI-001464 - V-221907 - SV-221907r420065_rule
RMF Control
AU-14
Severity
L
CCI
CCI-001464
Version
SRG-APP-000092-AU-000670
Vuln IDs
  • V-221907
  • V-100043
Rule IDs
  • SV-221907r420065_rule
  • SV-109147
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-23622r420063_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-23611r420064_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-221908 - SV-221908r420068_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000130
Version
SRG-APP-000095-AU-000680
Vuln IDs
  • V-221908
  • V-100045
Rule IDs
  • SV-221908r420068_rule
  • SV-109149
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-23623r420066_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-23612r420067_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-221909 - SV-221909r420071_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000131
Version
SRG-APP-000096-AU-000690
Vuln IDs
  • V-221909
  • V-100047
Rule IDs
  • SV-221909r420071_rule
  • SV-109151
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-23624r420069_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-23613r420070_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-221910 - SV-221910r420074_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000132
Version
SRG-APP-000097-AU-000700
Vuln IDs
  • V-221910
  • V-100049
Rule IDs
  • SV-221910r420074_rule
  • SV-109153
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-23625r420072_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-23614r420073_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-221911 - SV-221911r420077_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000133
Version
SRG-APP-000098-AU-000710
Vuln IDs
  • V-221911
  • V-100051
Rule IDs
  • SV-221911r420077_rule
  • SV-109155
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-23626r420075_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-23615r420076_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-221912 - SV-221912r420080_rule
RMF Control
AU-3
Severity
L
CCI
CCI-000134
Version
SRG-APP-000099-AU-000720
Vuln IDs
  • V-221912
  • V-100053
Rule IDs
  • SV-221912r420080_rule
  • SV-109157
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-23627r420078_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-23616r420079_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-221913 - SV-221913r420083_rule
RMF Control
AU-3
Severity
L
CCI
CCI-001487
Version
SRG-APP-000100-AU-000730
Vuln IDs
  • V-221913
  • V-100055
Rule IDs
  • SV-221913r420083_rule
  • SV-109159
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-23628r420081_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-23617r420082_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-221914 - SV-221914r420086_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000162
Version
SRG-APP-000118-AU-000100
Vuln IDs
  • V-221914
  • V-100057
Rule IDs
  • SV-221914r420086_rule
  • SV-109161
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-23629r420084_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-23618r420085_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-221915 - SV-221915r420089_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000163
Version
SRG-APP-000119-AU-000110
Vuln IDs
  • V-221915
  • V-100059
Rule IDs
  • SV-221915r420089_rule
  • SV-109163
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-23630r420087_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-23619r420088_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-221916 - SV-221916r420092_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000164
Version
SRG-APP-000120-AU-000120
Vuln IDs
  • V-221916
  • V-100061
Rule IDs
  • SV-221916r420092_rule
  • SV-109165
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-23631r420090_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-23620r420091_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-221917 - SV-221917r420095_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001493
Version
SRG-APP-000121-AU-000130
Vuln IDs
  • V-221917
  • V-100063
Rule IDs
  • SV-221917r420095_rule
  • SV-109167
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-23632r420093_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-23621r420094_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-221918 - SV-221918r420098_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001494
Version
SRG-APP-000122-AU-000140
Vuln IDs
  • V-221918
  • V-100065
Rule IDs
  • SV-221918r420098_rule
  • SV-109169
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-23633r420096_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-23622r420097_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-221919 - SV-221919r420101_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001495
Version
SRG-APP-000123-AU-000150
Vuln IDs
  • V-221919
  • V-100067
Rule IDs
  • SV-221919r420101_rule
  • SV-109171
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-23634r420099_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-23623r420100_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-221920 - SV-221920r420104_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
SRG-APP-000141-AU-000090
Vuln IDs
  • V-221920
  • V-100069
Rule IDs
  • SV-221920r420104_rule
  • SV-109173
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-23635r420102_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-23624r420103_fix

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

a
The Central Log Server must notify system administrators and ISSO when accounts are created.
AC-2 - Low - CCI-001683 - V-221921 - SV-221921r420107_rule
RMF Control
AC-2
Severity
L
CCI
CCI-001683
Version
SRG-APP-000291-AU-000200
Vuln IDs
  • V-221921
  • V-100021
Rule IDs
  • SV-221921r420107_rule
  • SV-109125
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-23636r420105_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-23625r420106_fix

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

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-221922 - SV-221922r420110_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
SRG-APP-000295-AU-000190
Vuln IDs
  • V-221922
  • V-100015
Rule IDs
  • SV-221922r420110_rule
  • SV-109119
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-23637r420108_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-23626r420109_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-221923 - SV-221923r420113_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002363
Version
SRG-APP-000296-AU-000560
Vuln IDs
  • V-221923
  • V-100017
Rule IDs
  • SV-221923r420113_rule
  • SV-109121
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-23638r420111_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-23627r420112_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-221924 - SV-221924r420116_rule
RMF Control
AC-12
Severity
L
CCI
CCI-002364
Version
SRG-APP-000297-AU-000570
Vuln IDs
  • V-221924
  • V-100019
Rule IDs
  • SV-221924r420116_rule
  • SV-109123
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-23639r420114_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-23628r420115_fix

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

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-221925 - SV-221925r420119_rule
RMF Control
AC-7
Severity
M
CCI
CCI-002238
Version
SRG-APP-000345-AU-000400
Vuln IDs
  • V-221925
  • V-100035
Rule IDs
  • SV-221925r420119_rule
  • SV-109139
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-23640r420117_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-23629r420118_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 require users to reauthenticate when organization-defined circumstances or situations require reauthentication.
IA-11 - Low - CCI-002038 - V-221926 - SV-221926r420122_rule
RMF Control
IA-11
Severity
L
CCI
CCI-002038
Version
SRG-APP-000389-AU-000180
Vuln IDs
  • V-221926
  • V-100071
Rule IDs
  • SV-221926r420122_rule
  • SV-109175
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-23641r420120_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-23630r420121_fix

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

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-221927 - SV-221927r420125_rule
RMF Control
SC-23
Severity
M
CCI
CCI-002470
Version
SRG-APP-000427-AU-000040
Vuln IDs
  • V-221927
  • V-100075
Rule IDs
  • SV-221927r420125_rule
  • SV-109179
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-23642r420123_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-23631r420124_fix

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

b
The Central Log Server must generate audit records when successful/unsuccessful logon attempts occur.
AU-12 - Medium - CCI-000172 - V-221928 - SV-221928r420128_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-APP-000503-AU-000280
Vuln IDs
  • V-221928
  • V-100041
Rule IDs
  • SV-221928r420128_rule
  • SV-109145
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-23643r420126_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-23632r420127_fix

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

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-221929 - SV-221929r531240_rule
RMF Control
IA-7
Severity
H
CCI
CCI-000803
Version
SRG-APP-000610-AU-000050
Vuln IDs
  • V-221929
  • V-100073
Rule IDs
  • SV-221929r531240_rule
  • SV-109177
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-23644r420129_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-23633r531239_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.

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-241819 - SV-241819r695402_rule
RMF Control
AU-12
Severity
L
CCI
CCI-001914
Version
SRG-APP-000095-AU-000050
Vuln IDs
  • V-241819
  • V-81137
Rule IDs
  • SV-241819r695402_rule
  • SV-95851
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-45095r695400_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-45054r695401_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.
CM-6 - Low - CCI-000366 - V-241820 - SV-241820r695405_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
SRG-APP-000516-AU-000060
Vuln IDs
  • V-241820
  • V-81139
Rule IDs
  • SV-241820r695405_rule
  • SV-95853
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-45096r695403_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-45055r695404_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.