What does it take to secure AI
agents without slowing developers down?A recent panel explored the
answer
I recently joined Zach Lloyd, founder and CEO of Warp;Gavriel Cohen, co-founder and CEO of NanoCo and creator of NanoClaw;and moderator Moriah Hara, founder of a community of more than 3,000 CISOs and a three-time Fortune 500 CISO, for a discussion on one of the biggest challenges facing enterprise security teams today:how to safely unlock the productivity of agentic AI.
In Part 1, we explored why traditional security models struggle with autonomous agents.As developers begin delegating more work to AI systems, a growing amount of activity happens outside familiar checkpoints such as repositories, CI/CD pipelines, and deployment environments.That naturally raises a new question:If governance needs to exist where agents actually execute work, what does that look like in practice?
Most organizations already have policies.
Don’t expose customer data. Don’tIn Part 1, we walked through six categories of AI
coding agent failures and why they keep happening.The agent runs as
you, with your filesystem permissions and your credentials, and
nothing sits between the model’s decision and the shell’s
execution.In Part 2, we looked at one specific version of
that failure in detail, the rm -rf ~/ incident that
wiped a developer’s entire Mac in a single command.Part 3 moves the
same problem up the stack, into a production AWS environment Continuous learning is a necessity for developers in today’s fast-paced development landscape.Docker recognizes the importance of keeping developers at the forefront of innovation, and to do so, we aim to empower the developer community with comprehensive learning resources.
Docker has taken a multifaceted approach to developer education by forging partnerships with renowned platforms like Udemy and LinkedIn Learning, investing in our own documentation and guides, and highlighting the incredible learning content created by the developer community, including Docker Captains.
Seite 1 von 23