Device Health State
Monitoring device health metrics (CPU, memory, jailbreak/root status) to determine trustworthiness for Zero Trust access.
What is Device Health State?
Device Health State monitors various health metrics of devices to determine if they're trustworthy enough to access sensitive resources.
Key health indicators:
- Jailbreak/Root status: Is the device compromised (iOS jailbreak, Android root)?
- OS version: Is the OS up-to-date with security patches?
- Antivirus status: Is endpoint protection active and updated?
- CPU/Memory usage: Is the device under abnormal load (botnet)?
- Network performance: Unusual traffic patterns (data exfiltration)?
In Zero Trust architectures, devices with poor health state are quarantined or blocked from accessing sensitive resources.
Analogy
Think of device health state like a car's dashboard. It shows 'Check Engine' (jailbroken), 'Low Fuel' (low memory), 'Overheating' (high CPU). If the dashboard shows critical warnings, you don't let the car drive itself (untrusted device can't access sensitive data).
Types and Use Cases
- Zero Trust: Block jailbroken/rooted devices from accessing corporate resources"
- "Enterprise SSO": Require minimum OS versions (iOS 15+, Android 12+)"
- "MDM Integration": Pull device health from Intune/Jamf to make access decisions"
- "CIAM": Flag devices with suspicious CPU/memory patterns (botnets)"
How it Works
{
"deviceHealthState": {
"deviceId": "a1b2c3d4-e5f6-7890",
"metrics": {
"jailbroken": false,
"rooted": false,
"osVersion": "iOS-16.5",
"minOsRequired": "iOS-15.0",
"antivirusActive": true,
"osUpToDate": true,
"cpuUsage": "12%",
"memoryUsage": "45%"
},
"healthScore": 95,
"policies": {
"jailbroken=true": {"action": "deny", "reason": "Compromised device"},
"osVersion < minOsRequired": {"action": "requireUpdate"},
"healthScore < 50": {"action": "quarantine"}
}
}
}Device Health State vs Device Profiling
Device Health State
Device Profiling
Device Health State monitors security/compliance (jailbreak, OS version)
Device Profiling collects technical attributes (browser, screen size)
Health state is for trust decisions (block compromised devices)
Profiling is for recognition (device fingerprint)
Health requires continuous monitoring
Profiling is snapshot-based (at login)
Best Practices for Device Health State
- Block jailbroken/rooted devices: Never allow compromised devices to access sensitive data"
- "Require minimum OS versions: Enforce iOS 15+, Android 12+ for security patches"
- "Continuously monitor: Check health state throughout session (not just at login)"
How LoginRadius Powers Device Health State
LoginRadius CIAM platform provides device health monitoring: jailbreak/root detection (block compromised iOS/Android devices), OS version enforcement (require iOS 15+, Android 12+), integration APIs to pull health data from MDM solutions (Intune, Jamf), health scoring based on multiple metrics, and continuous monitoring throughout sessions. We also provide health-based access policies and detailed device health audit logs.
FAQs
Device Health State monitors security status (jailbroken/rooted, OS version, antivirus). Device Profiling collects identifying attributes (browser type, screen size, OS). Health tells you 'is this device secure?'; Profiling tells you 'what device is this?'. Both are used in Zero Trust architectures.
Yes, absolutely. Jailbroken iOS and rooted Android devices: (1) Bypass security controls (disable app sandboxing), (2) Can install malware (bypass app store checks), (3) Are considered compromised per NIST Zero Trust. Block these devices from accessing sensitive resources (HR, finance, admin portals).
LoginRadius evaluates device health through: (1) Jailbreak/root detection - block compromised iOS/Android devices, (2) OS version checks - enforce minimum versions (iOS 15+, Android 12+), (3) Integration APIs - pull health data from MDM (Intune, Jamf), (4) Health scoring - calculate trust score based on multiple metrics, (5) Continuous monitoring - check health throughout session.