Managing Access in a Distributed Linux Infrastructure
summary
Explains privileged access management (PAM) for distributed Linux infrastructures: what a PAM system is, why it’s needed, and the requirements it must meet. Compares different approaches to access control and management in high-load, distributed Linux environments.
AI-written summary · about
chapters (20)
- 0:00Access management intro
- 2:37Teleport demo features
- 4:42Admin panel limits
- 9:59Custom admin panel
- 11:23Access analysis inventory
- 13:09Graphical access visualization
- 14:14Production reliability challenges
- 16:44Database fragmentation issues
- 18:10Proxy protocol stability
- 19:57Version compatibility issues
- 20:59MacBook Touch ID issues
- 21:41Critical bugs fixes
- 22:45Custom PAM module
- 25:53Privilege issuance rules
- 27:16User experience simplification
- 28:40Service accounts management
- 29:47Emergency access mechanism
- 31:53System architecture summary
- 32:39Operations team benefits
- 33:20Q&A
related talks
36mLinux-PAM demystified
14mThe Problem Isn’t Access, It’s Actions
12mIAM and Privileged Access Foundations for Secure ML Platforms
51mPermissions: Centralized or Decentralized? Both!
31mTaming Identity Sprawl to Close the Cybersecurity Exposure Gap
22mThe Sheer Terror of PAM
28mAn Approach to Protect the Entire Privileged Access Life Cycle
26mWho Authenticates Linux? Rethinking PAM & NSS in the Age of Cloud Identity