Tech Talks Daily
00:27:16 · Jonathan Trayers, Neil C. Hughes
[00:27:16] S1: Thanks very much, Neil. [00:27:17] S0: So much gold in Jonathan's answers today, and one of the big things I'm taking away is to look closely at what an agent is allowed to do. A helpful instruction cannot compensate for access that reaches further than that work or request requires. So we're talking about separate identities, narrower permissions and a way to withdraw access and make that responsibility easier to manage. And I think Jonathan also made a case for beginning with one defined use case and building a repeatable pattern around it. Test in a control environment, keep a person involved while learning how the system behaves, and then monitor everything that happens after deployment. What I'm trying to say is the work continues when the demo ends. So a big thank you to him for joining me today. I will add his LinkedIn profile, the website, and a few other things over on the blog post associated with this at techtalksnetwork.com. But let me know your experience. Is it... And also have a think. If an AI agent surprised your team tomorrow, would you know which system it could reach and who could stop its access and its tracks right now? If you can't answer that right now, then maybe you need to be having a chat with someone in your tech teams. But let me know. Techtalksnetwork.com. I'll be back again tomorrow with another guest. Thanks for listening. Bye for now.