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.
\nThe official System Guard Secure Launch and SMM protection from Microsoft supports the following bounded statements:
\nThese 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.
\nTreat 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.
\nDSE 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.
\nAn 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.
\nKeep 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.
\nKeep 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.
\n