STIGQter STIGQter: STIG Summary: Active Directory Domain Security Technical Implementation Guide (STIG) Version: 2 Release: 13 Benchmark Date: 26 Apr 2019:

User accounts with domain level administrative privileges must be members of the Protected Users group in domains with a domain functional level of Windows 2012 R2 or higher.

DISA Rule

SV-92837r3_rule

Vulnerability Number

V-78131

Group Title

AD.0017

Rule Version

AD.0017

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Add user accounts from the local domain that are members of the domain level administrative groups listed below to the Protected Users group. One account may excluded to ensure availability if there are issues with Kerberos.

Enterprise Admins (Users node)
Domain Admins (Users node)
Schema Admins (Users node)
Administrators (Builtin node)
Account Operators (Builtin node)
Backup Operators (Builtin node)

The use of the Protected Users group should be thoroughly tested before fully implementing.

Check Contents

If the domain functional level is not at least Windows 2012 R2, this is NA.

Open "Windows PowerShell".

Enter "Get-ADDomain | FL DomainMode" to determine the domain functional level.

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

Compare membership of the Protected Users group to membership of the following groups. By default, the groups are under the node referenced; however, it is possible to move those under "Users" to another location.
Enterprise Admins (Users node)
Domain Admins (Users node)
Schema Admins (Users node)
Administrators (Builtin node)
Account Operators (Builtin node)
Backup Operators (Builtin node)

It is recommended that one account be excluded to ensure availability if there are issues with Kerberos.

Excluding the account left out for availability, if all user accounts from the local domain that are members of the domain level groups above are not also members of the Protected Users group, this is a finding. (User accounts is referring to accounts for personnel, not service accounts.)

Vulnerability Number

V-78131

Documentable

False

Rule Version

AD.0017

Severity Override Guidance

If the domain functional level is not at least Windows 2012 R2, this is NA.

Open "Windows PowerShell".

Enter "Get-ADDomain | FL DomainMode" to determine the domain functional level.

Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").

Compare membership of the Protected Users group to membership of the following groups. By default, the groups are under the node referenced; however, it is possible to move those under "Users" to another location.
Enterprise Admins (Users node)
Domain Admins (Users node)
Schema Admins (Users node)
Administrators (Builtin node)
Account Operators (Builtin node)
Backup Operators (Builtin node)

It is recommended that one account be excluded to ensure availability if there are issues with Kerberos.

Excluding the account left out for availability, if all user accounts from the local domain that are members of the domain level groups above are not also members of the Protected Users group, this is a finding. (User accounts is referring to accounts for personnel, not service accounts.)

Check Content Reference

M

Target Key

870

Comments