Device-based access policies were built to enforce control. Combine them with privilege escalation, and the story changes. An attacker who meets device compliance rules can bypass layers that should have stopped them. The security model shifts. Integrity becomes fragile.
It starts with a gap between design and reality. Organizations enforce access rules based on hardware identifiers, security posture, or MDM enrollment. But if a user gains high-level privileges while already inside those rules, the device check becomes irrelevant. Privilege escalation exploits do not care if the machine is encrypted or enrolled. At that point, the attacker is operating with the same trust your systems give to an authorized admin.
This is why device-based access policies are not a complete control. They are a snapshot, not continuous enforcement. Once initial gatekeeping is passed, they stop protecting. A policy that trusts the device without revalidating during access changes is at risk. An attacker with standard user rights can escalate privilege, manipulate session tokens, and inherit the same scope as your top-level accounts.