Skip to main content

Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story

Blog

Endpoint security management: how to protect a distributed estate

Learn how endpoint security management unifies Intune, compliance evidence, and protection across physical and cloud-hosted devices.

A governance, risk, and compliance (GRC) lead asks for proof that every device in the estate has disk encryption enabled, and the answer involves three portals, two spreadsheets, and a contractor laptop nobody ever enrolled.

Unified endpoint management lives in the space between a written baseline and an enforced one. Verizon's 2026 DBIR puts exploitation of vulnerabilities at 31% of breaches, up from 20%, now the most common initial access vector.

This guide is for platform owners managing Windows 365, Microsoft Intune-enrolled physical devices, and Azure Virtual Desktop. GRC leads can use it to verify policy enforcement across the distributed estate.

What endpoint security management covers when your endpoints live in three places

Endpoint security management means enrolling every device that touches corporate data, configuring it to a known baseline, patching it, and re-verifying it before Conditional Access grants access.

The management half of that work is where distributed estates leak. TechTarget's ESG analysis found that 31% of endpoints accessing corporate resources are unmanaged, and 59% of those unmanaged endpoints have no SASE or zero trust coverage. An unmanaged laptop is invisible to the compliance policy you wrote for it. Microsoft's Digital Defense Report stated that over 90% of ransomware attacks reaching the encryption stage used unmanaged devices as the initial access point or for remote encryption.

Gartner files endpoint management tools under IT infrastructure and endpoint protection platforms under IT security, two different taxonomy branches. Management keeps a device in a known-good state. Security defends the device once something gets through.

"Every device" now includes Intune-enrolled physical laptops alongside cloud-hosted endpoints under Windows Cloud, Microsoft's umbrella term for Windows 365 Cloud PCs and Azure Virtual Desktop hosts. Many enterprises run both cloud desktop services next to a physical fleet, and each endpoint shape enrolls through its own path with its own policy exceptions.

Generic endpoint-security advice rarely accounts for those differences, so the first step is pinning down which Microsoft tool owns which layer.

Where Microsoft Defender for Endpoint stops and Intune begins

Microsoft Defender for Endpoint is the EDR layer that responds to threats on a device. Intune is the unified endpoint management layer that defines the state a device must hold. Microsoft describes Intune as "a cloud-based endpoint management service that secures and manages your organization's devices and apps." For Windows, Intune's endpoint security policies include the following.

  • Antivirus
  • Disk encryption
  • Firewall
  • Endpoint detection and response
  • Attack surface reduction
  • App Control for Business
  • Account protection

Intune and Microsoft Defender surface those same policies in two portals. Administrators can edit endpoint security policies from both the Intune admin center and the Microsoft Defender portal, as Microsoft documents. The Defender view requires access to all devices plus Core security settings (manage) permissions, and it can deliver a subset of those policies to devices running Defender for Endpoint without an Intune enrollment.

Two portals with separate permission models create an operational risk where a setting can change in one place without anyone noticing in the other.

Gartner's taxonomy places a management layer above Intune in its IT operations branch, while endpoint protection sits in its security branch. Nerdio Manager for Enterprise is that kind of layer. It orchestrates Intune policy and combines that state with Defender threat data so teams can see enrollment and compliance status before an incident. That visibility only pays off when access decisions depend on device compliance.

Access depends on device compliance

Under NIST SP 800-207, zero trust grants "no implicit trust" to "assets or user accounts based solely on their physical or network location," and its fourth tenet requires access decisions to weigh device health and patch level. In the Microsoft stack, Intune compliance policies produce that signal. Per Microsoft Learn, "The compliance policy evaluation determines the device's compliance status, which is reported to both Intune and Microsoft Entra ID." Conditional Access then decides whether to allow or block the device.

Intune marks devices with no compliance policy assigned as Compliant, so a device that never received a policy passes a Conditional Access check that requires compliance. Microsoft recommends configuring that setting as Not compliant when Conditional Access is in use.

Windows 365 Conditional Access spans three Entra app IDs (Windows 365, Azure Virtual Desktop, and Windows Cloud Login), and Microsoft recommends matching policies across all three. Cloud PCs don't support BitLocker or Administrator protection, so exclude both settings from Cloud PC compliance policies. That split requires separate baseline assignments and evidence checks for cloud-hosted endpoint types.

Intune treats personal Azure Virtual Desktop hosts like physical Windows Enterprise desktops. Multi-session hosts have different limits:

Every exception is a place where enforcement can differ from the policy document, which is the drift problem.

Written policy and enforced policy drift apart between audits

Gartner's August–October 2024 survey of 162 large enterprises put the average at 45 cybersecurity tools. Plenty of those estates are tool-rich and process-poor. Inside Intune alone, Microsoft documents the conflict paths. Security baselines set non-default values while endpoint security and device configuration policies default to Not configured, and Microsoft warns that mixing them can create conflicts that administrators must identify and resolve manually.

Intune allows only the most recent version of a baseline to create a new instance. When you move a profile to a newer version, the newer version stops enforcing settings it omits. You don't notice a setting that stopped being enforced until an auditor asks for it.

For virtual desktop infrastructure (VDI), Microsoft also marks the Defender for Endpoint baseline as "Not recommended for use on VMs or VDI endpoints" because certain settings disrupt remote interactive sessions.

NIST SP 800-137 describes managing configurations as having "become almost impossible using manual methods." Recovering a deleted Intune policy requires separate backup tooling. Otherwise, recovering from an accidental deletion means rebuilding it by hand.

Patching carries the same design gap, and the clocks your obligations impose are short:

Against those clocks, the 2026 DBIR healthcare snapshot measured a 43-day median to fully resolve CISA KEV-listed critical vulnerabilities, with only 26% fully remediated.

