A common mistake is assuming identity assurance is enough on its own. If the endpoint is unmanaged, compromised, or non-compliant, a valid login can still become an unsafe session. Security teams need to evaluate both who is authenticating and from what device, because identity-only controls do not fully reduce risk in modern access environments.
Why This Matters for Security Teams
Identity controls are often treated as the gate, but endpoint trust determines whether the session is actually safe. A valid user or service identity can authenticate from a compromised laptop, a jailbroken mobile device, a rogue VM, or a non-compliant build agent and still inherit access. That is why modern access decisions need both identity assurance and device posture, especially in environments using conditional access, PAM, and Zero Trust. NIST’s Cybersecurity Framework 2.0 emphasizes continuous risk handling, not one-time login approval.
NHIMG research shows how quickly identity risk becomes operational: the Ultimate Guide to NHIs notes that only 5.7% of organisations have full visibility into service accounts, and 79% have experienced secrets leaks. Those numbers matter here because unmanaged endpoints and unmanaged identities often fail together, creating a path where “authenticated” becomes “trusted” by mistake. In practice, many security teams discover this only after a compromised endpoint has already been used to access production systems.
How It Works in Practice
The practical error is letting identity signal carry more weight than device signal. Identity proves who or what is trying to connect, but endpoint trust indicates whether the source environment is known, managed, compliant, and sufficiently hardened. For human users, that usually means combining SSO, MFA, and device posture checks. For non-human identities, it means validating both the workload identity and the execution environment before granting access to secrets, APIs, and sensitive data.
Current guidance suggests using layered decision points rather than a single access check. A strong model includes:
- device compliance signals such as patch level, encryption, EDR status, and MDM enrollment
- session-level policy evaluation at request time, not just at sign-in
- short-lived credentials and restricted token scopes so a trusted login does not create broad standing access
- continuous re-evaluation when posture changes, such as endpoint quarantine or jailbreak detection
This is especially important for NHI-heavy environments. NHIMG’s Top 10 NHI Issues highlights how excessive privilege and poor visibility amplify risk, while the 52 NHI Breaches Analysis shows that compromised identities often become the easiest route into downstream systems. The right control pattern is to treat endpoint trust as a required input to authorisation, not as a nice-to-have signal after login. These controls tend to break down when legacy VPNs, unmanaged BYOD, or headless automation endpoints cannot produce reliable posture telemetry because the access stack cannot distinguish safe from unsafe sessions.
Common Variations and Edge Cases
Tighter endpoint controls often increase friction, requiring organisations to balance stronger assurance against user disruption and operational exceptions. That tradeoff is real, especially where third-party contractors, shared workstations, air-gapped systems, or developer tools are involved. Current guidance suggests not every endpoint can be treated the same way, and there is no universal standard for this yet.
Some environments need compensating controls instead of full device management. For example, a build server may never look like a laptop, but it can still be trusted through workload identity, network restrictions, and tightly scoped access to secrets. Likewise, a BYOD device might be allowed into low-risk applications while being blocked from privileged admin paths. For NHI and agentic workflows, the issue is sharper because an autonomous workload may pivot across services if the runtime is compromised. That is why endpoint trust should include the host, container, or orchestration layer, not only the login origin. Where endpoint telemetry is absent, incomplete, or easy to spoof, identity-only policies become fragile and the organisation ends up approving sessions it cannot truly verify.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207), NIST SP 800-63 and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AC-4 | Access decisions should include device trust, not identity alone. |
| NIST Zero Trust (SP 800-207) | SC-7 | Zero Trust requires continuous verification of source conditions. |
| NIST SP 800-63 | AAL2 | Identity assurance levels do not replace device trust checks. |
| OWASP Non-Human Identity Top 10 | NHI-05 | Compromised endpoints can expose NHI secrets and tokens. |
| NIST AI RMF | AI risk guidance supports continuous context-aware access decisions. |
Use ongoing risk evaluation so authenticated agents do not inherit unsafe access from compromised hosts.
Related resources from NHI Mgmt Group
- What do organisations get wrong when they rely on autofill without training users on secure item handling?
- What do organisations get wrong when they try to secure flexible work with legacy controls?
- What do organisations get wrong when they rely on password security alone to stop account takeover?
- What do organisations get wrong when they rely on trust-centre automation?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 26, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
