# Validate What is ML-DSA support in AD CS? with AD/DNS evidence > Use What is ML-DSA support in AD CS? to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/validate-what-is-ml-dsa-support-in-ad-cs-with-ad-dns-evidence/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T16:59:29+00:00 - Modified: 2026-08-27T17:41:21+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use What is ML-DSA support in AD CS? to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of What is ML-DSA support in AD CS? ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Validate What is ML-DSA support in AD CS? with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [What is ML-DSA support in AD CS?](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/ml-dsa-overview) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “Active Directory Certificate Services (AD CS) supports Module-Lattice-Based Digital Signature Algorithm (ML-DSA), a National Institute of Standards and Technology (NIST)-standardized post-quantum digital signature algorithm designed to resist quantum computing attacks.” The research record locates this support at Introduction below H1. - At Introduction below H1, Microsoft states: “ML-DSA is a signature-only algorithm and doesn’t support encryption or key exchange.” The research record locates this support at Introduction below H1. These statements are the factual basis for this document. Do not extend them into a broader assurance. Review certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles only where the source and recorded environment align. ## What the source does not establish The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, including exceptions? - What baseline for Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, observed and expected states, owner, and reason for deviation. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and sanitize protected material before retention. ## Verification and evidence A reviewer should be able to retrace the decision from Introduction below H1; Introduction below H1 through CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks. Record what was collected, where, when, by whom, and which system or role it represents. Label this evidence set DSE-20260827-477 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee. ## Official references - [What is ML-DSA support in AD CS?](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/ml-dsa-overview) — Microsoft ## Primary reference - Name: What is ML-DSA support in AD CS? - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/ml-dsa-overview - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Validate What is ML-DSA support in AD CS? with AD/DNS evidence,” DSE Security, https://update.dsesecurity.com/updates/validate-what-is-ml-dsa-support-in-ad-cs-with-ad-dns-evidence/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.