TL;DR: Operational risk now overlaps with identity governance as shadow IT, shared credentials, and vendor dependencies can bypass normal controls, according to Panorays. Continuous monitoring and trusted access paths matter because weak visibility lets small failures compound into wider exposure.
Editorial analysis by NHI Mgmt Group, based on content published by Panorays: “Operational Risk Management: Strategies for Business Resilience”.
Key questions
Q: Why do browser extensions and other user-installed tools create operational risk?
A: They create operational risk because they often inherit browser context, user sessions, and permissions that security teams never intended to grant.
Q: How should organisations prioritise third-party risk inside operational risk programmes?
A: They should prioritise the third parties that sit closest to critical services, revenue, sensitive data, or privileged access.
A: When shadow IT bypasses normal controls, the organisation loses visibility into who can access what, what data those tools can touch, and which approval paths were skipped.
Practitioner guidance
- Map operational risk to identity trust paths Identify where access decisions, credential sharing, and third-party permissions sit inside critical workflows so you can see which failures can become business interruptions.
- Review browser extension permissions continuously Inventory sanctioned and unsanctioned extensions, then compare their privileges with the data and sessions they can reach in the browser.
- Tie KRIs to control drift Track access anomalies, vendor score changes, and recurring process exceptions so that risk reporting reflects live operational weakness rather than stale quarterly status.
Bottom line: Operational risk now overlaps with identity governance because unapproved tools, shared credentials, and vendor dependencies can bypass normal controls.
Glossary terms: Operational Risk Management (ORM), Key Risk Indicator, Shadow IT, Third-party risk management
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Operational risk has become an identity governance problem. The article is right to frame losses as a blend of people, process, systems, and external events, but the governance difference today is that many of those failures now begin with unmanaged access paths. Shadow IT, unsanctioned browser extensions, and casual credential sharing all create hidden trust relationships that standard control reviews often miss. The practical conclusion is that operational risk programmes now need identity-aware visibility, not just process documentation.
A question worth separating out:
Q: How do security teams know whether ICT risk controls are actually working?
A: Security teams should look for evidence that risk information is current, traceable, and usable in day-to-day decision-making. Useful signals include clean integration with source systems, clear ownership, timely updates after change, and risk views that support prioritisation. If reports are hard to reconcile or quickly outdated, the control is not working well.
👉 Read our full editorial: Operational risk management now depends on identity and vendor controls