What is posture-based access?
Posture-based access is an access control model that evaluates device or user context before granting or continuing access to enterprise resources. Rather than trusting the user identity or network location alone, it assesses conditions such as device compliance state, encryption status, patch level, security configuration, location context, or network environment.
This allows organizations to make access decisions that reflect the actual security state of the connecting device rather than assumptions about who is using it or where they are connecting from.
Why does it matter?
Network location is no longer a reliable indicator of whether a device is safe. A remote device, a personal laptop, and a fully managed corporate endpoint can each be in very different security states depending on how they have been configured, maintained, and used.
Posture-based access helps security teams differentiate between a device that meets the organization's security requirements and one that does not, regardless of where that device is located or who claims to be using it. It shifts access decisions away from broad assumptions toward evidence grounded in the actual current state of the connecting endpoint.
How do health checks evaluate an endpoint's security posture before granting access?
Health checks query the device for specific attributes that indicate its security state. These typically include whether disk encryption is enabled, whether the operating system and key applications are at the required patch level, whether endpoint security software is running and up to date, whether the device is enrolled in a recognized management platform, and whether any high-risk indicators such as jailbreaking or rooting have been detected.
The result of these checks is compared against a defined policy, and access is granted, restricted, or denied based on whether the device meets the minimum acceptable posture for the resource being requested.
What is the difference between identity-based access and posture-based access?
Identity-based access verifies who the user is, typically through authentication credentials and, ideally, multi-factor authentication. It confirms that the person requesting access is who they claim to be.
Posture-based access verifies whether the device being used meets security requirements, independent of who is authenticating from it. A verified identity on a compromised or non-compliant device may still represent an unacceptable risk. Posture-based access adds the device dimension to what would otherwise be a purely identity-focused decision, making both the user and the endpoint subject to verification before access is granted.
Why is posture-based access a core requirement for Zero Trust Network Access (ZTNA)?
Zero Trust requires that no request be trusted implicitly based on network location or prior authentication alone. Posture-based access is the mechanism that operationalizes this principle for the device layer. Without it, Zero Trust policies can verify identity while remaining blind to the state of the device making the request, which is a meaningful gap when compromised or non-compliant endpoints represent a significant portion of the attack surface.
ZTNA policies that incorporate device posture can deny access from endpoints that fail health checks even when the user's credentials are valid, which closes a class of risk that identity-only controls cannot address.
What happens when an employee attempts to log in from a non-compliant or unpatched personal device?
The specific outcome depends on policy configuration, but common responses include full denial of access with an explanation of why the device does not meet requirements, redirection to a remediation portal where the user can address specific compliance gaps, or limited access to a restricted set of resources that do not require the same level of device trust as the full corporate environment.
The goal is to communicate clearly what the compliance gap is and provide a path to resolution, rather than leaving the user with an unexplained access failure that generates a support ticket.
How do you handle temporary access for devices that fail a posture assessment without blocking productivity?
A common approach is to define tiered access levels based on posture results rather than a binary allow-or-deny decision. A device that fails one non-critical check might receive access to low-sensitivity resources while being restricted from high-sensitivity ones until remediation is complete. Time-limited exceptions with enhanced logging can also be granted when a business justification is documented and approved.
The design goal is to maintain security intent without creating unnecessary productivity loss for users whose devices fail a check that can be resolved quickly with minimal risk in the interim.
What device telemetry metrics are checked during a posture-based access evaluation?
Common metrics include encryption status, operating system patch level, security software presence and signature currency, device enrollment status in a recognized management platform, screen lock policy enforcement, presence of unauthorized software, jailbreak or root detection on mobile devices, and certificate or certificate authority trust state.
The specific set of checks is defined by policy and may vary based on the sensitivity of the resource being accessed, with stricter requirements applied to high-value assets than to lower-sensitivity services.
Relevance for IT admins
For IT administrators, posture-based access is most effective when the endpoint management layer responsible for device compliance feeds accurate, current state data into the access control layer making the decision.
Endpoint Central can serve as that compliance data source, providing patch status, configuration compliance, software inventory, and enrollment state for managed devices that posture-based access policies can reference when evaluating whether a device meets the requirements for a given access request.
The value of posture-based access depends directly on the accuracy of the underlying device state information, which makes endpoint management quality a direct input into access security outcomes.