WN16-00-000340 - Windows Server 2016 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability.

Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts.

To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours.

Domain accounts can be configured with an account expiration date under 'Account' properties.

Local accounts can be configured to expire with the command 'Net user [username] /expires:[mm/dd/yyyy]', where username is the name of the temporary user account.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_Windows_Server_2016_V2R5_STIG.zip

Item Details

References: CAT|II, CCI|CCI-001682, Rule-ID|SV-224849r857243_rule, STIG-ID|WN16-00-000340, STIG-Legacy|SV-87937, STIG-Legacy|V-73285, Vuln-ID|V-224849

Plugin: Windows

Control ID: 8328059cd896c84b1c7d63f4e7c900482a487e5a21e9edf4583fe4812110107a