User access reviews at banks: from paper signatures to examiner ready evidence
Why user access reviews at community banks still run on spreadsheets and signatures, why core banking systems make it hard, and how to automate the review without changing a single system.
Thomas Bieser, Cofounder and CEO ·
Ask the person responsible for information security at a community bank what keeps them busy, and access reviews come up early. Not provisioning speed. Not single sign on. The quarterly review where every manager confirms who can reach what, and the bank proves to its examiners that it happened.
Over the last quarter we have heard the same story from banks of very different sizes. This post describes what we heard, without naming anyone, and what we have found works.
What access reviews look like at most banks today
At one bank, close to two hundred applications are reviewed by a few people in IT. The process goes like this.
- Export. Someone logs in to each system and pulls a user list, often as a report or a screenshot.
- Translate. Core banking and payment systems express access as role and permission codes. Someone has to turn those into something a branch manager can understand.
- Distribute. Spreadsheets or printouts go to managers and application owners.
- Collect signatures. Approvals come back on paper or by email, at different speeds.
- Remove. Access marked for removal becomes a ticket to the application owner, who removes it by hand.
- File the evidence. Everything is assembled for the next exam.
Another bank does this monthly. Access information, with timestamps, is pulled from each application into a spreadsheet or PDF, reviewed, and removals are sent as tickets to each app's administrator.
Everyone involved agrees the process is not sustainable. There are not enough hours in a quarter to review every application properly with a small team, so reviews get compressed, and the riskiest systems get the least attention because they are the hardest to export from.
Why core banking makes it harder
Identity governance tools review access by reading it from each application. That works for modern SaaS apps with connectors. It breaks on the systems banks depend on most.
- Core banking platforms often have no direct integration path for identity tools. One bank told us its core provider offered no supported way to connect its access data, so every subsystem was reviewed by hand.
- Access is in codes, not names. A teller's permissions in a core system are a set of codes and limits. A reviewer cannot approve what they cannot read.
- Custom integration is slow and expensive. Banks we spoke with had been quoted custom development projects for these systems that cost more than the governance tool itself.
- Upgrades do not help. Moving every application to its top plan to get a connector, where one exists at all, multiplies cost and still leaves out the core.
A better pattern: read the access, review it in one place
The approach that works keeps the review where governance already lives and fills in the data it cannot reach.
- List the applications and pick the first ten. Start with the systems examiners ask about most: core banking, wires and payments, lending, and the systems that hold customer data.
- Create a read only service account in each. Nothing changes in the system. The account can see users and roles, and nothing else.
- Collect who has access on a schedule. StitchOps signs in with that account, anywhere a person can log in and act, and collects users, roles and permission codes. The run is deterministic and logged step by step.
- Translate codes into plain language. Role codes are mapped once, with your team, into entitlements a manager recognizes.
- Review in your governance tool. The access lands in your governance tool, such as Okta Identity Governance, so managers review core banking alongside every other application in one campaign.
- Carry out removals. When a reviewer revokes access, StitchOps removes it in the application and records the result, instead of opening a ticket. Banks that want to start smaller can keep removals manual at first.
- Hand the examiner one record. Every review, decision and removal is in one place, with dates and evidence.
What the bank's team actually does
The work on the bank's side is small, and that matters to teams that are already stretched.
- Provide the list of applications to cover.
- Create the read only service accounts.
- Sit with us once to map role codes to plain language.
We build and run the collection workflows. Your reviewers use the governance tool they already know.
Start with reviews, add the rest later
Banks often tell us that reviews matter more than provisioning speed, because reviews are what examiners ask about. So start there. Once reviews run cleanly, the same connections can drive onboarding and offboarding from your HR system, so access is right before the next review instead of corrected during it. See joiner, mover, leaver and how to connect any HR system to Okta.
About AI
Several banks have told us plainly that they do not want AI making access decisions. It does not. People make every review decision. StitchOps workflows run deterministically: the same inputs produce the same outputs, every step is logged, and AI is optional. Credentials stay in your vault or in the StitchOps per tenant vault, and the worker runs as an unattended session on a dedicated worker VM in your environment.
Next step
Send us the ten applications your examiners ask about most. We will tell you how each one can be read, what the read only account needs, and what your first review campaign would look like. Governance features are priced per app on pricing. See also StitchOps for financial services.
Frequently asked questions
- What is a user access review at a bank?
- A periodic check, usually quarterly, where managers and application owners confirm that every person's access in every system still matches their job, and access that should not exist is removed. Examiners ask for the evidence.
- Why are access reviews so hard for community banks?
- Core banking platforms and many vendor systems have no API or connector for identity tools, access is expressed in role codes only the system understands, and a small IT team has to export, translate, collect signatures and file the results for every application.
- Do we need to change our core banking system to automate reviews?
- No. StitchOps uses a read only service account in each application to collect who has access, the same way an administrator would view it, and changes nothing in the system.
- Can access reviews be automated without automating onboarding and offboarding?
- Yes. Many banks start with access reviews alone because that is what examiners ask about, and add joiner, mover and leaver automation later.
- Does this use AI to make access decisions?
- No. People make every review decision. StitchOps workflows execute deterministically, with the same inputs producing the same outputs, and every step is logged. AI is optional and only used where a bank chooses to.
- Where do the reviews happen?
- In your identity governance tool, such as Okta Identity Governance, alongside the applications it already covers. StitchOps feeds it the access data it cannot reach on its own.
Okta is a trademark of Okta, Inc. Other names may be trademarks of their respective owners. Examples are from conversations with banks and are described without identifying details.