Notifications
Clear all
Topic starter
02/08/2026 12:30 pm
TL;DR: The real issue is not storage of credentials, but controlling the operator journey around privileged access, according to Island. Island describes how a global airline used an enterprise browser to mediate access to CyberArk, hide irrelevant privileged credentials by role, and enforce policy-driven choices inside Azure administration workflows so auditors can trace changes end to end.
NHIMG editorial — based on content published by Island: Updated: WWLW Ep. 6, the case of the unmanageable privileged access
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: How should security teams reduce privilege creep without slowing access requests?
A: Move the decision to request time.
Q: Why is privileged access hard to manage in 24x7 operational environments?
A: Because operators need fast access to sensitive credentials while the organisation still needs strong misuse prevention and traceability.
Q: What do IAM teams get wrong about privileged access management?
A: They often treat privileged access as just another user access category, which hides the extra risk attached to admin rights and high-impact credentials.
Practitioner guidance
- Map the full privileged operator journey Document where admins discover, retrieve, and use credentials, then identify the points where visibility should be reduced or action choices constrained.
- Limit credential visibility by role and task Expose only the privileged credentials needed for the current role or group, and review whether any operators can see credentials they do not need.
- Enforce policy at the point of cloud action Apply rules inside administrative workflows so operators can only select approved infrastructure options, especially in portals used to create servers, networks, or access paths.
What's in the full article
Island's full blog post covers the operational detail this post intentionally leaves for the source:
- How the browser is positioned as the only access path to CyberArk in this airline workflow
- The specific role-based display logic used to narrow which credentials each operator can see
- Examples of browser-enforced policy rules inside Azure administration tasks
- The auditor traceability model used to follow a privileged change through the full cycle
👉 Read Island's analysis of browser-based privileged access governance →
Privileged access in the browser: what it means for IAM teams?
Explore further
02/08/2026 1:28 pm
Privileged access governance fails when the control point sits too far from the action. Storing credentials in a vault is necessary, but it does not by itself govern what the operator sees, chooses, or does after retrieval. Browser mediation pushes control closer to the actual administrative act, which is where misuse, accidental exposure, and policy drift usually emerge. The practitioner lesson is that PAM success depends on shaping the execution path, not only protecting the secret.
A few things that frame the scale:
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months, according to The State of Non-Human Identity Security.
- A separate finding shows that 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, which reinforces how much governance still depends on incomplete identity context.
A question worth separating out:
Q: How can organisations improve auditability for privileged IT changes?
A: Link login events, credential retrieval, policy decisions, and final configuration changes into one traceable workflow. That makes it possible to show not only that access occurred, but that the access path was constrained and the change was intentional.
👉 Read our full editorial: Enterprise browser controls for privileged access governance
