Join our Newsletter — 33% off our NHI Course
Home› Guides› MITRE ATT&CK T1649 Steal or Forge Authentication Certificates…
Guide Privileged Access (PAM)

MITRE ATT&CK T1649 Steal or Forge Authentication Certificates Guide: Detecting and Containing Certificate Credential Abuse

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 17 min read
On this page

A stolen or forged authentication certificate is a credential that survives password resets, bypasses most MFA prompts and often goes unnoticed for its whole validity period. MITRE ATT&CK tracks this as T1649 Steal or Forge Authentication Certificates, a Credential Access technique that covers Active Directory Certificate Services (AD CS), Entra ID device and application certificates, and certificate stores on Windows, Linux and macOS. This guide reads T1649 through a defender's eyes: what the technique includes, which telemetry shows it, how to hunt and measure, and how to respond so that a certificate does not outlive your incident. It is written for identity engineers, detection engineers and incident responders. It deliberately goes beyond the template hardening covered in the AD CS Security Guide, which you should read alongside it.

Key takeaways

  • T1649 is wider than AD CS. ATT&CK v20 lists Windows, Linux, macOS and Identity Provider platforms, so client certificates in key stores, device certificates and certificates added to cloud application credentials are all in scope.
  • Two halves, two defences. Stealing an existing certificate is a key protection and endpoint telemetry problem; forging or mis-issuing one is a CA configuration, template and mapping problem.
  • Certificates break the usual reset playbook. A certificate issued to or for a compromised account keeps authenticating after the password is changed, so response must include finding and revoking certificates, and for a stolen CA key, rebuilding trust.
  • Strong certificate mapping is now the floor. Microsoft's KB5014754 moved domain controllers to Full Enforcement in February 2025 and ended the compatibility fallback in September 2025, which closes the classic name-spoofing route but not template abuse or key theft.
  • Detection lives in four places. CA audit events (4886, 4887 and the CA configuration events), DC Kerberos events (4768 with certificate fields, Kdcsvc 39 to 41), endpoint key-store access, and cloud audit logs for certificate credential changes.

What T1649 covers in ATT&CK v20

ATT&CK describes T1649 as adversaries stealing or forging certificates used for authentication to access remote systems or resources. The technique page gives Entra ID device certificates and AD CS certificates as examples of certificates that bind to an identity and act as credentials for domain accounts. It sits under Credential Access, but the description is explicit that the same activity enables Lateral Movement, Privilege Escalation (through the Subject Alternative Name, or SAN, in a certificate) and Persistence, because a certificate keeps working as a valid account for its whole lifetime even after the password changes.

VariantWhat the adversary obtainsPrimary control pointRelated techniques
Theft from a certificate storeAn existing user or machine certificate and its private key, exported from the Windows store, registry, roaming credentials or a key fileNon-exportable keys, TPM or smart card storage, endpoint telemetryT1552.004 Private Keys
Theft of misplaced filesPFX or PEM files on shares, repositories or build serversSecret scanning, file share hygieneT1552.004 Private Keys
Mis-issuance through enrolmentA new certificate whose SAN names a more privileged account, through a weak template or CA settingTemplate and CA hardening, approval, strong mappingT1078.002 Domain Accounts
Persistence by enrolment or renewalA legitimately issued client authentication certificate for an account the adversary already controlsIssuance monitoring, revocation on responseT1098 Account Manipulation
Golden certificateThe CA private key, then forged certificates for any principalHSM-protected CA keys, CA as Tier 0T1552.004 Private Keys, T1558.001 Golden Ticket (ticket access from certificates)
Cloud certificate credentialsA certificate added to an application or service principal, or an exported device certificateApplication credential governance, cloud audit logsT1098 Account Manipulation

