Central Log Server Security Requirements Guide

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: [email protected]

Details

Version / Release: V1R1

Published: 2018-08-29

Updated At: 2018-10-11 21:50:05

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-95819r1_rule SRG-APP-000080-AU-000010 CCI-000166 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). 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
    SV-95821r1_rule SRG-APP-000086-AU-000020 CCI-000174 LOW The Central Log Server must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage. 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 inc
    SV-95823r1_rule SRG-APP-000086-AU-000030 CCI-000174 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. 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 i
    SV-95825r1_rule SRG-APP-000086-AU-000390 CCI-000174 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. 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 wi
    SV-95827r1_rule SRG-APP-000088-AU-000040 CCI-001353 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. 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 normalize
    SV-95829r1_rule SRG-APP-000089-AU-000400 CCI-000169 MEDIUM The Central Log Server must be configured to retain the DoD-defined attributes of the log records sent by the devices and hosts. 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.
    SV-95831r1_rule SRG-APP-000090-AU-000070 CCI-000171 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. 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. Mi
    SV-95833r1_rule SRG-APP-000111-AU-000150 CCI-000154 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. 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 centra
    SV-95835r1_rule SRG-APP-000115-AU-000160 CCI-000158 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. 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
    SV-95837r1_rule SRG-APP-000116-AU-000270 CCI-000159 LOW The Central Log Server must be configured to use internal system clocks to generate time stamps for log records. 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
    SV-95839r1_rule SRG-APP-000125-AU-000300 CCI-001348 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. 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 e
    SV-95841r1_rule SRG-APP-000125-AU-000310 CCI-001348 LOW The Central Log Server system backups must be stored on media capable of guaranteeing file integrity for a minimum of five years. 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 missio
    SV-95843r1_rule SRG-APP-000181-AU-000200 CCI-001876 MEDIUM The Central Log Server must be configured to perform audit reduction that supports on-demand reporting requirements. 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 i
    SV-95845r1_rule SRG-APP-000292-AU-000420 CCI-001684 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. 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 o
    SV-95847r1_rule SRG-APP-000293-AU-000430 CCI-001685 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. 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
    SV-95849r1_rule SRG-APP-000294-AU-000440 CCI-001686 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. 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 mit
    SV-95851r1_rule SRG-APP-000353-AU-000050 CCI-001914 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. 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 de
    SV-95853r1_rule SRG-APP-000353-AU-000060 CCI-001914 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. 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
    SV-95855r1_rule SRG-APP-000354-AU-000080 CCI-001919 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. If the system is not configured to select a user session to capture and view or produce a report, investigations into suspicious or harmful events would be hampered by the volume of information captured. The volume of information captured may also adverse
    SV-95857r1_rule SRG-APP-000356-AU-000090 CCI-001844 LOW The Central Log Server must be configured for centralized management of the events repository for the purposes of configuration, analysis, and reporting. 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 a
    SV-95859r1_rule SRG-APP-000358-AU-000100 CCI-001851 MEDIUM The Central Log Server must be configured to off-load log records onto a different system or media than the system being audited. 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, f
    SV-95861r1_rule SRG-APP-000359-AU-000120 CCI-001855 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. 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 managem
    SV-95863r1_rule SRG-APP-000360-AU-000130 CCI-001858 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. 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 operat
    SV-95865r1_rule SRG-APP-000361-AU-000140 CCI-001861 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. 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
    SV-95867r1_rule SRG-APP-000362-AU-000170 CCI-001886 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. 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 invest
    SV-95869r1_rule SRG-APP-000363-AU-000180 CCI-001887 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. 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 inve
    SV-95871r1_rule SRG-APP-000364-AU-000190 CCI-001875 MEDIUM The Central Log Server must be configured to perform audit reduction that supports on-demand audit review and analysis. 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 c
    SV-95873r1_rule SRG-APP-000365-AU-000210 CCI-001877 LOW The Central Log Server must be configured to perform audit reduction that supports after-the-fact investigations of security incidents. 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 t
    SV-95875r1_rule SRG-APP-000366-AU-000220 CCI-001878 LOW The Central Log Server must be configured to generate on-demand audit review and analysis reports. 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 capab
    SV-95877r1_rule SRG-APP-000367-AU-000230 CCI-001879 LOW The Central Log Server must be configured to generate reports that support on-demand reporting requirements. 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 b
    SV-95879r1_rule SRG-APP-000368-AU-000240 CCI-001880 LOW The Central Log Server must be configured to generate reports that support after-the-fact investigations of security incidents. 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
    SV-95881r1_rule SRG-APP-000369-AU-000250 CCI-001881 LOW The Central Log Server must be configured to perform audit reduction that does not alter original content or time ordering of log records. 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 re
    SV-95883r1_rule SRG-APP-000370-AU-000260 CCI-001882 LOW The Central Log Server must be configured to generate reports that do not alter original content or time ordering of log records. 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 o
    SV-95885r1_rule SRG-APP-000374-AU-000290 CCI-001890 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). 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 G
    SV-95887r1_rule SRG-APP-000375-AU-000280 CCI-001889 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. 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 synchr
    SV-95889r1_rule SRG-APP-000381-AU-000320 CCI-001814 LOW The Central Log Server must be configured to audit the enforcement actions used to prevent access to modules or functions that can change the account access levels. Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions.
    SV-95891r1_rule SRG-APP-000515-AU-000110 CCI-001851 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. 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, f
    SV-95893r1_rule SRG-APP-000516-AU-000330 CCI-000366 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. 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 admini
    SV-95895r1_rule SRG-APP-000516-AU-000340 CCI-000366 MEDIUM The Central Log Server that aggregates log records from hosts and devices must be configured to use TCP for transmission to guarantee delivery. 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 gu
    SV-95897r1_rule SRG-APP-000516-AU-000350 CCI-000366 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. 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
    SV-95899r1_rule SRG-APP-000516-AU-000360 CCI-000366 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). 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 fam
    SV-95901r1_rule SRG-APP-000516-AU-000370 CCI-000366 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. 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 compreh
    SV-95903r1_rule SRG-APP-000516-AU-000380 CCI-000366 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. 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 c
    SV-95905r1_rule SRG-APP-000516-AU-000410 CCI-000366 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. 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 coul
    SV-95995r1_rule SRG-APP-000148-AU-002270 CCI-000764 HIGH The Central Log Server must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). 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 org
    SV-95997r1_rule SRG-APP-000171-AU-002540 CCI-000196 HIGH For accounts using password authentication, the Central Log Server must be configured to store only cryptographic representations of passwords. 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
    SV-95999r1_rule SRG-APP-000172-AU-002550 CCI-000197 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. 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
    SV-96001r1_rule SRG-APP-000175-AU-002630 CCI-000185 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. 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
    SV-96003r1_rule SRG-APP-000176-AU-002640 CCI-000186 HIGH The Central Log Server, when using PKI-based authentication, must enforce authorized access to the corresponding private key. 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 priva
    SV-96005r1_rule SRG-APP-000178-AU-002660 CCI-000206 HIGH The Central Log Server must obfuscate authentication information during the authentication process so that the authentication is not visible. 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 m
    SV-96009r1_rule SRG-APP-000179-AU-002670 CCI-000803 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). 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 m
    SV-96011r1_rule SRG-APP-000033-AU-001610 CCI-000213 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. 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 cont
    SV-96015r1_rule SRG-APP-000439-AU-004310 CCI-002418 HIGH The Central Log Server must be configured to protect the confidentiality and integrity of transmitted information. 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 distr
    SV-96017r1_rule SRG-APP-000514-AU-002890 CCI-002450 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. 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, th
    SV-96021r1_rule SRG-APP-000149-AU-002280 CCI-000765 MEDIUM The Central Log Server must use multifactor authentication for network access to privileged user accounts. 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.
    SV-96023r1_rule SRG-APP-000150-AU-002320 CCI-000766 MEDIUM The Central Log Server must use multifactor authentication for network access to non-privileged user accounts. 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 authentica
    SV-96027r1_rule SRG-APP-000151-AU-002330 CCI-000767 MEDIUM The Central Log Server must use multifactor authentication for local access using privileged user accounts. 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 achiev
    SV-96029r1_rule SRG-APP-000154-AU-002360 CCI-001936 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. 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
    SV-96031r1_rule SRG-APP-000156-AU-002380 CCI-001941 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. 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 cryptogra
    SV-96033r1_rule SRG-APP-000163-AU-002470 CCI-000795 MEDIUM The Central Log Server must disable accounts (individuals, groups, roles, and devices) after 35 days of inactivity. 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 a
    SV-96035r1_rule SRG-APP-000164-AU-002480 CCI-000205 MEDIUM The Central Log Server must be configured to enforce a minimum 15-character password length. 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 bru
    SV-96037r1_rule SRG-APP-000391-AU-002290 CCI-001953 MEDIUM The Central Log Server must be configured to accept the DoD CAC credential to support identity management and personal authentication. 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 com
    SV-96041r1_rule SRG-APP-000392-AU-002300 CCI-001954 MEDIUM The Central Log Server must be configured to electronically verify the DoD CAC credential. 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 com
    SV-96045r1_rule SRG-APP-000397-AU-002590 CCI-002041 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. 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 typical
    SV-96049r1_rule SRG-APP-000165-AU-002580 CCI-000200 LOW The Central Log Server must be configured to prohibit password reuse for a minimum of five generations. 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
    SV-96051r1_rule SRG-APP-000166-AU-002490 CCI-000192 LOW The Central Log Server must be configured to enforce password complexity by requiring that at least one upper-case character be used. 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
    SV-96053r1_rule SRG-APP-000167-AU-002500 CCI-000193 LOW The Central Log Server must be configured to enforce password complexity by requiring that at least one lower-case character be used. 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
    SV-96059r1_rule SRG-APP-000168-AU-002510 CCI-000194 LOW The Central Log Server must be configured to enforce password complexity by requiring that at least one numeric character be used. 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
    SV-96063r1_rule SRG-APP-000169-AU-002520 CCI-001619 LOW The Central Log Server must be configured to enforce password complexity by requiring that at least one special character be used. 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
    SV-96067r1_rule SRG-APP-000170-AU-002530 CCI-000195 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. 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 c
    SV-96069r1_rule SRG-APP-000173-AU-002560 CCI-000198 LOW The Central Log Server must be configured to enforce 24 hours/1 day as the minimum password lifetime. 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 sp
    SV-96073r1_rule SRG-APP-000174-AU-002570 CCI-000199 LOW The Central Log Server must be configured to enforce a 60-day maximum password lifetime restriction. 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
    SV-96077r1_rule SRG-APP-000177-AU-002650 CCI-000187 LOW The Central Log Server must map the authenticated identity to the individual user or group account for PKI-based authentication. 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.