Join our Newsletter — 33% off our NHI Course
Governance, Ownership & Risk

AD CS ESC4

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Governance, Ownership & Risk

AD CS ESC4 is a class of misconfiguration in Active Directory Certificate Services where certificate template or CA settings are too permissive. It can let a low-privilege user request a certificate that can be abused for authentication or for impersonating another account, so template permissions, enrolment flags and authorised subject rules must be tightly controlled.

What ESC4 Means in AD CS

ESC4 is not a single bug, but a dangerous permission state in AD CS security where template or CA settings are too permissive. That means the attack surface is created by configuration drift, not necessarily by a software flaw, which is why review of flags, ACLs, enrolment rules and subject controls matters.

Why It Becomes a Privilege Escalation Path

When certificate templates allow a low-privilege requester to influence identity fields, request approval flow, or certificate usage, the resulting certificate can become an authentication token in practice. In Active Directory environments, that can let an attacker obtain a certificate that maps to a more powerful account or service context, turning a benign issuance path into a path to impersonation.

The danger is that certificate-based authentication often looks legitimate to downstream systems. If subject naming, SAN handling, EKU selection, or enrollment permissions are loose, the certificate can be accepted as a trusted proof of identity even though the original requester should never have been able to act in that role.

How Organisations Check Exposure

Exposure review starts with inventory: which templates are published, who can read or modify them, which CAs issue them, and whether enrolment permissions align with business need. The practical questions are whether the template allows unsafe subject supply, whether application policies are overly broad, and whether the CA or template DACLs let unintended principals enrol or change settings.

Auditing tools and directory queries are useful here because the weakness is often hidden in configuration detail rather than in a headline service outage. A focused certificate template audit helps teams identify ESC-style conditions before they are reachable from a standard user session.

Hardening and Response After Discovery

The response is usually to tighten template permissions first, then reduce enrolment flexibility, then confirm that only the right subjects and uses are allowed. In many environments, the cleanest fix is not just one setting, but removing the combination of unsafe enrolment rights, permissive name construction, and overly broad authentication EKUs that make abuse possible.

Post-compromise response should also assume the certificate may already have been used for authentication. That means looking for forged or misused certificates, reviewing certificate issuance logs, and considering whether related credentials or mapped account access need to be reset or revoked if the abuse path reached production authentication.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementAD CS ESC4 hinges on who may enroll and use certificate-based access.
IA-5 — Authenticator ManagementAbused certificates function as authenticators and must be governed accordingly.
CM-6 — Configuration SettingsESC4 is a permissive configuration state in templates or CA settings.
Recommendation — Restrict certificate enrollment and issuance to approved principals only. Treat issued certificates as authenticators and manage their lifecycle tightly. Harden certificate template and CA configuration baselines and review drift.
CIS Controls v85 — Account ManagementTemplate enrolment and issuance permissions are an access-control problem.
4 — Secure Configuration of Enterprise Assets and SoftwareESC4 is commonly prevented by secure configuration of AD CS components.
Recommendation — Review and limit accounts and groups that can enroll or alter certificate templates. Standardise secure AD CS configurations and continuously validate them.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org