Risk Scoring

​

Score ranges

​

Risk factors

• Jailbreak detection — Actual jailbreak/root signals. The strongest single factor.
• Development builds — Debug, Xcode, and TestFlight installs are scored as a separate, lower-weight signal than jailbreak. A dev build alone doesn’t mark a device as compromised — it’s expected during integration.
• Device integrity — Does the attestation pass Apple’s checks?
• Suspicious activity history — Past suspicious events raise the score, with recency decay: each clean week forgives one past event, so a device that stays clean earns its trust back over time.
• Device age — New devices (fewer than 3 attestations) carry a temporary penalty that clears as attestation history builds.
• Anomaly detection — Rapid country changes, app version downgrades, VPN/proxy networks, device model inconsistencies, and unusual timing patterns.

​

Using risk data

​

By category (all plans)

let result = try await grantiva.validateAttestation()
// Trusted: 0–20 | Suspicious: 21–75 | Blocked: 76–100
let score = result.deviceIntelligence.riskScore

if score <= 20 {
    proceedNormally()
} else if score <= 75 {
    requestAdditionalAuth()
} else {
    blockAccess()
}

​

By numeric score (Pro / Business / Enterprise)

let result = try await grantiva.validateAttestation()
let score = result.deviceIntelligence.riskScore

switch score {
case 0...20:
    proceedNormally()
case 21...50:
    requestAdditionalAuth()
case 51...75:
    limitAccess()
default:
    blockAccess()
}

​

On your backend

{
  "device_intelligence": {
    "risk_score": 15,
    "risk_category": "trusted",
    "jailbreak_detected": false,
    "device_integrity": "valid"
  }
}

​

Webhooks

• device.high_risk — A device exceeds your risk threshold
• device.new — First attestation from a new device
• device.attestation_failed — A device fails attestation
• attestation.anomaly — Unusual attestation pattern detected

​

Dashboard analytics