Device posture assessment for network access control

Device posture assessment checks whether a device is healthy enough to be on the network. It looks at patch level, disk encryption, antivirus, firewall and enrolment. It can run once at admission, or continuously, using Change of Authorization to act on a live session. Agent-based posture sees managed devices in depth, but it cannot reach BYOD or IoT. Identity-first access closes that gap. Each device is authenticated and segmented by role, so it can only reach what its role allows.
IN THIS ARTICLE
Device posture assessment is the check that asks: is this device healthy enough to be on the network? This page explains what posture inspects, the two ways it runs, how it plugs into the access decision, the cost of agent-based posture, and where identity-first access does the heavier lifting.
What device posture assessment is
Posture assessment inspects the state of a device before or during network access. Typical checks:
- Is the operating system patched to a required level?
- Is disk encryption on?
- Is antivirus or endpoint protection running and current?
- Is a host firewall enabled?
- Is the device managed and enrolled, and does it carry the expected certificate?
If the device passes, it gets normal access. If it fails, it is blocked, quarantined to a remediation VLAN, or granted limited access until it is fixed.
Pre-admission versus continuous
There are two timing models, and they answer different questions.
- Pre-admission posture checks the device once, at the moment it joins. It answers “is this device healthy right now?” and then trusts it for the session.
- Continuous posture re-checks during the session. If a device falls out of compliance — antivirus stops, encryption is turned off — the system reacts mid-session.
Continuous posture needs a way to change a live session. That mechanism is Change of Authorization (CoA, RFC 5176): the policy server sends the access point a message that moves the device to a quarantine VLAN or disconnects it. Without CoA, posture is a one-time gate, not an ongoing control.
Agent-based versus agentless
Posture also splits on how it sees the device.
- Agent-based posture installs software on the endpoint that reports its health in detail. It is the deepest signal, and it is the most expensive to run.
- Agentless posture infers state from the outside — fingerprinting, profiling, and signals from other systems. It is lighter, and it sees less.
Agent-based posture gives you the deepest view of the devices you fully manage, and no view of the devices you do not.
The cost of agent-based posture
Agents are powerful and demanding:
- They must be installed and kept current on every device.
- They cannot be installed on unmanaged personal devices, and users resist them.
- They do not exist for headless and IoT devices at all.
- They add a second system to operate alongside the network.
In a world of BYOD and IoT, the fraction of the network an agent can see is shrinking. Posture that depends only on agents is posture with a growing blind spot.
The identity-first alternative
There is a different starting point. Instead of trusting a device once it passes a health check, assume no device is fully trusted, authenticate the user and device by identity, and segment tightly by role.
This is the model cloud-native NAC uses. Each user connects with a certificate or a per-device key, not a shared password. Identity maps to a VLAN and a policy. A compromised or unpatched device can only reach what its segment allows, regardless of its posture signal.
Identity-first access does not replace posture. It reduces how much you depend on it. When segmentation is tight, a device that fails a posture check is already limited by its role, not just by the check.
How the two layers work together
The strongest designs use both, at the layer each is good at:
- The endpoint layer — an MDM or endpoint protection platform runs the agent and reports device health.
- The network layer — NAC authenticates by identity, segments by role, and can act on a posture signal through CoA.
Together they answer both questions: is the device healthy, and is it allowed where it is trying to go.
How Cloud4Wi fits
Cloud4Wi’s Cloud NAC operates at the network layer. It authenticates users and devices by identity — certificates for managed devices, the Cloud4Wi BYOD app for personal ones, PPSK and MAC authentication for headless and IoT — on built-in cloud RADIUS, and applies role-based segmentation and monitoring. It integrates with your identity provider, so access follows the person.
For deep endpoint health, Cloud NAC complements an MDM or endpoint protection platform rather than replacing it. The MDM inspects the device; Cloud NAC controls what an authenticated, segmented device can reach. That division keeps the network-layer control simple and lets the posture signal come from the tool built to produce it.
Frequently asked questions




