TL;DR: Oak shows that financial services identity governance must cover human, machine and AI agent identities under PCI DSS, DORA, SOX and NYDFS, because review cadence, segregation of duties and examiner evidence all depend on a complete access record. Separate inventories leave regulated access invisible, so governance has to move to one live model.
Editorial analysis by NHI Mgmt Group, based on content published by Oak: “Identity Governance in Financial Services, for Every Identity Type”.
Key questions
Q: What is the best way to govern service accounts in a bank?
A: The best way to govern service accounts is to assign each one an internal owner, a defined purpose, and a documented system scope.
Q: How do payment workflows create segregation of duties risk?
A: Payment workflows create segregation of duties risk when one person can both initiate and approve a transaction, because that combines conflicting controls in a single path.
Q: How should teams certify effective access in financial systems?
A: Teams certify effective access by reviewing the access a user can actually exercise through direct entitlements, roles, groups and inheritance, not just the permissions listed on paper.
Practitioner guidance
- Map effective access, not just assigned access Resolve nested groups, inherited rights and impersonation paths before certification so reviewers see the authority an identity can actually use.
- Move to event-driven access reviews Trigger review when an identity changes role, gains privilege, goes dormant or is onboarded as a third party, instead of waiting for the next campaign.
- Treat contractor and vendor accounts as owned identities Assign an internal owner to every external account and require the same review and revocation discipline used for employee access.
Bottom line: Financial identity governance fails when people, machines and AI agents are reviewed in separate systems that cannot show effective access.
Glossary terms: Effective Access, Segregation of Duties, Machine Identity, Joiner Mover Leaver
What's in the full article
Oak's full blog post covers the operational detail this post intentionally leaves for the source:
- Implementation detail for connecting the live graph to existing IGA and ticketing workflows
- Operational guidance for reviewer context, revocation proof and management acknowledgment
- Examples of how Oak maps human, machine and AI agent identities into one model
- Details of integrations and connectors for systems the IGA cannot currently reach
👉 Read Oak's analysis of identity governance for financial services →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Financial identity governance breaks when access is split across records that do not resolve to one accountable view. The core failure is not lack of review intent, but lack of a single model that can answer who and what has access once inheritance, delegation and third-party paths are flattened. Financial firms need one governance truth set, or they will keep certifying the wrong thing.
A few things that frame the scale:
- Only 44% of organisations are currently using a dedicated secrets management system, according to the 2024 State of Secrets Management Survey.
A question worth separating out:
Q: Why do third-party accounts create audit problems?
A: Third-party accounts create audit problems because they often lack a named owner, a full inventory, and a clear business justification. Without those controls, it is hard to prove who is accountable, what access the account has, when it was last reviewed, and whether it should still exist.
👉 Read our full editorial: Financial identity governance needs one live record for all access