The amount of challenge an organisation can introduce before legitimate users start abandoning the journey. In fraud-heavy environments, it becomes a governance constraint, not just a UX preference, because every extra step has both security value and conversion cost.
What the friction budget actually measures
Friction budget is not a fixed usability score. It describes how much extra effort you can ask of a legitimate user before the journey starts to break down, which means the right threshold depends on the user population, the sensitivity of the action, and the trust level already established.
In practice, the same login, recovery, or payment flow can tolerate very different levels of challenge. A low-risk action may need only light verification, while a high-risk action can justify more steps because the added friction is part of the control, not an accidental usability defect.
Why friction budget is a governance decision
The key issue is trade-off management. Every additional prompt, check, or delay can reduce abuse, but it also increases abandonment, support demand, and the chance that users seek unsafe workarounds. That makes friction budget a policy choice about how much inconvenience is acceptable for a given trust boundary.
Organisations usually discover the budget only after measuring drop-off, false rejects, and recovery volume. NIST Cybersecurity Framework 2.0 is useful here because it frames the problem as a balance of governance, protection, and recovery outcomes rather than a pure UX preference.
Where friction helps and where it backfires
Friction is most valuable when the action is high impact, high value to attackers, or hard to reverse, such as account recovery, password resets, payment changes, or privileged approval paths. In those cases, the extra step can interrupt fraud, reduce automation, or create a stronger trust checkpoint.
It backfires when the organisation applies the same hurdle everywhere. Excessive friction on routine tasks trains users to ignore controls, reuse risky shortcuts, or abandon legitimate activity. NIST SP 800-63 Digital Identity Guidelines is relevant because it ties assurance decisions to the risk of the transaction, not just to a desire for more verification.
How friction budget should be tuned
A useful friction budget is calibrated by risk, not by habit. Higher assurance should be reserved for moments where the organisation can point to a clear threat, a meaningful loss scenario, or a sensitive workflow that warrants extra challenge.
The strongest implementations are adaptive. They increase friction when signals suggest fraud, account takeover, or unusual behaviour, and stay lighter when the session is low risk. NIST AI Risk Management Framework and NIST Privacy Framework both reinforce the broader principle that controls should be proportionate to expected harm and user impact.
Risk and Threat Considerations
When friction budgets are misjudged, the organisation either gives attackers an easy path or drives legitimate users into unsafe behaviour. Too little friction can make fraud, takeover, and automated abuse easier; too much can push users toward weaker recovery paths, help-desk escalation, or repeated retries that erode control quality.
Failure mechanism: The control fails when friction is applied uniformly instead of conditionally, so low-risk users experience unnecessary burden while high-risk activity receives no meaningful extra challenge.
Impact: The result is higher abandonment, weaker trust in the journey, more support load, and, in fraud-heavy environments, a net loss of security because users start bypassing the intended control path.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-63, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk Management Strategy | Friction budget is a risk trade-off that needs governance and measurable tolerance. |
| Recommendation — Define acceptable friction thresholds for each journey based on risk and business impact. | ||
| NIST SP 800-63 | IAL — Identity Assurance Level | Identity assurance decisions should scale with transaction risk and user impact. |
| Recommendation — Match verification strength to the assurance needed for the specific action. | ||
| NIST SP 800-53 Rev 5 | IA-8 — Identification and Authentication (Non-Organizational Users) | User-facing challenge controls affect how external users authenticate and proceed. |
| Recommendation — Tune authentication challenges so they deter abuse without causing excessive legitimate abandonment. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Friction budget affects how access checks are governed across sensitive journeys. |
| Recommendation — Set policy for when access flows require stronger checks and when they should remain streamlined. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | The term concerns how much control overhead users can bear before the workflow breaks. |
| Recommendation — Adjust access control steps to the sensitivity of the task and the user journey. | ||
Practitioner Guidance
Governance implication: Treat friction as a managed security threshold, not a design preference. Set explicit ownership for where extra challenge is allowed, where it must be avoided, and which journeys may justify stronger controls because the security payoff outweighs the conversion cost.
What to watch for: Rising drop-off, repeated retries, help-desk assisted workarounds, and sudden spikes in recovery traffic are signs that the budget is too tight or too loose for the risk level of the journey. The practical goal is not minimum friction, but the right amount of friction for the threat.
Related resources from NHI Mgmt Group
- When does zero trust IAM create more friction than risk reduction?
- How should organisations implement PSD2 controls without adding too much checkout friction?
- How should security teams implement zero trust authentication without adding too much user friction?
- How should security teams replace traditional MFA without creating new access friction?
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 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org