Certificate Services (AD-CS)


AD CS is Microsoftโ€™s PKI implementation that provides everything from encrypting file systems, to digital signatures, to user authentication (a large focus of our research), and more. While AD CS is not installed by default for Active Directory environments, from our experience in enterprise environments it is widely deployed, and the security ramifications of misconfigured certificate service instances are enormous. (specterops.io)
In their research papers, Will Schroeder and Lee Christensen shared their research on AD CS and identified multiple theft, escalation and persistence vectors.



  • PKI (Public Key Infrastructure) โ€” a system to manage certificates/public key encryption
  • AD CS (Active Directory Certificate Services) โ€” Microsoftโ€™s PKI implementation
  • CA (Certificate Authority) โ€” PKI server that issues certificates
  • Enterprise CA โ€” CA integrated with AD (as opposed to a standalone CA), offers certificate templates
  • Certificate Template โ€” a collection of settings and policies that defines the contents of a certificate issued by an enterprise CA
  • CSR (Certificate Signing Request) โ€” a message sent to a CA to request a signed certificate
  • EKU (Extended/Enhanced Key Usage) โ€” one or more object identifiers (OIDs) that define how a certificate can be used


While AD CS offers attackers a wide range of exploitation and persistence scenarios, this set of services is not always installed, and when it is, it is a requirement to identify its different parts in the domain.

Cert Publishers

An initial indicator is the "Cert Publishers" built-in group whose members usually are the servers where AD CS is installed (i.e. PKI/CA).
  • From UNIX-like systems: rpc net group members "Cert Publishers" -U "DOMAIN"/"User"%"Password" -S "DomainController"
  • From Windows systems: net group "Cert Publishers" /domain

pKIEnrollmentService objects

Alternatively, information like the PKI's CA and DNS names can be gathered through LDAP.
โ€‹CrackMapExec's adcs module (Python) can be used to find PKI enrollment services in AD.
crackmapexec ldap 'domaincontroller' -d 'domain' -u 'user' -p 'password' -M adcs
โ€‹windapsearch (Python) can be used to manually to the LDAP query.
windapsearch -m custom --filter '(objectCategory=pKIEnrollmentService)' --base 'CN=Configuration,DC=domain,DC=local' --attrs dn,dnshostname --dc 'domaincontroller' -d 'domain.local' -u 'user' -p 'password'

Attack paths

โ€‹Certipy (Python) and Certify (C#) can also identify the PKI enrollment services and potential attack paths.
From UNIX-like systems, the Certipy (Python) tool can be used to operate multiple attacks and enumeration operations.
certipy 'domain.local'/'user':'password'@'domaincontroller' find
By default, Certipy uses LDAPS, which is not always supported by the domain controllers. The -scheme flag can be used to set whether to use LDAP or LDAPS.
From Windows systems, the Certify (C#) tool can be used to operate multiple attacks and enumeration operations.
Certify.exe cas


The different domain escalation scenarios are detailed in the following parts.


Microsoft ADCS โ€“ Abusing PKI in Active Directory Environment - RiskInsight
AD CS - What Can Be Misconfigured? - HTTP418 InfoSec
HTTP418 InfoSec
AD CS - The 'Certified Pre-Owned' Attacks - HTTP418 InfoSec
HTTP418 InfoSec
Last modified 2mo ago
Copy link
Edit on GitHub