Scalable Infrastructure Access Management
summary
Claims bastion hosts cause single-point-of-failure and get replaced by access clusters running on Kubernetes or ECS; those clusters run ephemeral bastion containers that are protocol-aware and proxy Postgres and other services. Client-facing credentials become short-lived while server-facing credentials stay persistent, enabling just-in-time access, approval workflows and reduced blast radius. Approach is validated across 100+ organizations and focuses on engineering the proxy layer rather than manual SSH bastions.
AI-written summary · about
related talks
39mBastion DB: enabling secure developer access to databases
31mEffective building blocks for securing...
29mZero Trust Security and Identity Management with Boundary
22mBASTION: A Security Enforcement Network Stack for Container Networks
32mSplicing the Identity Based Access Gene into your Infrastructure DNA with HashiCorp Boundary
32mSimplifying remote access in dynamic environments with Boundary
15mBoundary: Then and Now [Abridged]
31munlighted, but what about Security and Multi tenancy?