ATT&CK v20 lists APT29 (G0016) abusing misconfigured AD CS templates to impersonate administrators and create further authentication certificates, and NIMBUS MANTICORE (G1059) leveraging vulnerable AD CS templates to impersonate higher-privileged accounts. Several commodity and dual-use tools also implement certificate export. The lesson for defenders is that this is established tradecraft for capable groups, not a laboratory curiosity.

Why certificates make attractive credentials

Certificates differ from passwords and tokens in ways that matter for detection and response:

  • Lifetime: client authentication templates commonly issue certificates valid for one or two years. Passwords rotate, sessions expire, but the certificate keeps working until it expires or is revoked and the revocation is checked.
  • Independence from the password: Kerberos PKINIT authenticates with the key pair, not the password, so a reset does not invalidate the certificate. SpecterOps' Certified Pre-Owned research made this point in 2021 and it remains the most commonly missed response step.
  • MFA by default: certificate logon is often treated as strong or multi-factor authentication. A stolen certificate with an exportable key inherits that trust without the second factor the design assumed.
  • Weak revocation in practice: forged certificates from a stolen CA key never appear in the CA database, so there is nothing to revoke. The only fix is removing trust in that CA.
  • Credential conversion: ATT&CK notes that certificate access can be used to obtain other credentials, such as ticket-granting tickets or NTLM material, which then feed into MITRE ATT&CK T1558 Steal or Forge Kerberos Tickets Guide territory.

Prevention: removing the conditions T1649 needs

ATT&CK maps four mitigations to T1649. The table translates each into the concrete controls a Windows and cloud estate should have. Template-level detail (ESC classes, enrolment rights, manager approval) is in the AD CS guide and is not repeated here.

ATT&CK mitigationWhat it means in practiceEvidence it is done
M1015 Active Directory ConfigurationTreat every enterprise and subordinate CA, and anything holding CA keys, as Tier 0. Stop templates letting low-privileged enrollees supply a SAN; require CA certificate manager approval where SAN supply is unavoidable. Keep domain controllers in strong mapping Full Enforcement.CA servers in the Tier 0 management boundary; no authentication template with enrollee-supplied subject and broad enrolment; no Kdcsvc 39 warnings outstanding
M1042 Disable or Remove Feature or ProgramRemove unused HTTP enrolment roles (Web Enrollment, Certificate Enrollment Web Service and Policy Service, NDES). Where they must stay, require HTTPS with Extended Protection for Authentication and remove NTLM.Role inventory per CA; IIS authentication settings reviewed
M1041 Encrypt Sensitive InformationProtect private keys in TPMs, smart cards or HSMs. Mark keys non-exportable in templates and use the Microsoft Platform Crypto Provider or a key storage provider backed by hardware where devices support it. Protect CA keys in an HSM.Template cryptography settings; HSM inventory for every CA
M1047 AuditRegularly review issued certificates, template permissions and CA settings, and remove certificates that no longer have a purpose.Dated review records; count of active certificates per template trending down

Two further controls sit outside the ATT&CK list but follow directly from it:

  • Review the NTAuth store: only CAs in the domain's NTAuth store can issue certificates for Windows logon. Every entry is a CA you trust to mint domain credentials, so the list should be short, known and owned.
  • Govern cloud certificate credentials: application registrations and service principals that authenticate with certificates should have an owner, a documented purpose, a short validity and alerting on credential changes. See the Azure Entra Client Secrets Security Guide for the equivalent secret controls.

Strong certificate mapping and what it does not stop

Microsoft's KB5014754 addressed CVE-2022-26923 (often called Certifried), CVE-2022-26931 and CVE-2022-34691, all elevation of privilege flaws in how the KDC mapped certificates to accounts. Since the May 2022 update, enterprise CAs add a SID extension (OID 1.3.6.1.4.1.311.25.2) to certificates issued from online templates, and domain controllers check it. The registry value StrongCertificateBindingEnforcement under HKLM\SYSTEM\CurrentControlSet\Services\Kdc controlled the transition (0 disabled, 1 compatibility, 2 full enforcement). The February 2025 security update moved domain controllers not already at 2 into Full Enforcement, and Microsoft states that the option to return to compatibility mode ended in September 2025.