Windows Autopatch automates the rings, but administrators assign devices to First, Fast, or Broad without controlling when updates push or when a device moves between rings, so the timing decision has to live in a scheduling layer above it. Nerdio Manager supplies that orchestration through built-in scripts for automated Windows patching tied to Patch Tuesday schedules without replacing Microsoft tooling. Regulators want to see the record of all of it.

Turn endpoint controls into audit evidence

The HIPAA Security Rule, PCI DSS, GDPR Article 32, NIS2 Directive, and Cyber Essentials all address endpoint security in different ways, with overlapping themes across four areas, though the exact requirements and terminology vary by framework:

  • Asset inventory
  • Encryption
  • MFA and access control
  • Timely patching

One enforced baseline can therefore generate evidence for several audits at once, provided the evidence exists somewhere other than an engineer's memory.

Healthcare carries the highest breach cost and the tightest rules

Healthcare is the sharpest case. IBM's 2026 Cost of a Data Breach Report ranked healthcare the costliest industry for the thirteenth consecutive year at USD 6.64 million per breach. That cost makes current endpoint state part of the risk record, not just an operations detail.

Under the current HIPAA Security Rule, organizations must set up audit controls (45 CFR § 164.312(b)) and person or entity authentication, while HHS OCR's January 2026 cybersecurity newsletter points to an up-to-date IT asset inventory as the foundation for patching obligations. The January 2025 NPRM, which remains proposed and not finalized, would mandate MFA and encryption of ePHI at rest and in transit. Together, those rules make current device state and change history part of the audit answer.

MFA and encryption deadlines are already in force outside healthcare

Outside healthcare the clocks are already running. Cyber Essentials made MFA mandatory for every cloud service that offers it from April 27, 2026, with failure an automatic assessment fail. GDPR Article 32 is risk-based rather than prescriptive, but the ICO's remote-working checklists call for "encryption and remote wiping capabilities" on mobile devices and MFA "configured where possible."

Prove each control reached each endpoint

Deadlines only matter when teams can show which endpoints met them. An Intune compliance report plus an audit log gives your auditor the current state and the change history.

A scope tag record of who could change what closes the last gap. Your team stops rebuilding the answer on a Teams call the week the assessment lands.

A management platform centralizes that evidence for all three supported endpoint shapes without a spreadsheet and does not certify compliance.

How Nerdio Manager unifies endpoint security management across the estate

Nerdio Manager deploys from Microsoft Marketplace and runs inside your Entra ID tenant and Azure subscription. It is a management platform that applies policy automation and role-based access control to its orchestration workflows. Those workflows include audit logging. Security enforcement itself comes from Intune and Defender for Endpoint, which Nerdio Manager orchestrates.

Its agentless insights and monitoring place no third-party agent between Intune and the endpoints it manages.

One console for Intune management

Nerdio Manager consolidates Intune policy and compliance work in one place. It also handles app deployment and recovery-key lookup alongside Intune policy and compliance work. It can create an Intune policy backup and restore it later. This provides separate backup tooling for deleted policies. Intune reporting provides the compliance view to whoever owns the audit.

Syneos Health reported 70% faster configuration changes. Unified Application Management deploys apps to Cloud PCs in about 30 seconds through WinGet. Native Intune delivery can take up to three hours because Intune polls on its own schedule.

CIS-aligned baselines and hardened images for virtual desktops

Nerdio's Modern Work CIS Baselines are CIS Certified, and the CIS Hardened Images integrated into Nerdio Manager ship preconfigured to meet CIS Security Benchmarks for Windows 11 and Windows Server. Nerdio integrated CIS Hardened Images directly into the product in August 2024. The configuration profile follows CIS Level 1. Desktop orchestration automates updates and versioning of hardened images for session hosts and personal desktops after the initial build. It also automates their distribution.

Note that CIS hardened images do not support Unified Application Management and the CIS Certified designation applies to Nerdio's baselines and images as shipped.

Delegated administration with an audit trail

Built-in and custom roles support delegated administration with granular permissions. A Tier 1 technician can restart or reimage a Cloud PC from Nerdio Manager without escalating.

Policy backup, Intune reporting, and delegated administration go after unenforced baselines and settings someone changed in one portal without anyone noticing in the other.

Nerdio Manager aligns with CIS and supports the requirements of HIPAA and GDPR, though it does not certify compliance with any of them. Its Intune policy and compliance reporting shows whether assigned controls reached each supported endpoint shape in the estate.

What to change in the next 90 days

The GRC evidence request should not end in three portals, two spreadsheets, and an unenrolled laptop. The next steps are to reconcile enrollment and enforce one versioned baseline for each endpoint shape, with access dependent on compliance.

  1. Reconcile enrollment first, because unmanaged endpoints sit outside the compliance policies you wrote. Compare your Intune device list against your identity and EDR inventories, then enroll or block whatever is missing. Flip the "no compliance policy assigned" default to Not compliant and confirm Conditional Access covers all three Windows 365 app IDs.
  2. Pick one baseline per endpoint shape, version it, and record every deviation the way NIST SP 800-128 describes.
  3. Set your patch deadline to the strictest obligation you carry, whether that is the Cyber Essentials clock or the PCI DSS clock, and measure your estate against it every month throughout the year.

If your platform team is running Intune-managed laptops next to Cloud PCs and session hosts, and your GRC lead is asking where the evidence lives, centralized policy backup and Intune reporting put policy state, change history, and compliance reports in one place.

Get a demo to see how Nerdio Manager works across your Windows 365, Intune, and Azure Virtual Desktop estate, or try it free in your Azure tenant.

Frequently asked questions about endpoint security management

Ready to get started?