# Enable and attest System Guard Secure Launch on supported processors > Use System Guard Secure Launch and SMM protection to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/enable-and-attest-system-guard-secure-launch/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:13:52+00:00 - Modified: 2026-08-27T13:01:31+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Guide - DSE priority: Advisory - Topics: Cybersecurity, IT - Reading time: 3 minutes ## What you need to know Use System Guard Secure Launch and SMM protection 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 System Guard Secure Launch and SMM protection ## 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 connect an official requirement or behavior to observable evidence: Enable and attest System Guard Secure Launch on supported processors. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [System Guard Secure Launch and SMM protection](https://learn.microsoft.com/en-us/windows/security/hardware-security/system-guard-secure-launch-and-smm-protection) from Microsoft supports the following bounded statements: - System Guard Secure Launch and SMM protection improve Windows startup security. The research record locates this support at Opening overview. - Secure Launch requires a supported processor and Microsoft documents how to verify that it is configured and running. The research record locates this support at Opening overview; section: How to verify. 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 Treat enablement and runtime verification as separate acceptance checks. 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; section: How to verify, 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. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations before and after the test, and store only sanitized operational evidence. ## Verification and evidence Keep the source locations Opening overview; Opening overview; section: How to verify 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. Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed. ## Official references - [System Guard Secure Launch and SMM protection](https://learn.microsoft.com/en-us/windows/security/hardware-security/system-guard-secure-launch-and-smm-protection) — Microsoft ## Primary reference - Name: System Guard Secure Launch and SMM protection - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows/security/hardware-security/system-guard-secure-launch-and-smm-protection - Source publication date: 2025-08-15 ## Citation and use Preferred citation: “Enable and attest System Guard Secure Launch on supported processors,” DSE Security, https://update.dsesecurity.com/updates/enable-and-attest-system-guard-secure-launch/ 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.