This matters for T1649 in a precise way. Strong mapping stops a certificate being accepted for an account it was not issued to, which closes name-spoofing and many SAN tricks against modern domain controllers. It does not stop:

  • theft of a legitimately issued certificate for the victim account, because the SID in the certificate is the victim's own;
  • a CA that is configured to issue a certificate carrying another account's identity and SID, which is why template and CA hardening still matter;
  • a golden certificate forged with the CA key, because the forger controls every field;
  • certificates used against systems that do not perform AD mapping at all, such as cloud applications or third-party services that trust a certificate chain directly.

Mapping details, altSecurityIdentities formats and the events Kdcsvc 39, 40 and 41 are covered in the Kerberos PKINIT and Certificate Mapping Guide.

Detection: telemetry and analytics

ATT&CK v20 ships a detection strategy for T1649 (DET0240) with analytics for Windows, Linux, macOS and identity providers. Combined with the CA and DC event sets, that gives the following map.

SourceEvent or signalWhat to look for
CA (Security log, Audit Certification Services)4886 request received, 4887 request approved and issuedRequests where the requester differs from the subject or SAN, especially SANs naming privileged accounts; spikes from one requester; requests for authentication templates from unusual hosts
CA4882 security permissions changed, 4890 manager settings changed, 4891 configuration entry changed, 4892 property changed, 4898 template loadedAny change outside a change window; new flags permitting requester-defined SANs
CA4876 and 4877 backup started and completed, 4885 audit filter changed, 4896 rows deletedCA backups not run by the backup service account (a key export risk); audit filter reductions; database row deletion
Domain controller4768 Kerberos TGT requested, certificate fields populatedPKINIT logons by accounts that never use certificates; certificate issuer not in your expected CA list; serial numbers absent from the CA database (a golden certificate indicator)
Domain controller (System log, Kdcsvc)39, 40, 4141 means the SID in the certificate does not match the account, a strong sign of a certificate issued to another user
Windows endpoint4657 registry value modified (in DET0240), process access to certificate storesUnusual processes reading or exporting private keys, PFX files written to disk outside enrolment workflows
Linux and macOSauditd open and read on /etc/ssl, /etc/pki, ~/.pki/nssdb; execve of PKCS#12 and keystore utilities; Keychain accessKey material read by processes that do not normally use it; exports on servers
Entra ID and Microsoft 365 auditAdd or update certificate credential on applications and service principalsCertificate credentials added outside deployment pipelines, by unusual actors or to high-privilege applications

Microsoft Defender for Identity, where deployed with sensors on AD CS servers, raises alerts that align with these analytics, including Suspicious certificate usage over Kerberos protocol (PKINIT) (2425), Suspicious Domain Controller certificate request (ESC8) (2432), Suspicious modifications to the AD CS security permissions/settings (2435), Suspicious disable of audit filters of AD CS (2434) and Suspected rogue Kerberos certificate usage (2047). Whatever product you use, the logic to replicate is the same: correlate issuance on the CA with use on the DC, and treat a certificate used at the DC that the CA never issued as a critical incident.

Prerequisite: CA events only appear if both the Audit Certification Services subcategory is enabled on the CA servers and the CA's own audit filter (the Auditing tab in the Certification Authority console) has its event categories selected. Many estates have one without the other.

Hunting for T1649

