FFIEC identity and access controls for banks and credit unions
The FFIEC Information Security booklet expects banks and credit unions to grant least-privilege access, change it when people move or leave, review it on a risk-based schedule, and tightly control privileged access; the 2021 authentication guidance adds identifying every user, including service accounts and third parties. Examiners ask for access reviews, privileged and service account inventories with owners, and termination evidence, which Autharva supports by mapping what each identity can reach.
Who it applies to: US banks, savings associations and credit unions examined by FFIEC member agencies such as the Federal Reserve, FDIC, OCC and NCUA, including systems that third parties provide on their behalf.
What the rule asks for
- IS Booklet II.C.7(b)User access program. Management should run a user access program built on least privilege, with business and application owners defining user profiles.
- IS Booklet II.C.15Logical access administration. Assign only the access users and devices need, update access rights after personnel or system changes, and review users' access rights at a frequency based on risk.
- IS Booklet II.C.15Job changes and departures. Promptly review and modify access for users who transfer, resign or are terminated, especially those with privileged, remote or customer-information access.
- IS Booklet II.C.15Privileged access. Tightly control privileged access: document grants, use a separate ID from normal business use, prohibit shared privileged accounts, log and independently monitor use, and have an independent party review privileged rights at appropriate intervals.
- 2021 Authentication Guidance, Section 3Identify all users and high-risk users. Identify all users of institution systems, including employees, service accounts and third-party users, and flag high-risk users such as privileged users, remote users and senior management for enhanced controls.
- 2021 Authentication Guidance, Section 5MFA for high-risk users. Single-factor authentication with layered security has shown to be inadequate for high-risk users, and MFA or controls of equivalent strength can more effectively mitigate the risk.
- 2021 Authentication Guidance, AppendixService accounts and privileged user controls. Examples of effective controls include inventorying service accounts with assigned responsibility, alerting when privileged accounts are added or removed, and independent periodic review of privileged user activity.
Dates that matter
- FFIEC issues the revised Information Security booklet of the IT Examination Handbook.
- FFIEC issues Authentication and Access to Financial Institution Services and Systems, replacing the 2005 and 2011 internet banking authentication guidance.
Where access evidence usually falls short
- Access reviews follow a calendar rather than a documented risk-based schedule, and cover only the core and a few major applications.
- Service accounts are not inventoried, or have no employee or department assigned responsibility for them.
- Job changes add new access without removing the old, so privileged and remote access accumulates.
- Third-party and vendor users are outside the review population, even when they reach institution systems.
- Privileged access reviews are performed by the same team that holds the access.
How Autharva helps
- Shows what every employee, contractor, service account, OAuth grant and AI agent can actually reach, not only what appears on its access list.
- Assigns a named owner and a scope to every service account, vendor login and OAuth grant.
- Closes access no one should still have, only with the owner's approval, and hands exceptions back to your existing certification campaigns.
- Runs as a container in your data center or VPC, starts read-only, and keeps customer data inside your network.
- Deploys the same day, with first findings in week one from exports and reports.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- Risk-based access review schedule and completed review records
- Inventory of privileged users with grant documentation and independent review
- Service account inventory showing the employee or department responsible for each
- Records of access changes after transfers, resignations and terminations
- Risk assessment identifying high-risk users and the authentication controls applied to them
Questions.
Is the FFIEC handbook a regulation?+
No. The handbook guides examiners, and the 2021 guidance states that it does not impose new regulatory requirements. The binding standards are the Interagency Guidelines Establishing Information Security Standards, such as 12 CFR 30 Appendix B for national banks and 12 CFR 748 Appendix A for credit unions.
How often does the FFIEC expect access rights to be reviewed?+
The Information Security booklet does not set a fixed frequency. It says management should review access rights on a schedule commensurate with risk, and promptly after job changes.
Do service accounts count as users?+
Yes. The 2021 guidance defines users to include employees, board members, third parties, service accounts, applications and devices that access institution systems.
Does Autharva replace our IGA or core provider controls?+
No. Your IGA keeps doing its job. Autharva covers the systems it does not reach and hands exceptions back to your review campaigns.
Sources
- FFIEC IT Examination Handbook, Information Security booklet, 2016-09
- FFIEC IT Examination Handbook InfoBase, II.C.15 Logical Security, 2016-09
- FFIEC, Authentication and Access to Financial Institution Services and Systems (FDIC FIL-55-2021 attachment), 2021-08-11
- FDIC, FIL-55-2021, 2021-08-11
- Federal Reserve, SR 21-14, 2021-08-11
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.