Join our Newsletter — 33% off our NHI Course

What happens when workflow friction widens privileged access?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Workflow friction can push engineers toward broader, less precise requests in privileged access, according to Apono. Least privilege depends on access design that stays usable under real developer pressure.

Editorial analysis by NHI Mgmt Group, based on content published by Apono: “Apono vs StrongDM: Which Privileged Access Solution Delivers Better Developer Experience?”.

Key questions

Q: When does workflow friction create the most security risk in privileged access?

A: Workflow friction creates the most risk when teams are under incident or debugging pressure.

Q: What are the signs that a privileged access model is too rigid?

A: Common signs include repeated access re-submissions, broad requests that are more generous than the task requires, and growing dependence on pre-created access bundles.

Q: What breaks when privileged access workflows are too friction-heavy?

A: When privileged access workflows are too friction-heavy, engineers often respond by requesting broader access than they actually need.

Practitioner guidance

  • Align access requests to engineering workflows Embed privileged access requests into Slack, CLI, portals, or other tools engineers already use so the secure path is the easy path.
  • Map task intent to scope guidance Provide guidance that translates common operational tasks into the smallest appropriate permission set, especially for debugging and incident response.
  • Review broad-request patterns Track when users repeatedly ask for wider access after failed or delayed requests, then treat those patterns as evidence that the access model is too brittle.

Bottom line: Workflow friction can undermine privileged access even when policy and enforcement are technically strong.

Glossary terms: Developer experience in privileged access, Workflow friction, Access scope inflation

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Workflow friction is a privileged access control failure, not a usability side issue. When engineers cannot express the right request quickly, they will optimise around the system by asking for broader access. That turns the request path into the real control boundary, which means least privilege can fail before enforcement even begins. The practitioner conclusion is that access experience is part of the security design.

A few things that frame the scale:

A question worth separating out:

Q: How should security teams run access reviews using least privilege?

A: Security teams should anchor each review to current job need, not historical entitlement approval. The reviewer should ask whether the identity still requires each permission today, whether the access is still being used, and whether the account should be narrowed or removed. Least privilege only works when review decisions lead to actual revocation, not just attestation.

👉 Read our full editorial: Developer experience is the hidden control in privileged access



   
ReplyQuote
Share:

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.