Scheduled hunts complement real-time rules because certificate abuse can be quiet. Useful hunts, each defensive and based on data you already hold:

  1. Issued versus requested identity: export the CA database view of issued certificates for authentication templates and flag rows where the requester account differs from the subject or SAN. Legitimate cases (enrolment agents, provisioning services) should be a short, known list.
  2. Certificates for privileged accounts: list every valid certificate whose subject or SAN maps to a Tier 0 account or group member. Most should have none; each one needs an owner and a reason.
  3. PKINIT users who should not be: compare accounts seen in 4768 with certificate fields over 90 days against your list of smart card or Windows Hello for Business users and machine certificate holders.
  4. Unknown issuers and serials: join DC certificate logons on issuer and serial to the CA database. A serial with no matching issuance record is the signature of a forged certificate.
  5. Exported keys on disk: search file shares, repositories and build servers for PFX and PEM private keys. See the Git Secret Scanning Guide.
  6. Cloud credential drift: list certificate credentials on applications and service principals created in the last 30 days and reconcile them against pipeline deployments.

Responding to certificate abuse

Response to T1649 fails most often because teams follow the password playbook. Use these steps in order:

  1. Scope by certificate, not just account: identify every certificate issued to, requested by or carrying the identity of affected accounts and machines, using the CA database and DC logs.
  2. Revoke and publish: revoke those certificates, publish a fresh CRL and confirm that relying parties, including domain controllers, check revocation. Plan for CRL caching delays.
  3. Close the issuance path: fix the template, CA flag, enrolment endpoint or permission that allowed mis-issuance before revoking, or the adversary can simply request again.
  4. Treat a CA key compromise as a trust rebuild: if the CA key may have been exposed, forged certificates cannot be revoked individually. Remove the CA from NTAuth and trust stores, stand up a new CA with an HSM-protected key, and reissue. The Active Directory Domain Compromise Response Playbook covers the wider forest recovery.
  5. Reset secondary credentials: certificate access may have been converted into tickets or hashes, so include the related Kerberos and account resets.
  6. Cloud side: remove unexpected certificate credentials from applications, review what those applications accessed, and rotate any credential a breached supplier held for you.

Implementing T1649 coverage

  1. Visibility first (weeks 1 to 2): enable Audit Certification Services and the CA audit filter on every CA, forward CA and DC Security and Kdcsvc events to the SIEM, and confirm volume. This is low risk and reversible.
  2. Inventory (weeks 2 to 4): list CAs, NTAuth entries, published templates, HTTP enrolment roles, and cloud applications with certificate credentials. Assign owners.
  3. Baseline (weeks 3 to 6): record normal PKINIT users, normal requesters per template and normal CA administrators. Write detections in alert-only mode first.
  4. Harden in rings: change templates and CA settings in a test forest or on a cloned template, then a pilot group, then production. Keep the previous template version unpublished, not deleted, so you can roll back by republishing.
  5. Protect keys: move CA keys to HSMs during planned CA renewal; move client keys to TPM-backed providers as devices are refreshed.
  6. Promote detections: once false positives are understood, raise the issuer-and-serial mismatch and SID mismatch rules to high severity with a defined response runbook.
  7. Exercise: run a tabletop on "certificate issued for a domain admin" and verify that responders revoke, publish CRLs and check for persistence.

Decision guidance: a small organisation with one CA used only for Wi-Fi and VPN may be better served by removing domain logon trust (taking the CA out of NTAuth) than by building a full PKI monitoring programme. A large estate with smart card logon, Windows Hello for Business certificate trust and many templates needs dedicated PKI ownership, HSMs and correlated detection. If you cannot staff that, reduce the number of templates that permit client authentication before adding tooling.

Measuring whether it works

  • Template exposure: number of published templates allowing client authentication with enrollee-supplied subject or broad enrolment rights (target zero).
  • Privileged certificate count: valid certificates mapped to Tier 0 identities, each with a documented owner (target: only those justified).
  • Audit coverage: percentage of CAs with both audit policy and CA audit filter enabled and events arriving in the SIEM (target 100%).
  • Key protection: percentage of CAs with HSM-protected keys, and percentage of client authentication certificates with non-exportable or hardware-backed keys.
  • Response readiness: time from detection to revocation and CRL publication in the last exercise.
  • Cloud hygiene: application certificate credentials without an owner or with validity longer than policy.

