Privileged Access Management
Privileged access management (PAM) manages powerful accounts, credentials, and sessions. The video includes temporary administrator grants and session recording among its controls. CyberArk and Delinea are examples used to explain the category, not recommendations or evidence of comparative product performance. Source: IAM Ecosystem Explained (16:36-17:58).
Limit Powerful Access
Start with a business need and approval from the manager and application owner. Just-in-time access makes a grant temporary and lets it expire automatically. This avoids turning a short task into indefinite access; PAM applies these controls to powerful accounts and administrative work. Source: IAM Ecosystem Explained (16:36-17:58).
Session recording provides a record of privileged activity. It sits alongside credential management and temporary grants in the video’s explanation. It does not replace deciding whether the person should receive access in the first place. Source: IAM Ecosystem Explained (16:36-17:58).
Preserve Emergency Access
Break-glass access must remain usable when the identity provider fails. Protect these emergency accounts, restrict their use, monitor them, and test that they work. The aim is an emergency path that remains available without becoming an unobserved everyday route around normal controls. Source: IAM Ecosystem Explained (17:58-18:22).
Powerful permissions also need conflict checks. The example of creating a restaurant and approving its payments illustrates segregation of duties: forbid the conflicting combination or require extra approval. Temporary access and session recording do not, by themselves, resolve that conflict. Source: IAM Ecosystem Explained (16:36-17:58; 18:22-19:15).