Active Directory Domain Security Technical Implementation Guide (STIG)

This STIG provides focused security requirements for the AD or Active Directory Domain Services (AD DS) element for Windows Servers operating systems. These requirements apply to the domain and can typically be reviewed once per AD domain. The separate Active Directory Forest STIG contains forest level requirements. Systems must also be reviewed using the applicable Windows STIG. Comments or proposed revisions to this document should be sent via e-mail to the following address: [email protected]

Details

Version / Release: V2R10

Published: 2018-05-30

Updated At: 2018-09-23 19:11:45

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-9018r3_rule AD.0260 CCI-000366 LOW User accounts with delegated authority must be removed from Windows built-in administrative groups or remove the delegated authority from the accounts. In AD it is possible to delegate account and other AD object ownership and administration tasks. (This is commonly done for help desk or other user support staff.) This is done to avoid the need to assign users to Windows groups with more widely ranging p
    SV-30991r3_rule DS00.1140_AD CCI-002418 MEDIUM A VPN must be used to protect directory network traffic for directory service implementation spanning enclave boundaries. The normal operation of AD requires the use of IP network ports and protocols to support queries, replication, user authentication, and resource authorization services. At a minimum, LDAP or LDAPS is usually required for communication with every domain co
    SV-30994r3_rule DS00.4140_AD CCI-000067 MEDIUM If a VPN is used in the AD implementation, the traffic must be inspected by the network Intrusion detection system (IDS). To provide data confidentiality, a VPN is configured to encrypt the data being transported. While this protects the data, some implementations do not allow that data to be processed through an intrusion detection system (IDS) that could detect data from a
    SV-30996r3_rule DS00.6140_AD CCI-000366 MEDIUM Active Directory must be supported by multiple domain controllers where the Risk Management Framework categorization for Availability is moderate or high. In Active Directory (AD) architecture, multiple domain controllers provide availability through redundancy. If an AD domain or servers within it have an Availability categorization of medium or high and the domain is supported by only a single domain con
    SV-30995r4_rule DS00.6120_AD CCI-000366 LOW Active Directory implementation information must be added to the organization contingency plan where the Risk Management Framework categorization for Availability is moderate or high. When an incident occurs that requires multiple Active Directory (AD) domain controllers to be rebuilt, it is critical to understand the AD hierarchy and replication flow so that the correct recovery sequence and configuration values can be selected. With
    SV-31214r2_rule DS00.7100_AD CCI-000366 LOW The impact of INFOCON changes on the cross-directory authentication configuration must be considered and procedures documented. When incidents occur that require a change in the INFOCON status, it may be necessary to take action to restrict or disable certain types of access that is based on a directory outside the Component’s control. Cross-directory configurations (such as tru
    SV-30989r3_rule DS00.1120_AD CCI-000366 LOW Each cross-directory authentication configuration must be documented. Active Directory (AD) external, forest, and realm trust configurations are designed to extend resource access to a wider range of users (those in other directories). If specific baseline documentation of authorized AD external, forest, and realm trust co
    SV-9030r2_rule AD.0170 CCI-000366 MEDIUM Access to need-to-know information must be restricted to an authorized community of interest. Because trust relationships effectively eliminate a level of authentication in the trusting domain or forest, they represent less stringent access control at the domain or forest level in which the resource resides. To mitigate this risk, trust relationsh
    SV-9031r2_rule AD.0180 CCI-000366 HIGH Interconnections between DoD directory services of different classification levels must use a cross-domain solution that is approved for use with inter-classification trusts. If a robust cross-domain solution is not used, then it could permit unauthorized access to classified data. To support secure access between resources of different classification levels, the solution must meet discretionary access control requirements. Th
    SV-9033r2_rule AD.0181 CCI-000366 HIGH A controlled interface must have interconnections among DoD information systems operating between DoD and non-DoD systems or networks. The configuration of an AD trust relationship is one of the steps used to allow users in one domain to access resources in another domain, forest, or Kerberos realm. When a trust is defined between a DoD organization and a non-DoD organization, the securi
    SV-9035r3_rule AD.0190 CCI-000764 MEDIUM Security identifiers (SIDs) must be configured to use only authentication data of directly trusted external or forest trust. Under some circumstances it is possible for attackers or rogue administrators that have compromised a domain controller in a trusted domain to use the SID history attribute (sIDHistory) to associate SIDs with new user accounts, granting themselves unautho
    SV-9037r3_rule AD.0200 CCI-000213 MEDIUM Selective Authentication must be enabled on outgoing forest trusts. Enabling Selective Authentication on outbound Active Directory (AD) forest trusts significantly strengthens access control by requiring explicit authorization (through the Allowed to Authenticate permission) on resources in the trusting forest. When Sele
    SV-9044r3_rule AD.0220 CCI-000804 MEDIUM The Anonymous Logon and Everyone groups must not be members of the Pre-Windows 2000 Compatible Access group. The Pre-Windows 2000 Compatible Access group was created to allow Windows NT domains to interoperate with AD domains by allowing unauthenticated access to certain AD data. The default permissions on many AD objects are set to allow access to the Pre-Windo
    SV-9045r3_rule AD.0240 CCI-000366 MEDIUM Membership in the Group Policy Creator Owners and Incoming Forest Trust Builders groups must be limited. Membership in the Group Policy Creator Owners and Incoming Forest Trust Builders groups assigns a high privilege level for AD functions. Unnecessary membership increases the risk from compromise or unintended updates. Members of these groups must specif
    SV-31557r2_rule DS00.3200_AD CCI-000366 MEDIUM Accounts from outside directories that are not part of the same organization or are not subject to the same security policies must be removed from all highly privileged groups. Membership in certain default directory groups assigns a high privilege level for access to the directory. In AD, membership in the following groups enables high privileges relative to AD and the Windows OS: Domain Admins, Enterprise Admins, Schema Admins
    SV-9048r4_rule AD.0160 CCI-000366 MEDIUM The domain functional level must be at a Windows Server version still supported by Microsoft. Domains operating at functional levels below Windows Server versions no longer supported by Microsoft reduce the level of security in the domain and forest as advanced features of the directory are not available. This also prevents the addition of domain
    SV-30992r3_rule DS00.3230_AD CCI-000366 MEDIUM Inter-site replication must be enabled and configured to occur at least daily. Timely replication makes certain that directory service data is consistent across all servers that support the same scope of data for their clients. In AD implementation using AD Sites, domain controllers defined to be in different AD Sites require Site l
    SV-31547r3_rule DS00.0160_AD CCI-000366 MEDIUM Active Directory data must be backed up daily for systems with a Risk Management Framework categorization for Availability of moderate or high. Systems with a categorization of low must be backed up weekly. Failure to maintain a current backup of directory data could make it difficult or impossible to recover from incidents including hardware failure or malicious corruption. A failure to recover from the loss of directory data used in identification and aut
    SV-32179r3_rule AD.0151 CCI-000366 MEDIUM The Directory Service Restore Mode (DSRM) password must be changed at least annually. The Directory Service Restore Mode (DSRM) password, used to log on to a domain controller (DC) when rebooting into the server recovery mode, is very powerful. With a weak or known password, someone with local access to the DC can reboot the server and co
    SV-32648r2_rule AD.0270 CCI-000366 MEDIUM Read-only Domain Controller (RODC) architecture and configuration must comply with directory services requirements. The RODC role provides a unidirectional replication method for selected information from your internal network to the DMZ. If not properly configured so that the risk footprint is minimized, the interal domain controller or forest can be compromised. ROD
    SV-47837r2_rule AD.0001 CCI-000366 HIGH Membership to the Enterprise Admins group must be restricted to accounts used only to manage the Active Directory Forest. The Enterprise Admins group is a highly privileged group. Personnel who are system administrators must log on to Active Directory systems only using accounts with the level of authority necessary. Only system administrator accounts used exclusively to ma
    SV-47838r2_rule AD.0002 CCI-000366 HIGH Membership to the Domain Admins group must be restricted to accounts used only to manage the Active Directory domain and domain controllers. The Domain Admins group is a highly privileged group. Personnel who are system administrators must log on to Active Directory systems only using accounts with the level of authority necessary. Only system administrator accounts used exclusively to manage
    SV-47839r2_rule AD.0003 CCI-000366 MEDIUM Administrators must have separate accounts specifically for managing domain member servers. Personnel who are system administrators must log on to domain systems only using accounts with the minimum level of authority necessary. Only system administrator accounts used exclusively to manage domain member servers may be members of an administrator
    SV-47840r2_rule AD.0004 CCI-000366 MEDIUM Administrators must have separate accounts specifically for managing domain workstations. Personnel who are system administrators must log on to domain systems only using accounts with the minimum level of authority necessary. Only system administrator accounts used exclusively to manage domain workstations may be members of an administrators
    SV-47841r2_rule AD.0005 CCI-000366 HIGH Delegation of privileged accounts must be prohibited. Privileged accounts such as those belonging to any of the administrator groups must not be trusted for delegation. Allowing privileged accounts to be trusted for delegation provides a means for privilege escalation from a compromised system.ECLP-1
    SV-47842r5_rule AD.MP.0001 CCI-001082 MEDIUM Only Privileged Access Workstations (PAWs) dedicated for the sole purpose of managing Active Directory must be used to manage Active Directory remotely. Only domain systems used exclusively to manage Active Directory, referred to as Privileged Access Workstations (PAWs) must be used to manage Active Directory remotely. Dedicating domain systems to be used solely for managing Active Directory will aid in p
    SV-47844r4_rule AD.0008 CCI-001941 MEDIUM Local administrator accounts on domain systems must not share the same password. Local administrator accounts on domain systems must use unique passwords. In the event a domain system is compromised, sharing the same password for local administrator accounts on domain systems will allow an attacker to move laterally and compromise mul
    SV-56469r2_rule AD.0009 CCI-000366 MEDIUM Separate smart cards must be used for Enterprise Admin (EA) and Domain Admin (DA) accounts from smart cards used for other accounts. A separate smart card for Enterprise Admin and Domain Admin accounts eliminates the automatic exposure of the private keys for the EA/DA accounts to less secure user platforms when the other accounts are used. Having different certificates on one card do
    SV-56473r2_rule AD.0013 CCI-000366 MEDIUM Separate domain accounts must be used to manage public facing servers from any domain accounts used to manage internal servers. Public facing servers should be in DMZs with separate Active Directory forests. If, because of operational necessity, this is not possible, lateral movement from these servers must be mitigated within the forest. Having different domain accounts for adm
    SV-56533r4_rule AD.AU.0001 CCI-000366 MEDIUM Usage of administrative accounts must be monitored for suspicious and anomalous activity. Monitoring the usage of administrative accounts can alert on suspicious behavior and anomalous account usage that would be indicative of potential malicious credential reuse.
    SV-56534r4_rule AD.AU.0002 CCI-000366 MEDIUM Systems must be monitored for attempts to use local accounts to log on remotely from other systems. Monitoring for the use of local accounts to log on remotely from other systems may indicate attempted lateral movement in a Pass-the-Hash attack.
    SV-56535r4_rule AD.AU.0003 CCI-000366 MEDIUM Systems must be monitored for remote desktop logons. Remote Desktop activity for administration should be limited to specific administrators, and from limited management workstations. Monitoring for any Remote Desktop logins outside of expected activity can alert on suspicious behavior and anomalous accoun
    SV-56889r2_rule AD.0014 CCI-000199 MEDIUM Windows service \ application accounts with administrative privileges and manually managed passwords, must have passwords changed at least every 60 days. NT hashes of passwords for accounts that are not changed regularly are susceptible to reuse by attackers using Pass-the-Hash. Windows service \ application account passwords are not typically changed for longer periods of time to ensure availability of t
    SV-67945r1_rule AD.0015 CCI-000366 MEDIUM Domain controllers must be blocked from Internet access. Domain controllers provide access to highly privileged areas of a domain. Such systems with Internet access may be exposed to numerous attacks and compromise the domain. Restricting Internet access for domain controllers will aid in protecting these pr
    SV-87467r1_rule AD.0016 CCI-000199 MEDIUM All accounts, privileged and unprivileged, that require smart cards must have the underlying NT hash rotated at least every 60 days. When a smart card is required for a domain account, a long password, unknown to the user, is generated. This password and associated NT hash are not changed as are accounts with passwords controlled by the maximum password age. Disabling and re-enabling t
    SV-92837r2_rule AD.0017 CCI-000366 MEDIUM 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. Accounts with domain level administrative privileges are highly prized in Pass-the-Hash/credential theft attacks. The Protected Users group provides extra protections to accounts such as preventing authentication using NTLM. These accounts include Enter