Auditing: System must be configured to audit logoff successes

282bb2eb-115f-483f-85fb-637124552335

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.

Logoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.

Remediation

To fix this configure the policy value for

STIG: Server
2022: https://system32.eventsentry.com/stig/viewer/V-254311
2019: https://system32.eventsentry.com/stig/viewer/V-205838
2016:

Desktop
W11: https://system32.eventsentry.com/stig/viewer/V-253315
W10: https://system32.eventsentry.com/stig/viewer/V-220757

Computer Configuration
|_ Windows Settings
|_ Advanced Audit Policy Configuration
|_ System Audit Policies
|_ Logon/Logoff
|_ Audit Group Membership with "Success" selected.

NIST 800-53 : AU-2, AU-3, AU-12, AC-17
NIST 800-171: 3.3.1, 3.3.2, 3.1.2
CMMC v2.0 L2: AU.L2-3.3.1, AU.L2-3.3.2, AC.L2-3.1.2
PCI-DSS v4.0: Req 10.2.1, Req 10.2.1.4, Req 10.2.1.5
HIPAA SR : §164.312(b), §164.312(a)(1)
HIPAA HICP : Practice 3 (Identity and Access Management), Practice 8 (Incident Response)