Most Windows estates either ignore Microsoft's security baselines or import them wholesale, and both approaches leave predictable gaps. Microsoft publishes tested configuration baselines for Windows client, Windows Server, Microsoft 365 Apps and Microsoft Edge, together with the Security Compliance Toolkit (SCT) used to compare and apply them. The same intent is delivered three ways: Group Policy Object backups, Intune security baseline profiles built on configuration service providers (CSPs), and, for Windows Server 2025, OSConfig scenarios with built-in drift control. This guide explains how to consume each channel, how to use Policy Analyzer to compare a baseline against what you already enforce, how to tailor and document deviations, and how to deploy, monitor and roll back without breaking production. It is written for Windows platform engineers, endpoint and server teams, and security architects who own configuration standards.
This is an independent guide from NHI Mgmt Group, based on Microsoft's public documentation as of November 2026. It is not sponsored or reviewed by Microsoft. Product features change, so confirm settings against Microsoft's current documentation.
Key takeaways
- A baseline is a starting point, not a certificate. Microsoft states that Intune baselines are not strictly CIS or NIST compliant and that defaults are usually the most restrictive values, so every deployment needs a reviewed list of deviations.
- Compare before you import. Policy Analyzer shows redundant settings, internal conflicts and differences between the new baseline, your existing GPOs and the local registry, which is the fastest way to find what will actually change.
- Pick one authority per setting. GPO, Intune profiles, Defender baselines and OSConfig can all write the same setting; two sources with different values produce Conflict states or settings that flip back and forth.
- Versions move, so plan the upgrade path. Older Intune baseline profiles become read-only when a new version ships, and the Update Version workflow creates a side-by-side copy whose assignments you must move yourself.
- The people who edit baselines are privileged identities. Rights to edit domain GPOs or Intune baseline profiles can change security settings on every device, so they belong in your privileged access model.
What Microsoft security baselines are and what they assume
A security baseline is a group of Microsoft-recommended configuration settings with an explanation of their security impact. Microsoft built them because Windows exposes thousands of Group Policy settings (more than 3,000 for Windows 10, plus over 1,800 for Internet Explorer 11 when that browser was in scope) and only a minority affect security. The baselines encode Microsoft's view of the right value for the ones that do.
Three design principles, stated on Microsoft Learn, decide what is and is not in a baseline.:
- Target environment: the baselines are designed for well-managed, security-conscious organisations where standard users do not have administrative rights. If your users are local administrators, many settings provide much less protection than intended. See the Endpoint Privilege Management Guide and the Local Administrator Password Solution (LAPS) Guide.
- Enforcement test: a setting is enforced only if it mitigates a contemporary threat and does not cause operational problems worse than the risk it removes. This is why some hardening found in CIS Benchmarks or STIGs is absent from Microsoft baselines.
- Defaults are enforced selectively: a secure default is pinned only if an authorised user is likely to change it insecurely. If a non-administrator can set an insecure state, the default is enforced; if an administrator is needed, it is enforced only where a misinformed administrator would probably choose badly.
A Microsoft baseline is therefore deliberately narrower than a compliance benchmark: a well-tested floor. If you also need CIS or DISA STIG alignment, start from the Microsoft baseline and layer the extra settings with documented justification. See the CIS Benchmarks Guide and the DISA STIG Guide.
Delivery channels and what each is for
The same Microsoft guidance reaches devices through different packages. They are not interchangeable: setting names, scope and tooling differ.
| Channel | Format | Products covered (at time of checking) | Best fit | Watch out for |
|---|---|---|---|---|
| Security Compliance Toolkit download | GPO backups, documentation spreadsheet, Policy Analyzer rules, local install scripts | Windows 11 and 10 releases, Windows Server 2016 to 2025, Microsoft 365 Apps for enterprise, Microsoft Edge | Active Directory domains, golden images, reference documentation | Some settings depend on custom administrative templates shipped in the package; import them before editing the GPOs |
| Intune security baselines | Endpoint security profiles built from CSP settings (new format since May 2023) | Windows 10 and later, Windows 365, Defender for Endpoint, Microsoft 365 Apps, Edge, HoloLens 2 | Cloud-managed or co-managed Windows devices | Setting names follow the CSP, not the GPO; older version profiles become read-only |
| OSConfig (Windows Server 2025) | PowerShell module Microsoft.OSConfig with scenarios per role | Windows Server 2025 domain controller, member server and workgroup member | New Server 2025 builds, Azure Arc managed servers | Applies drift control; a second tool writing the same setting causes constant changes |
| Intune STIG audit baseline | Audit-only profile mapped to a DISA STIG SCAP benchmark | Windows 11, US Government GCC High tenants with the required licensing | Evidence of STIG alignment | Does not configure or enforce anything |
Microsoft's own Learn pages list which baseline versions are current; check them at each release because version numbers move several times a year. Windows 10 reached end of support on 14 October 2025, and Microsoft notes that while it remains selectable in Intune, functionality is not guaranteed.
What is inside the SCT baseline package
- GPOs: backups for each scope, typically separate objects for computer settings, user settings, domain controllers, member servers, Defender Antivirus, Credential Guard and browser settings, so you can link them selectively.
- Documentation: a spreadsheet listing every setting, its path and value, and Policy Analyzer
.PolicyRulesfiles for the baseline. The spreadsheet is the document your exception register should reference. - Scripts: a local install script that uses
LGPO.exeto apply the baseline to a non-domain-joined machine, useful for labs and kiosk builds rather than production domains. - Templates: custom administrative templates (the MS Security Guide template, which carries settings such as WDigest authentication, LSA protection and SMBv1 client and server, and the legacy MSS template). Copy these into the central store before editing the GPOs or the settings show as extra registry values.
The Security Compliance Toolkit tools
| Tool | What it does | Typical use |
|---|---|---|
| Policy Analyzer | Compares sets of GPOs as a unit, highlights redundant settings and internal inconsistencies, shows differences between versions, and compares GPOs to the current local policy and registry. Exports to Excel and can snapshot a baseline for later comparison. | Gap analysis before adopting a new baseline version; proving what changed between releases; checking a reference machine |
| GPO2PolicyRules | Command-line converter from a GPO backup to a .PolicyRules file, shipped with Policy Analyzer | Scripting comparisons in a pipeline without the GUI |
| LGPO.exe | Applies Registry.pol files, security templates, advanced audit backups and LGPO text files to local policy; exports local policy to a GPO backup; converts between Registry.pol and editable text | Workgroup servers, images, verifying a GPO's effect in isolation |
| SetObjectSecurity.exe | Sets the security descriptor on files, directories, registry keys, event logs, services and SMB shares, optionally with inheritance; can output a REG_BINARY value | Applying ACL requirements that GPO cannot express cleanly |
A practical Policy Analyzer gap analysis
- Back up every GPO currently linked to the target organisational units with Group Policy Management, including the Default Domain Policy and Default Domain Controllers Policy.
- Add the new baseline's
.PolicyRulesfiles and your exported GPO backups to Policy Analyzer as separate policy sets. - Compare them together with the effective state of a representative reference machine. Rows where the baseline and your GPO disagree are your decision list; rows present only in the baseline are new controls; rows present only in your GPOs are your existing additions.
- Flag conflicts inside your own GPO set (the same setting with different values in two linked GPOs). These depend on link order and are a common cause of "works on one OU, not another".
- Export to Excel and give each difference an owner and a decision: adopt, adopt with a different value, or reject with a reason.
For a new release, compare the old and new baseline rule sets to isolate the settings that changed.
Tailoring and the exception register
Microsoft's Intune guidance is explicit: review each setting, enforce only the settings and values you need, and treat the baseline as a starting point. In practice the settings that most often need a local decision are predictable.
| Area | Why it often needs a decision | Typical approach |
|---|---|---|
| Legacy authentication and protocols (NTLM restrictions, SMB signing, LDAP signing and channel binding) | Old applications, printers and appliances fail silently | Enable auditing first, inventory callers from event logs, then enforce by OU |
| Credential protections (Credential Guard, LSA protection) | Incompatible drivers, smart card middleware or third-party authentication packages | Pilot ring with compatibility testing; keep exceptions machine-specific |
| Firewall policy merge | Microsoft warns that baseline firewall defaults may not merge local rules with MDM rules | Validate application rules before assignment; move needed rules into central policy |
| Defender for Endpoint baseline on VDI | Microsoft does not currently recommend it for VMs or VDI; some settings affect remote interactive sessions | Use a separate, tested profile for virtual desktops |
| Attack surface reduction rules and Office macro controls | Line-of-business add-ins and macros | Audit mode, review events, then block with scoped exclusions |
| Audit policy and log size | Volume and SIEM cost | Keep the baseline values; tune collection in the SIEM rather than reducing local auditing |
Record every deviation in an exception register: setting name and path, baseline value, your value, scope (OU, group or device filter), reason, compensating control, owner, approval date and review date. It turns the next upgrade into a review of the register.
Deploying through Group Policy
- Prepare the central store: copy the current Windows, Edge and Microsoft 365 Apps administrative templates and the baseline's custom templates into the domain's PolicyDefinitions folder.
- Import into new GPOs: use the Group Policy Management console or
Import-GPOwith-CreateIfNeededand a clear naming convention (for exampleSEC-Baseline-Win11-25H2-Computer). Never import over a live GPO; create a new object so you can switch back by changing the link. - Apply your tailoring in a separate GPO linked with higher precedence, rather than editing the Microsoft GPO. This keeps the baseline object identical to the published version and makes the next upgrade a simple replacement.
- Link to a pilot OU first containing representative devices and owners who will report problems. Use security filtering or a WMI filter only where needed, because filters are easy to forget.
- Verify on the device with
gpresult /hand a Policy Analyzer comparison of the reference machine against the baseline rules. - Expand in rings (IT, early adopters, business units, servers by role) with a fixed observation period at each stage.
- Roll back by disabling the link or removing the GPO. Be aware that some settings "tattoo" the registry or security database and do not revert when the GPO is removed; for these, apply an explicit reversal GPO or rely on rebuilds.
Domain controllers deserve their own baseline GPO and change window. Audit policy, LDAP signing and NTLM settings on domain controllers affect every client in the domain. See the Group Policy Security Guide and the Windows Server Hardening Guide.
Deploying through Intune and OSConfig
Intune security baselines
- Creating a profile: in the Intune admin center go to Endpoint security, Security baselines, choose the baseline type and create a policy. Review defaults in the configuration step, apply scope tags, then assign include and exclude groups. Intune deploys immediately to assigned groups, so assign a pilot group first.
- User or device scope: baselines are assigned to user groups or device groups depending on the settings, so full coverage may need more than one profile.
- Testing variants: use Duplicate to test a variant or a version change on a subset of devices. Duplicates copy settings and scope tags but not assignments.
- Upgrading versions: select the profile and use Update Version, choosing either to keep your customisations or to discard them. The workflow creates a side-by-side profile; assignments and scope tags are not carried over, so assign the new profile to the pilot, then remove assignments from the old one to avoid conflicts. Review update downloads a CSV of changed, added and removed settings.
- Preview baselines: Microsoft does not recommend preview baselines in production, because settings can change during the preview.
- Migrating from Group Policy: Microsoft positions baselines as useful when moving from on-premises Group Policy to Intune. Run the GPO and the Intune profile against the same pilot devices only long enough to confirm parity, then remove one; on co-managed devices make sure the workload authority is clear.
OSConfig on Windows Server 2025
- Scenarios by role:
SecurityBaseline/WindowsServer/2025/DomainController,.../MemberServerand.../WorkgroupMember, with companion scenarios for Secured-core, Defender Antivirus and Windows LAPS on member servers. - Applying: install the
Microsoft.OSConfigmodule for all users, apply a scenario withSet-OSConfigDesiredConfiguration, and read effective values withGet-OSConfigDesiredConfiguration. Individual settings can be customised and stay under drift control. - Drift control: OSConfig restores its settings automatically. If Group Policy or another tool manages the same setting with a different value, remove one source.
- Restarts and removal: applying or removing a baseline needs a restart, and removal does not guarantee settings return to their previous state, so test on a snapshot.
- Logging: the server baseline sets advanced audit subcategories for success and failure, process creation auditing with command lines (event 4688), firewall logging on all profiles, and a Security log of at least 192 MB.
- Updates: baseline versions ship inside the module and each fully supersedes the previous one; update the module, then reapply the scenario after testing.
See the Microsoft Intune Guide and the Configuration Drift and Baseline Enforcement Guide.
Where identity fits
Baselines are configuration, but they are controlled by identities and they protect identities.
- Who can change the baseline: anyone with edit rights on a GPO linked to a domain or OU, or with the Security baselines Create, Update and Assign permissions in Intune, can weaken controls across thousands of devices. ATT&CK tracks malicious changes to domain policy as T1484.001 Group Policy Modification. Microsoft lists Policy and Profile Manager as the least privileged built-in Intune role for baselines; use scoped custom roles rather than broad administrator roles.
- Tenant-wide administrators: in the Stryker Intune wiper attack, a compromised administrator created a new Global Administrator and used Intune itself to wipe devices. A perfect device baseline does nothing against an attacker holding the management plane; protect it with phishing-resistant MFA, scoped roles and multi admin approval.
- Automation accounts: pipelines that export or import GPOs, or call Microsoft Graph to manage Intune profiles, use service accounts or app registrations with powerful rights. Inventory them, scope their permissions and rotate their credentials like any other non-human identity. See the Windows Services and Service Account Security Guide.
- Credential settings in the baseline: settings such as LSA protection, Credential Guard and WDigest restrictions protect cached credentials of every account that signs in, including service and administrator accounts. Treat exceptions to these settings as high-risk.
Detection and measurement
- Intune reporting: each profile reports Succeeded, Error, Conflict, Pending and Not applicable per device, with Per setting status showing counts per setting. The Settings details pane lists every Source Profile that configures the same setting with a different value, which is how you find conflicts. First data can take up to 24 hours, later changes up to six hours.
- Device diagnostics: the Advanced Diagnostic Report under Access work or school, and the DeviceManagement-Enterprise-Diagnostics-Provider Admin log, show why a CSP setting failed.
- GPO change monitoring: audit directory service changes on GPO objects and SYSVOL so edits to baseline GPOs raise an alert. Watch for attempts to disable logging, which ATT&CK records as T1685.001 Disable or Modify Windows Event Log.
- Scheduled comparisons: run Policy Analyzer or GPO2PolicyRules comparisons of reference machines against the baseline rules on a schedule and keep the exports as evidence.
| Metric | How to measure | Healthy signal |
|---|---|---|
| Baseline coverage | Devices with an assigned and Succeeded baseline profile, or in an OU with baseline GPOs linked, divided by managed Windows devices | Above 95 percent, with the remainder explained |
| Conflict and error rate | Devices in Conflict or Error per baseline profile | Falling month on month, no conflict older than 30 days |
| Version lag | Days between a new baseline release and production assignment | Within an agreed window, for example 90 days |
| Exception count and age | Entries in the exception register and those past review date | Stable or falling; none overdue |
| Unauthorised changes | GPO or Intune profile edits outside approved change records | Zero |
Framework mapping
| Framework | Reference | How baselines support it |
|---|---|---|
| NIST SP 800-53 Rev. 5 | CM-2 Baseline Configuration, CM-2(2) Automation Support for Accuracy and Currency | Documented, versioned baseline maintained with tooling |
| NIST SP 800-53 Rev. 5 | CM-6 Configuration Settings, CM-6(1) Automated Management, Application, and Verification | Defined settings, deviations approved and recorded, automated application and checking |
| NIST SP 800-53 Rev. 5 | CM-3 Configuration Change Control, CM-7 Least Functionality, CA-7 Continuous Monitoring | Change records for baseline edits, disabled legacy features, ongoing compliance reporting |
| NIST CSF 2.0 | PR.PS-01 Configuration management practices are established and applied; DE.CM-09 | Platform security outcome; monitoring computing hardware and software for adverse events |
| CIS Controls v8.1 | Control 4 Secure Configuration of Enterprise Assets and Software (Safeguard 4.1) | A documented secure configuration process; see the CIS Control 4 Secure Configuration of Enterprise Assets and Software Guide |
| ISO/IEC 27001:2022 | Annex A 8.9 Configuration management | Established, documented and monitored security configurations |
| MITRE ATT&CK v20 | T1484.001 Group Policy Modification | Protect and monitor the policy objects that carry the baseline |
Common failure patterns
- Importing straight into production: the baseline is linked at the domain root without a pilot, legacy authentication breaks, and the whole baseline is removed under pressure and never returns.
- Editing Microsoft's GPOs in place: tailoring is mixed into the imported objects, so nobody can tell which values are Microsoft's and the next version cannot be compared or replaced cleanly.
- Two masters for one setting: GPO and Intune, or Intune and OSConfig, both manage firewall or Defender settings with different values. Devices sit in Conflict, or values flip on every refresh.
- Stranded versions: old Intune profiles stay assigned after an Update Version, the new profile never gets assignments, or both stay assigned and conflict.
- Baseline without the assumptions: users remain local administrators, so settings that rely on standard user rights can be undone by the user or by malware running as that user.
- Undocumented exceptions: settings are relaxed during an incident or project and never restored, and the next audit finds drift with no owner.
Practitioner checklist
- Download the current SCT baselines for every Windows, Microsoft 365 Apps and Edge version you run, and record the version numbers in your configuration standard.
- Run a Policy Analyzer comparison of each baseline against your existing GPOs and a reference machine; give every difference an owner and decision.
- Keep Microsoft's baseline objects unmodified and apply tailoring in separate, higher-precedence GPOs or clearly named Intune profiles.
- Maintain an exception register with reason, compensating control, owner and review date for every deviation.
- Decide one authority (GPO, Intune or OSConfig) per setting family and remove overlapping sources.
- Deploy in rings with a pilot group, verify with gpresult, Intune per-setting status or OSConfig effective values, and document the rollback for each ring.
- Restrict GPO edit rights and Intune baseline permissions to scoped roles, require phishing-resistant MFA, and alert on changes outside change control.
- Track coverage, conflicts, version lag and exception age monthly, and schedule a review within your agreed window whenever Microsoft releases a new baseline.
Standards and references
- Microsoft Learn: Security baselines
- Microsoft Learn: Microsoft Security Compliance Toolkit
- Microsoft Learn: Use security baselines to configure Windows devices in Intune
- Microsoft Learn: Manage security baseline profiles in Intune
- Microsoft Learn: Monitor security baseline profiles in Intune
- Microsoft Learn: Configure security baselines for Windows Server 2025 with OSConfig
- NIST: SP 800-53 Rev. 5
- MITRE ATT&CK: Group Policy Modification
Related NHI Mgmt Group resources: Endpoint Hardening Checklist · Windows Endpoint Hardening Guide · Group Policy Security Guide · Microsoft Intune Guide · CIS Benchmarks Guide