What a trust score actually measures
Published · Updated
6 min read
A plain-language walkthrough of the factors MFA-Brain™ weighs, and why a single score beats a stack of independent checks.
One number, many signals
Most authentication stacks run checks in isolation: a device check, an IP reputation check, a one-time code. Each returns pass or fail, and the journey is only as smart as the weakest rule.
Authiun evaluates the same signals together. Device posture, passkey presence, network context, behavioural rhythm and historical patterns are weighted into a single 0 to 100 trust score that is recalculated on every request.
What the score is made of
Possession signals confirm the request comes from a key the user actually holds. Context signals describe where and how the request arrived. Behaviour signals compare the current session against what this identity normally does.
No single factor can carry a session on its own. A familiar device on an unfamiliar network scores lower than the same device at home, and the journey threshold decides whether that is enough.
Why explainability matters
Every score Authiun produces carries the factors that moved it. That makes decisions reviewable after the fact, useful when a customer disputes a block, and necessary when an auditor asks why access was granted.
Thresholds are set per journey, so a read-only dashboard and a payment initiation do not have to share the same bar.