# Measure TPM lockout state before attempting another authorization > Use Manage TPM lockout to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/measure-tpm-lockout-before-another-authorization/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:13:55+00:00 - Modified: 2026-08-27T13:01:31+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, IT - Reading time: 3 minutes ## What you need to know Use Manage TPM lockout 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 Manage TPM lockout ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Measure TPM lockout state before attempting another authorization. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Manage TPM lockout](https://learn.microsoft.com/en-us/windows/security/hardware-security/tpm/manage-tpm-lockout) from Microsoft supports the following bounded statements: - The TPM enters lockout to resist tampering or repeated malicious authorization attempts. The research record locates this support at Opening overview. - During lockout it rejects authorization-dependent commands but preserves at least one owner attempt to reset lockout. The research record locates this support at Opening overview. These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows only where the source and recorded environment align. ## What the source does not establish Use the version-specific TPM 1.2 or 2.0 recovery method and do not clear the TPM casually. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations are healthy. Documented options are review inputs, not universal mandates. ## Applicability questions - For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows will be compared with the source, and why that instance? - How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations? - Who approves the conclusion, exception, test window, and rollback threshold? ## 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 Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows, observed and expected states, owner, and reason for deviation. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Keep the source locations Opening overview; Opening overview adjacent to the sanitized artifacts used for comparison. Prefer policy and feature state, security events, test detections, administrative assignments, exception approvals, and response tickets, with enough identity and timing data for an independent recheck. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [Manage TPM lockout](https://learn.microsoft.com/en-us/windows/security/hardware-security/tpm/manage-tpm-lockout) — Microsoft ## Primary reference - Name: Manage TPM lockout - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows/security/hardware-security/tpm/manage-tpm-lockout - Source publication date: 2025-08-15 ## Citation and use Preferred citation: “Measure TPM lockout state before attempting another authorization,” DSE Security, https://update.dsesecurity.com/updates/measure-tpm-lockout-before-another-authorization/ 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.