Teleport

The iScutum team is back from Identity Summit London 2026 hosted by Teleport , and we want to start with a sincere thank you to the Teleport team for the genuinely warm welcome. From the first handshake at the registration desk to the open, no-fluff conversations with their experts, product leaders, and executives — every interaction felt personal rather than transactional. In Ukraine, PAM is no longer optional. NBU №43, the Law on Critical Infrastructure, CMU №518, and looming NIS2 alignment turn privileged access into a regulatory must-have for banks, energy, telecom, healthcare, and beyond. Through iScutum Estonia, we serve EU clients where NIS2, DORA, and GDPR are the daily reality. One of the most thought-provoking parts of the summit was Teleport's deep dive into Agentic AI Security. The core challenge is simple but profound: AI agents now need access to infrastructure — databases, APIs, production systems — to actually get work done, but classic identity models were never built for non-human actors operating at machine speed and scale. iScutum has led successful Teleport implementations in banking, fintech, energy, and critical infrastructure — environments where downtime is not an option and compliance is non-negotiable. Thanks again to the Teleport team Lance Kukulies Phil Simpson Alna Patel Jeff Bunten Chris Weber Sami A. for an event built on real cases, and for the hospitality that made the trip memorable. Bringing several ideas home for our clients in Ukraine and Europe. #Cybersecurity #IdentitySecurity #Teleport #ZeroTrust #PAM #NIS2 #iScutum #AgenticAI Yuliya Rogova

🚨🚨 Your infrastructure has 144 non-human identities for every human. 97% of them have excessive privileges ‼️ You can see 5.7% of them. And now AI agents are adding an entirely new category of identity - one that chains tool calls dynamically, accesses different resources per task, and creates new credentials as it operates. All at machine speed. Without a human in the loop. I call it the three-body problem of modern identity 🔺 Humans. Machines. AI agents. Three categories of entities requiring fundamentally different security architectures — operating simultaneously across the same infrastructure. In my latest Built to Secure article, I break down: 🔍 Why identity visibility is the real crisis — and what the U.S. Treasury and Midnight Blizzard breaches proved about invisible identities ⚠️ The behavior gap — why knowing who an identity is means nothing without knowing what it does 🔐 How Teleport is solving this at the architectural level — unified identity chain, AI session summaries, 50+ real-time detections, 1-click identity lock, and Beams trusted agent runtimes 🛠️ Three architectural shifts every organization needs to make this week This isn't about adding another tool to the stack. It's about replacing static credentials entirely with cryptographic, ephemeral identity — for humans, machines, and AI agents alike. 📖 Full article: https://fandf.co/3R0yPrZ What's your organization's biggest identity blind spot right now? 👇 #Cybersecurity #IdentitySecurity #AgenticAI #ZeroTrust #BuiltToSecure #Teleport

Back in 2010, we could get away with SSH keys and API tokens in .env files. We can't do that anymore. I went down a rabbit hole to understand how identity-based access is much better (and it's replacing) static credentials. Imagine having to secure this: • Multiple nodes • Across different data centers • Letting researchers and engineers access them • While having agents run automated jobs It's impossible to keep all of this secure by sharing static keys. Identity-based access is the solution for this. The way this works is pretty simple: Instead of asking "do you have the key to enter?", identity-based access asks "can you prove who you are?" Basically, you give every human and every service a verified identity that belongs to them, is short-lived, and scoped to the specific job they need. You use your identity as long as it is valid; when it expires, it's done. There are no keys to share or rotate, and you always know who (or what) did what. This is what Teleport is built for. They are an AI Infrastructure Identity platform designed for exactly this class of modern infrastructure. Here is a full explanation of how this works. It's a pretty interesting reading: https://lnkd.in/ehb9wD3Y Thanks to the Teleport team for partnering with me on this post.

Back in 2010, we could get away with SSH keys and API tokens in .env files. We can't do that anymore. I went down a rabbit hole to understand how identity-based access is much better (and it's replacing) static credentials. Imagine having to secure this: • Multiple nodes • Across different data centers • Letting researchers and engineers access them • While having agents run automated jobs It's impossible to keep all of this secure by sharing static keys. Identity-based access is the solution for this. The way this works is pretty simple: Instead of asking "do you have the key to enter?", identity-based access asks "can you prove who you are?" Basically, you give every human and every service a verified identity that belongs to them, is short-lived, and scoped to the specific job they need. You use your identity as long as it is valid; when it expires, it's done. There are no keys to share or rotate, and you always know who (or what) did what. This is what Teleport is built for. They are an AI Infrastructure Identity platform designed for exactly this class of modern infrastructure. Here is a full explanation of how this works. It's a pretty interesting reading: https://lnkd.in/ehb9wD3Y Thanks to the Teleport team for partnering with me on this post.

One my my favorite parts of Teleport is the people I get to collaborate and engage with. Our fabulous team, partners and customers. Thank you to all who made Teleport Identity Summit 🇬🇧 an epic event. On to the next!