A liveness method that changes the required action each time the user is verified. By making the prompt unpredictable, the system reduces the value of pre-recorded media and scripted spoofing attempts. This approach is especially useful when an organisation needs stronger fraud resistance without relying only on static selfie matching.
What Randomised Liveness Challenges Do
Randomised liveness challenges are designed to prove that a person is present in real time by varying the requested action from one check to the next. That unpredictability makes it harder to reuse replayed video, still images, or scripted spoofing flows, so the test is more resistant to pre-recorded fraud than a static prompt.
Why Randomisation Improves Liveness Assurance
The security value of the method comes from removing the attacker’s ability to prepare a single reusable artefact. If the system always asks for the same blink, turn, or phrase, a spoof can be rehearsed against that fixed pattern; if the action changes each time, the attacker has less certainty and less time to adapt.
This makes the control especially useful where liveness is being used as a fraud-resistance signal rather than as a standalone identity proof. It is strongest when paired with other checks, because a live response can show presence without proving that the person is the right person, or that the capture environment is trustworthy.
Where It Fits in Verification Flows
Randomised liveness is usually one step in a broader verification journey that may include document checks, selfie comparison, device signals, or risk scoring. Its role is to reduce spoofing confidence at the moment of capture, not to solve the entire onboarding or authentication problem by itself.
Because the prompt changes each time, implementations need a clear challenge generator, a capture flow that can handle variable instructions, and a decision model that treats failure as a risk signal rather than an automatic proof of fraud. If the user experience is too confusing or the challenge is too hard to follow, legitimate users can be rejected even when they are genuinely present.
When the control is used in regulated or high-risk identity journeys, the surrounding treatment of biometric data and verification evidence matters as much as the liveness prompt itself. For a broader control context, organisations often map the surrounding access and verification requirements to NIST SP 800-53 Rev 5 Security and Privacy Controls and to NIST SP 800-63 Digital Identity Guidelines when identity assurance is part of the design.
Common Failure Modes and Evasion Paths
The main weakness of any liveness method is that it must distinguish a live human from a convincing imitation under real-world conditions, not just in a lab. Randomisation raises the bar, but attackers can still use deepfake video, real-time relay setups, injected media, or hybrid tactics that combine synthetic content with human assistance.
Failure usually occurs when the check is too predictable, when the challenge is visible to an accomplice too early, when the application accepts poor-quality evidence, or when the fraud model over-trusts one signal. A resilient deployment needs to assume that attackers will adapt their capture method once they understand the prompt pattern.
For organisations that want to understand the surrounding adversary behaviours, the challenge is best viewed alongside MITRE ATT&CK Enterprise Matrix for abuse patterns and MITRE ATLAS adversarial AI threat matrix where synthetic media or model-assisted deception is part of the threat path.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Liveness supports user authentication assurance in identity verification flows. |
| Recommendation — Require stronger identity verification controls where liveness is used to establish user presence. | ||
| NIST SP 800-63 | Digital Identity Guidelines | The term sits within digital identity assurance and anti-spoofing verification design. |
| Recommendation — Align liveness checks with assurance level and verifier requirements in the identity proofing flow. | ||
| MITRE ATT&CK | T1185 — Browser Session Hijacking | Replay and relay abuse can support fraudulent access paths that liveness aims to resist. |
| Recommendation — Hunt for replay and relay indicators when liveness challenges are being bypassed. | ||
Practitioner Guidance
Why practitioners should care: Randomised liveness should be treated as a fraud-control enhancement, not as a standalone guarantee of identity. Its value comes from forcing the attacker to respond in real time, so it works best when the organisation can tolerate some friction in exchange for stronger spoof resistance.
What to watch for: Review how often the same challenge patterns recur, how users fail, and whether suspicious sessions cluster around specific devices, channels, or geographies. If challenge variety is weak or operational staff can predict the sequence, the control loses much of its advantage.
Practitioner takeaway: Use randomisation to make replay attacks less practical, but calibrate it to the risk tier of the journey and keep a fallback path for users who cannot complete the challenge reliably.
Related resources from NHI Mgmt Group
- Why do randomised liveness checks reduce the risk of deepfake and spoofing attacks in identity verification?
- Should banks compare passive liveness with active challenge flows?
- Why do machine identities challenge zero trust architectures?
- How do security teams evaluate whether liveness detection is strong enough?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org