Some accounts can change system configurations, create users, read sensitive data or disable controls. Privileged access management applies additional governance and technical safeguards to those capabilities because misuse or compromise can affect far more than one ordinary account.
Privilege is defined by capability and consequence
Administrators, database operators, security tools, cloud roles, service accounts and emergency credentials can all hold privileged access. The important question is not whether an account has an administrator label, but whether it can perform a sensitive action that ordinary users are not authorized to perform.
Banks inventory privileged accounts, map them to systems and owners and identify shared, embedded or unmanaged credentials. The inventory includes people and machines because an application identity with broad production permissions can create the same or greater exposure as a human administrator.
Ordinary work is separated from privileged work
An employee who needs administrative capability generally uses a separate privileged identity rather than browsing email and performing daily work through the same powerful account. Authentication, approved devices and network or session controls are strengthened according to the sensitivity of the action.
Roles and entitlements are limited to defined responsibilities under least privilege. Joining, changing roles and leaving trigger timely provisioning or removal, while periodic access reviews compare current permissions with actual duties instead of treating an old approval as permanent.
Access can be issued just in time and for a stated purpose
A privileged access service may vault and rotate credentials, broker a session without revealing a reusable password or grant a temporary role after the user authenticates and provides an approved request. Time limits and task-specific entitlements reduce the window in which a stolen or misused credential remains powerful.
Higher-risk actions can require separate approval, stronger authentication or two people to complete different parts of the process. These controls should be proportionate: an approval that is routinely bypassed or a role so narrow that staff share credentials can weaken the evidence and accountability the process was meant to create.
Monitoring connects a privileged session with accountable action
Logs record who obtained access, which system and role were used, when the session began and ended and what material actions occurred. Session recording or command monitoring may provide additional evidence for sensitive environments, subject to security, privacy and retention requirements.
Alerts focus on conditions such as unexpected elevation, access outside an approved window, disabled logging, unusual targets or activity inconsistent with the request. Reviewers reconcile tickets, approvals, access events and system changes so a technically successful login is not mistaken for an authorized change.
Emergency access and platform failure need their own controls
A break-glass process preserves access during an incident when the normal approval or identity service is unavailable. Emergency credentials are protected, narrowly scoped, monitored and reviewed promptly after use; an emergency route that is never tested may fail when it is needed, while one that is always open can become an uncontrolled bypass.
The privileged access platform can itself become a concentrated dependency. Banks protect its administrators, encryption keys, backups, integrations and recovery procedures, and they assess third-party and cloud arrangements. PAM reduces exposure but does not replace secure configuration, change management, segregation of duties or investigation of suspicious activity.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.