Every Active Directory attack ends at a domain controller, because the DC holds every password hash in the domain and signs every Kerberos ticket. Most AD hardening advice is about objects (privileged groups, ACLs, delegation, certificate templates); this guide is about the DC as a server: who can log on to it, which protocols it accepts, what runs on it, how it is backed up, virtualised and patched, and what it should log. It covers Windows Server 2016 to 2025 DCs, including the protocol defaults that changed with Windows Server 2025. It is for AD engineers, Windows server teams and identity security leads. The directory-wide priorities are in the Active Directory and Entra ID Hardening Guide and general server settings are in the Windows Server Hardening Guide; this page goes deeper on the DC itself.
This is an independent guide from NHI Mgmt Group, based on Microsoft's public documentation as of November 2026. It is not sponsored or reviewed by Microsoft. Product features change, so confirm settings against Microsoft's current documentation.
Key takeaways
- Anything that can administer a DC is Tier 0. That includes hypervisor and storage admins for virtual DCs, backup operators and the systems management tool that patches DCs, not only Domain Admins.
- A DC should do one job. Server Core, no browser, no outbound internet, Print Spooler disabled, and only directory, DNS and the agents you must run.
- Close the legacy protocol doors in audit-first order. LDAP signing and channel binding, NTLM restriction and removal of RC4 from Kerberos each have their own events to find dependent clients before enforcement.
- Windows Server 2025 changes the defaults. New deployments require LDAP signing and use channel binding "when supported", and Microsoft states that Windows Server 2025 DCs do not issue RC4 TGTs.
- Monitor the DC for directory-level abuse, not just logons. Replication requests from non-DCs, DSRM changes, SID History additions and audit policy changes are high-signal events.
How identity and access work in a domain controller
A DC is unusual in three ways. It has no local account database of its own: local groups such as Administrators on a DC are the domain's built-in groups. Its computer account can replicate every secret in the domain. And control of the DC's operating system, its disk or its backups is equivalent to control of the domain, because ntds.dit and the krbtgt key are on it.
| Path to control | Who or what has it | Equivalent attack | Primary control |
|---|---|---|---|
| Interactive or remote admin on the DC | Administrators, Domain Admins, Enterprise Admins; Server, Backup, Account and Print Operators can also log on to DCs by default | Credential dumping, GPO and service changes | Empty the operator groups; dedicated Tier 0 admin accounts from PAWs |
| Directory replication rights | DC computer accounts, plus any account granted Replicating Directory Changes All | DCSync (T1003.006) | Review replication rights on the domain head |
| Disk or VM file access | Hypervisor administrators, storage administrators | Offline copy of ntds.dit (T1003.003) | Separate hosts and storage; BitLocker; shielded VMs |
| Backups and system state | Backup Operators, backup service accounts, backup platform admins | Restore or mount of a DC backup | Treat backup system as Tier 0; encrypt and isolate |
| GPOs linked to the Domain Controllers OU | Anyone with edit rights on those GPOs | Group Policy Modification (T1484.001) | Restrict GPO edit rights and monitor changes |
| Code that runs on the DC | Software distribution, EDR, monitoring and patching tools | Push a payload as SYSTEM | Separate management of DCs from general servers |
Admin roles and privileged access
- Dedicated Tier 0 accounts: use separate accounts for DC administration that never log on to Tier 1 or Tier 2 systems, and put them in Protected Users after testing. Protected Users members cannot use NTLM, DES or RC4 in Kerberos pre-authentication, or delegation, and their TGTs last 240 minutes. Microsoft warns never to add service or computer accounts, and to test before adding Domain Admins. See the Tiered Administration and Enterprise Access Model Guide.
- Remote administration only from PAWs: Microsoft recommends performing all DC operations remotely from privileged access workstations or secure administrative hosts, and using GPOs on the DC OU to allow RDP only from authorised users and jump servers. Because GPO reapplies on refresh, a bypassed setting returns at the next refresh.
- Empty the operator groups: Account Operators, Server Operators, Print Operators and Backup Operators carry rights on DCs that are easy to escalate. Keep them empty and alert when they change.
- Directory Services Restore Mode: the DSRM password is a local administrator for each DC. Set a unique, vaulted value per DC, rotate it with
ntdsutil, and alert on event 4794, which Microsoft rates high criticality. - Virtual DCs: Microsoft advises running virtual DCs on physical hosts separate from other VMs, separating their storage from storage administrators, and considering shielded VMs where they share hosts. See the Hyper-V Security Guide.
- Read-only DCs: where a branch cannot physically secure a DC, deploy an RODC with BitLocker and a Password Replication Policy that caches only local users, never administrators.
Integrations, API tokens and service accounts
DCs talk to many systems that hold credentials of their own. Each one either belongs in Tier 0 or must be prevented from reaching the DC with privilege.
- Hybrid identity servers: Entra Connect Sync holds accounts that can read every password hash in the domain. Manage the sync server as a DC. See the Microsoft Entra Connect and Cloud Sync Hardening Guide.
- AD Certificate Services: an enterprise CA can issue certificates that authenticate as any user, so CA servers are Tier 0. See the AD CS Security Guide.
- Applications binding to LDAP: service accounts that use simple binds over port 389 send passwords in clear and will break when signing is enforced. Move them to LDAPS on 636 or signed SASL binds, and find them through events 2887 and 2889. See the LDAP Security Deep Dive Guide.
- Service accounts with RC4-only keys: accounts whose passwords predate AES support have no AES keys until the password is reset;
msDS-SupportedEncryptionTypesvalues such as0x4mean RC4 only. Prefer group managed service accounts. - Agents on the DC: EDR, Defender for Identity sensors, monitoring and backup agents run as SYSTEM. Manage their consoles and update channels as Tier 0, separately from the general server estate, as Microsoft recommends for DC patching and systems management.
Logging and detection
Set the advanced audit policy through the Default Domain Controllers Policy or a dedicated DC GPO, forward events off the DC, and alert on these first.
| Event | What it shows | Why it matters on a DC |
|---|---|---|
| 4662 with replication GUIDs | Directory object operation, including replication rights use | Replication from an address that is not a DC is DCSync (T1003.006) |
| 4794 | Attempt to set the DSRM administrator password | Microsoft rates high; DSRM is a backdoor if logon behaviour is changed |
| 4765, 4766 | SID History added, or attempted | SID-History Injection (T1134.005); high criticality |
| 4719, 1102 | Audit policy changed; audit log cleared | Attackers turning off the evidence |
| 4706, 4713 | New trust created; Kerberos policy changed | Persistence and ticket lifetime tampering |
| 4768, 4769 (Ticket Encryption Type) | TGT and service ticket requests; 0x17 is RC4 | RC4 discovery before removal; RC4 service tickets also signal Kerberoasting |
| 4728, 4732, 4756 | Member added to security groups | Changes to Domain Admins, Administrators, operator groups |
| 5136 | Directory object modified | Changes to GPOs linked to the DC OU, AdminSDHolder and the domain head ACL |
| 2886, 2887, 2889 | LDAP signing not required; count of unsigned binds; per-client unsigned bind detail when LDAP interface diagnostic logging is raised | Find clients before enforcing LDAP signing |
| 3039, 3040, 3041 | LDAP channel binding events | Find clients before enforcing channel binding |
| Protected Users 100, 104 | NTLM or DES/RC4 attempts by Protected Users members | Logs are disabled by default; enable them on DCs |
Also watch for a new computer object registering DC service principal names or replicating (Rogue Domain Controller, T1207), unexpected LSASS access and authentication package changes on DCs (Domain Controller Authentication, T1556.001, the technique behind Skeleton Key style implants), and coerced authentication from DCs to other hosts (Forced Authentication, T1187). See the Active Directory Security Monitoring and Event IDs Guide.
Metrics
- Tier 0 membership: accounts with logon rights to DCs, and the operator groups at zero.
- Legacy protocol use: unsigned LDAP binds per day (event 2887), RC4 tickets per day (4768/4769 with
0x17), NTLM authentications to DCs; all trending to zero. - Baseline conformance: share of DCs on the current Windows Server version, Server Core, with Print Spooler disabled and outbound internet blocked.
- Patch latency: days from Microsoft release to all DCs patched.
- Restore readiness: date of the last tested forest recovery from DC backups.
Hardening baseline
Host
- Platform: newest supported Windows Server, Server Core installation option, TPM and BitLocker on all volumes, locally attached storage where possible. Decommission legacy DCs first.
- Roles and services: AD DS and DNS only; disable Print Spooler (any authenticated user can otherwise make the DC authenticate to a system with unconstrained delegation and expose the DC computer account; see the Printer and Print Spooler Security Guide); no web browser; no unrelated agents.
- Network: block outbound internet from DCs at the perimeter, allow only required AD ports between sites, restrict RDP and WinRM to PAWs and jump servers with Windows Defender Firewall rules delivered by GPO.
- Application control: AppLocker or App Control for Business in audit, then enforce, so only approved binaries run on DCs.
- Patching: patch DCs separately from the general Windows estate, through a Tier 0 management path.
Protocols
| Control | Setting | Audit first with |
|---|---|---|
| LDAP signing | Domain controller: LDAP server signing requirements enforcement (required by default on new Windows Server 2025 deployments) | Events 2886, 2887, 2889 |
| LDAP channel binding | Channel binding token requirements set to "When supported", then "Always" | Events 3039, 3040, 3041 |
| Kerberos RC4 removal | DefaultDomainSupportedEncTypes = 0x18 under HKLM\System\CurrentControlSet\services\KDC, or Network security: Configure encryption types allowed for Kerberos = AES128 and AES256 | 4768/4769 Ticket Encryption Type; Microsoft's Kerberos-Crypto scripts (Get-KerbEncryptionUsage.ps1 -Encryption RC4) |
| NTLM restriction | Network security: Restrict NTLM policies on DCs, audit mode first | NTLM operational log on DCs |
| SMB signing | Required on DCs (the Default Domain Controllers Policy requires it); do not relax it | Not applicable |
Microsoft's November 2022 Kerberos updates made AES the default for accounts without an explicit encryption type, and Microsoft planned to stop assuming RC4 support on DCs from the end of the second quarter of 2026 (KB5073381); check the current status of that change for your build. See the NTLM Deprecation and Elimination Guide and the Kerberos Security Guide.
Rollout
- Define the Tier 0 boundary: list DCs, their hypervisors and storage, backup systems, Entra Connect, AD CS, PAWs and management tools.
- Clean up access: empty operator groups, move DC admins to dedicated accounts, set unique DSRM passwords.
- Turn on auditing for LDAP signing, channel binding, Kerberos encryption types, NTLM and Protected Users, and send it to the SIEM.
- Fix clients for 30 to 90 days: reconfigure LDAP binds, reset passwords on accounts without AES keys, replace RC4-only devices.
- Enforce on one DC or one site first, watch for failures (for example 4769 with failure code
0xE, KDC_ERR_ETYPE_NOTSUPP), then all DCs. - Roll back by reverting the specific GPO or registry value on the DCs; keep each control in its own GPO so it can be reverted alone.
Small domains with two or three DCs can often move through these steps in a quarter; large forests with legacy appliances should expect a longer RC4 and NTLM tail and should enforce site by site.
Framework mapping
| Framework | Reference | Applies to |
|---|---|---|
| NIST SP 800-53 Rev. 5 | AC-6, AC-17, CM-7, IA-5, SC-23 Session Authenticity, AU-6, SI-4 | Tier 0 admin rights, remote admin paths, minimal DC role, krbtgt and DSRM secrets, LDAP signing and channel binding, monitoring |
| NIST CSF 2.0 | PR.AA-05, PR.PS-01, DE.CM-01 | Access policy, DC baseline, monitoring of directory services |
| CIS Controls v8.1 | 4.1 Secure Configuration Process; 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts; 8.2 Collect Audit Logs | DC baseline, Tier 0 accounts, audit policy |
| MITRE ATT&CK | T1003.006 DCSync; T1003.003 NTDS; T1558.001 Golden Ticket; T1484.001 Group Policy Modification; T1207 Rogue Domain Controller; T1134.005 SID-History Injection; T1556.001 Domain Controller Authentication; T1187 Forced Authentication | Detection targets for DC events |
Common misconfigurations
- Virtual DCs on the general cluster. Every VMware or Hyper-V administrator, storage admin and backup operator becomes an unofficial domain admin, and none of them is in Tier 0 monitoring.
- DCs patched and managed by the same tool as everything else. A compromise of the enterprise software distribution system can push code to DCs as SYSTEM.
- Print Spooler left running. It hands any authenticated user a way to coerce the DC's computer account authentication; combined with unconstrained delegation, that leads to domain compromise. See the Kerberos Delegation Security Guide.
- Enforcing LDAP signing or removing RC4 without auditing. Unannounced outages lead to rollback and then nobody tries again; run the audit events first and fix clients by name.
- Same DSRM password everywhere, never rotated. One leaked value gives local admin on every DC in recovery mode.
- Browsing and outbound internet from DCs. Admins download tools on the DC, and malware gets a direct path out; Microsoft says no web browser should be used on DCs.
Practitioner checklist
- Write down the Tier 0 boundary including DC hypervisors, storage, backups, Entra Connect, AD CS and management tools.
- Run DCs on the newest supported Windows Server, Server Core, with TPM and BitLocker.
- Disable Print Spooler, block outbound internet and browsers, and restrict RDP and WinRM to PAWs.
- Empty Account, Server, Print and Backup Operators; use dedicated Tier 0 accounts in Protected Users after testing.
- Set unique, vaulted DSRM passwords per DC and alert on event 4794.
- Audit, then enforce, LDAP signing, channel binding, RC4 removal and NTLM restriction.
- Patch DCs through a separate Tier 0 management path.
- Forward DC security and Directory Service logs centrally and alert on DCSync, SID History, audit policy and DC OU GPO changes.
- Test forest recovery from DC backups at least yearly and protect those backups as Tier 0.
Standards and references
- Microsoft: Securing domain controllers against attack
- Microsoft: LDAP signing for Active Directory Domain Services
- Microsoft: Detect and remediate RC4 usage in Kerberos
- Microsoft: Protected Users security group
- Microsoft: Appendix L, events to monitor
- Microsoft: Security assessment, domain controllers with Print Spooler service available
- MITRE ATT&CK: DCSync
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: Golden Ticket, Silver Ticket and DCSync Guide · Active Directory Domain Compromise Response Playbook · Identity Recovery Guide · BloodHound and Active Directory Attack Path Guide