Framework mapping

FrameworkReferenceRelevance to T1649
MITRE ATT&CK v20T1649; mitigations M1015, M1042, M1041, M1047; detection strategy DET0240Technique definition, mitigations and analytics used throughout this page
NIST SP 800-53 Rev. 5IA-5(2) Public Key-based Authentication; SC-12 Cryptographic Key Establishment and Management; SC-17 Public Key Infrastructure Certificates; AC-6 Least Privilege; AU-6 Audit Record Review, Analysis, and Reporting; CM-7 Least FunctionalityCertificate-to-account binding, CA key protection, enrolment rights, log review, removing unused enrolment roles
NIST CSF 2.0PR.AA-01; PR.AA-05; PR.PS-01; DE.CM-03; DE.AE-02Credential management, least privilege on templates, configuration management, monitoring and analysis
CIS Controls v8.1Control 5 Account Management; Control 6 Access Control Management; Control 8 Audit Log ManagementAccount and credential lifecycle, enrolment permissions, CA and DC logging
ISO/IEC 27001:2022 Annex AA.5.17 Authentication information; A.8.2 Privileged access rights; A.8.24 Use of cryptography; A.8.15 LoggingCertificate credentials, Tier 0 CA administration, key management, logging

Common failure patterns

  • Resetting passwords and calling it contained: the certificate issued during the intrusion keeps working. Revocation must be part of every identity incident runbook.
  • CA auditing half enabled: the audit subcategory is on but the CA audit filter is empty, so 4886 and 4887 never appear and there is no issuance record to correlate against.
  • CA servers managed like ordinary servers: backup operators, monitoring agents and patching tools with broad rights on the CA give a route to the CA key. A CA belongs in the Tier 0 boundary described in the Tiered Administration and Enterprise Access Model Guide.
  • Exportable keys everywhere: templates that allow private key export turn every endpoint compromise into a portable credential.
  • Shared certificates trusted by many tenants: one certificate trusted across many customers becomes a single key to all of them. The Mimecast Certificate Compromise 2021 showed a stolen vendor-issued certificate used to authenticate to customers' Microsoft 365 Exchange environments.
  • Ignoring cloud certificate credentials: teams harden AD CS but never alert when a certificate is added to a privileged application registration.

Lessons from incidents

The Mimecast case is the clearest public example on NHI Mgmt Group of T1649 against a cloud service: a certificate that customers had configured to connect a vendor service to Microsoft 365 was taken after the vendor's network was compromised, then used from outside the vendor's own address ranges. The defender lessons transfer directly to internal PKI: know which certificates can authenticate to which systems, keep them scoped and short-lived, restrict where they can be used from, and be ready to revoke and replace them quickly without breaking the service.

Practitioner checklist

  • Enable Audit Certification Services and the CA audit filter on every CA, and forward CA and DC events to the SIEM.
  • Confirm all domain controllers run in strong mapping Full Enforcement and resolve any Kdcsvc 39 events.
  • Inventory CAs, NTAuth entries and templates that allow client authentication, and assign an owner to each.
  • Remove unused HTTP enrolment roles and require HTTPS with Extended Protection where they remain.
  • Place CA servers and anything holding CA keys inside the Tier 0 boundary and protect CA keys in HSMs.
  • Make client authentication keys non-exportable and hardware-backed wherever devices support it.
  • Build the issuer-and-serial correlation between DC certificate logons and the CA database.
  • Alert on certificate credentials added to cloud applications and service principals outside pipelines.
  • Add certificate scoping, revocation and CRL publication to identity incident runbooks, and exercise them.

Standards and references

Related NHI Mgmt Group resources: AD CS Security Guide · Kerberos PKINIT and Certificate Mapping Guide · Machine Identity, PKI and Certificate Lifecycle Guide · Active Directory Domain Compromise Response Playbook

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

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
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.