NCUA Access Control Requirements: Rules vs. Guidance
NCUA Access Control Requirements: Rules vs. Guidance

TL;DR
- Federally insured credit unions must maintain a written security programme under 12 CFR § 748.0.
- Part 748, Appendix A provides risk-based safeguarding guidance, and the NCUA Examiner’s Guide describes access control practices examiners may assess.
- Part 748 does not set a universal quarterly user access review schedule. Set review frequency according to applicable obligations, risk, and internal policy.
- Reassess access after transfers, departures, and vendor engagement changes. Verify removals in the systems that granted the access.
- Keep evidence that links approvals, review decisions, and corrective actions to the permissions in effect during the period under review.
When a Completed Access Review Misses Borrower Records
A credit union completes its quarterly access review. Managers submit their decisions, and IT archives the certification report. During an examination, the credit union discovers that an employee who transferred out of lending can still open confidential borrower records.
The finding calls for an investigation into what access remained, why it remained, and how the credit union’s security programme addressed the risk. Whether it constitutes a regulatory violation depends on the applicable obligations and the facts. Understanding NCUA access control requirements starts with identifying which rules, guidance, and internal policies apply.
What Does NCUA Require for Access Control?
Under 12 CFR § 748.0, federally insured credit unions must develop a written security programme. Its objectives include protecting member records from anticipated threats and from unauthorised access or use that could cause substantial harm or serious inconvenience to a member. Access management is one part of that broader programme. ecfr.gov
Three Sources That Shape Credit Union Access Control Expectations
Section 748.0 and the Written Security Programme
Section 748.0 establishes the regulatory requirement for a written security programme and sets out its objectives. Credit unions use their risk assessment and applicable obligations to determine which controls are appropriate for their systems and operations. ecfr.gov
Part 748 Appendix A and Risk-Based Safeguards
Appendix A gives credit unions guidance on administrative, technical, and physical safeguards. It covers authentication, access restrictions, segregation of duties, independent testing, and service provider oversight. The choice of safeguards depends on the institution’s risks, size, complexity, and activities. ecfr.gov
In December 2025, NCUA proposed removing Appendix A from the Code of Federal Regulations and publishing the guidance separately. The current eCFR still includes Appendix A. govinfo.gov
The NCUA Examiner’s Guide and Supervisory Assessment
The Examiner’s Guide discusses individual credentials, job-related permissions, administrator controls, and independent review. Credit unions can use it to assess how their existing controls support accountability and protect member information. publishedguides.ncua.gov
| Control area | Regulatory or supervisory basis | Practical implication |
| Written security programme | Binding under § 748.0 | Maintain a written programme addressing the required security objectives |
| Protection of member records | Binding security programme objective | Address anticipated threats and unauthorised access risks |
| Authentication and access restrictions | Appendix A safeguarding guidance | Evaluate controls that restrict access to authorised identities |
| Job-related permissions | Examiner’s Guide and risk-based practice | Align permissions with current responsibilities |
| Access certification | Access governance practice | Reassess permissions according to risk and approved policy |
| Segregation of duties | Appendix A guidance and any applicable activity-specific requirements | Separate sensitive functions where required or appropriate |
| Independent testing | Appendix A safeguarding guidance | Assess whether key security controls work as intended |
Does NCUA Require Quarterly User Access Reviews?
The general Part 748 framework does not establish a universal quarterly review schedule for every credit union application. Set the frequency according to the institution’s risk assessment, applicable requirements, and approved policies. A credit union that adopts quarterly reviews should follow that schedule and document any exceptions. ecfr.gov
Standing administrator access to core banking may warrant closer oversight than routine access with a narrow scope. Departures, transfers, major system changes, and expired vendor engagements can also trigger reassessment between scheduled reviews.
How a Credit Union Can Investigate Retained Lending Access
A hypothetical credit union removes an employee’s loan origination role after a transfer to member services. The employee remains in a directory group that grants access to borrower documents in a shared repository.
- Confirm the exposure. Check what the group allows, whether the employee has a current business need, and whether other transferred employees retained similar permissions.
- Correct the access and the process. Remove unnecessary access through the approved change procedure. If the transfer checklist covered the lending application but omitted the repository, update the checklist and assign responsibility for verifying changes.
- Preserve the evidence. Keep the transfer date, original entitlement, review decision, change record, and evidence that removal took effect. Retest the revised procedure when suitable evidence is available.
What Access Control Evidence Should Credit Unions Maintain?
Keep evidence that shows who approved access, what permissions were in effect, and what happened when access no longer matched someone’s duties. A current account listing can show today’s access. Historical approvals, timestamps, and source-system records help establish what happened during the period under review.
| Control objective | Useful supporting evidence | What it helps demonstrate |
| Access authorisation | Requests and approval records | Permissions were appropriately approved |
| Identity accountability | User and account ownership records | Access belongs to known identities or accountable owners |
| Role appropriateness | Role definitions and entitlement records | Permissions match approved responsibilities |
| Privileged oversight | Administrator inventories and review decisions | Sensitive access received suitable scrutiny |
| Lifecycle management | Transfer and termination records | Employment changes triggered appropriate access updates |
| Review effectiveness | Certification outcomes and exceptions | Reviewers documented decisions and open issues |
| Remediation | Change records and updated entitlements | Required access removal took effect |
| Independent assessment | Test results and corrective action records | Controls were evaluated and weaknesses addressed |
Use this evidence framework to prepare for the institution’s examination scope and risk profile.
What Smaller Credit Unions Can Prioritise
Start with core banking administrators, lending approval authority, access to confidential member information, recent transfers and departures, and vendor or service accounts. Assign accountable owners and document how they approve, review, and remove access.
Where staffing makes full separation difficult, consider independent supervisory review or another compensating control where applicable requirements permit it. Any activity-specific legal restriction still applies.
Where Identity Governance and Automation Can Help
Automation becomes worth evaluating when reviewers receive unclear permission codes, employees retain access after transfers, revocations remain open, or historical decisions are difficult to reconstruct. User access review workflows can help coordinate certification, assign decisions, and track corrective actions across connected applications.
SecurEnds supports identity and entitlement visibility, access certifications, review workflows, and audit reporting. Verify connector coverage, permission detail, and how changes are implemented in each system. The identity governance solution for credit unions covers access oversight across banking, lending, and directory applications.
Best Practices for Credit Union Access Control
- Assign access according to current duties. Ask business and application owners to define which permissions each role needs.
- Keep user activity attributable. Use individual credentials and document ownership, restrictions, and monitoring for shared or technical accounts.
- Apply closer oversight to privileged access. Record its purpose and use independent authorisation or review where appropriate.
- Reassess access when responsibilities change. Include applications, directory groups, repositories, and vendor accounts affected by the change.
- Verify corrective actions in the affected system. Preserve evidence that approved removals or restrictions took effect.
- Prepare to explain open findings. Record the issue, potential impact, accountable owner, corrective action, and current status.
Frequently Asked Questions
What are the main NCUA access control requirements for federally insured credit unions?
Federally insured credit unions must maintain a written security programme under 12 CFR § 748.0 that addresses threats to member records and the risk of harmful unauthorised access or use. Appendix A provides risk-based guidance for selecting safeguards.
Is NCUA Part 748 Appendix A a binding regulation?
Appendix A contains safeguarding guidelines that support the written security programme requirement in § 748.0. NCUA’s December 2025 proposal describes Appendix A as guidance and proposes publishing it separately. The current eCFR still includes the appendix.
Does NCUA require credit unions to conduct user access reviews every quarter?
The general Part 748 framework does not prescribe quarterly certification for every application. Set the schedule according to risk, applicable obligations, and internal policy. Use event-driven reviews when a departure, transfer, or system change affects access.
Does NCUA require credit unions to purchase identity governance software?
No. Section 748.0 requires a written security programme and sets its objectives. Credit unions can use existing systems, documented manual processes, or specialised software to support their controls.
How should a credit union handle employee access after a departmental transfer?
Compare existing permissions with the employee’s new responsibilities. Include application-specific roles, directory groups, and shared repositories. Remove access that is no longer authorised and verify the change in each affected system.
What access control records are useful during an NCUA examination?
Useful records include policies, account inventories, approvals, privileged access listings, certification decisions, transfer and termination records, and verified remediation. Keep evidence relevant to the risk assessment, control testing, and period under review. The records needed depend on the examination scope and the institution’s controls.
Build Controls Around Risk and Accountability
Start with a sensitive permission and trace it from approval to the access it actually grants. Confirm who owns the decision, how the credit union reassesses the permission when duties change, and what evidence shows that corrective action took effect. That gives the institution a concrete way to demonstrate how its security programme protects member records.