Modern engineering teams ship constantly. The cloud changes daily. Pipelines run all day. On-call needs access right now. And now agentic apps are starting to act on their own.
Most privileged access controls weren’t built for that pace.
So teams do what they have to do: grant broad permissions, reuse credentials, leave access in place “just in case.” Those shortcuts don’t fail loudly. They quietly turn into unmanaged paths into production.
In this session, Neha Duggal (CPO) and Kelsey Brazill (Head of Product Marketing) will walk through five production resources where standing privilege creates outsized risk:
- Cloud infrastructure
- Servers and compute
- Databases with sensitive data
- Code repos and deployment workflows
- Agentic and automated applications
What you’ll learn:
- The most common “standing privilege signals” in each of the five areas
- Why legacy models break down (even when the team has good intentions)
- Practical ways teams are moving to just-enough, just-in-time access without slowing developers down
- How to reduce blast radius and make ownership and accountability less painful
If you’ve ever been afraid to remove access because it might break something, you’ll recognize the patterns.
