Reference

The IAM glossary, in plain English.

Every term framed for credit unions and community banks, and cross-linked to the page where it matters. Start with the pillar: What is IAM?

Access Certification / Recertification
Another term for the user access review decision, formally attesting that a person’s access is appropriate. A recertification is simply the next cycle’s certification. See What is a UAR?
Attestation Campaign
A scheduled, scoped round of access certifications sent to reviewers, for example, a quarterly campaign covering all branch staff. Provision routes each item and tracks completion.
Audit Trail
The complete, timestamped record of every access decision and action, who reviewed what, what they decided, who actioned it, and when it was verified. In Provision this is generated automatically and exportable on demand.
Birthright Access
The baseline access every employee receives automatically on hire (email, intranet, core read access for their role). Defining birthright access by role is a first step toward RBAC.
Core (Banking Core)
The central system that runs an institution’s accounts and transactions, such as FIS, Jack Henry, Fiserv, or Corelation. Access to the core is a primary focus of any access review. See connectors.
Deprovisioning
Removing a user’s access when they leave or change roles. Timely deprovisioning closes the lingering-account gap examiners look for; Automate automates it.
Entitlement
A specific permission within a system, for example, “can approve wires.” An entitlement review confirms the specific permissions a person holds are appropriate, not just that they should have the system at all.
Identity and Access Management IAM
The framework for managing digital identities and controlling access to systems and data. Read the full explainer →
Identity Governance and Administration IGA
The governance layer that makes access policy-driven, automated, and audit-ready. Read the full explainer →
Joiner-Mover-Leaver JML
The identity lifecycle as people join, change roles, and leave, and the access events each triggers. Provision automates JML so access follows policy at every step. See provisioning & automation.
Least Privilege
The principle that users should have only the minimum access required to do their job. RBAC is the most common way to enforce it.
Multifactor Authentication MFA
Confirming a user’s identity with more than one method, such as a password plus a one-time code or a fingerprint.
Privileged Access
Elevated access, admin rights, the ability to change other users’ access, or to move money, that carries outsized risk. Privileged accounts typically warrant more frequent review than standard ones.
Provisioning
Granting a user the access they need, ideally automatically and in line with policy. The counterpart to deprovisioning. See provisioning, RBAC & automation.
Role-Based Access Control RBAC
Granting access by role rather than per-person. Read the full explainer →
Segregation of Duties SoD
Ensuring no single person holds a combination of access that enables fraud or error, for example, the ability to both create and approve a payment. SoD conflicts are a common review and audit focus.
Self-Certified System
A system whose access data is brought into Provision by drag-and-drop upload rather than an automated connector, so it can be included in reviews even without an API.
User Access Review UAR
Periodic verification that each user has only the access their role requires. Read the full explainer →
Zero Trust
A security model that never assumes trust and verifies access continuously, rather than trusting anything inside the network perimeter by default.

From definitions to doing.

See these concepts at work, a review run end to end, with proof on every decision.