Skip to content
Compliance · FFIEC IT Examination Handbook and 2021 Authentication Guidance

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.

FAQ

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.

Ask an Autharva SME

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.
Bigger than a question?Share a problem statement or use case with the team that plans our roadmap →
0/2000

We use these details only to reply. Privacy statement

Next step

What can your identities really reach?

Find out before an attacker or an examiner does.