Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

A CI/CD pipeline deploying to production. A nightly database backup job. An AI agent performing maintenance tasks. New opportunities for engineering automation emerge every day. However, many of these workflows depend on stored secrets like hardcoded credentials, API keys, and long-lived tokens for privileged access.

We are reducing the number of supported major versions of Teleport from three to two. We are extending the support for each major version to 24 months. New major versions will come out once per year in August. The most recent major version of Teleport, referred to as the Current Version, is the only major version of Teleport that will receive new features. The previous major version, referred to as the Stable Version, will only receive bug fixes and security patches.

In Teleport 18, we’ve added official support to import Amazon EKS Audit Logs into Teleport Identity Security. This capability allows teams to have visibility into actions performed on Amazon EKS clusters when those actions were not executed via Teleport. Amazon EKS Audit Logs in Teleport Identity Security will be generally available in Teleport 18.3, coming November 2025. Your browser does not support the video tag.

Zero Standing Privileges (ZSP), where no user or system account has access unless there is a task being performed, is a milestone goal for most security teams. No always-on accounts, no secrets sitting around “just in case,” and nothing waiting to be misused. For a long time, privileged access management (PAM) has meant using credential vaults to store, rotate, and protect privileged credentials like administrative passwords, SSH keys, and API tokens.

I've spent the last few months talking to partners and prospects across EMEA about the upcoming Cyber Security and Resilience Bill, and there's a common theme: everyone knows it's coming, but most aren't sure where to start. The conversations usually begin with "Is this just another compliance checkbox?" and end with "How do we actually implement this without ripping out our entire infrastructure?" Here's what I've learnt from these discussions.

Since Teleport 1.0, we have shipped built-in session recording and replay. Nine years later, we are shipping the biggest upgrade yet: AI Session Summaries. Teams using Teleport onboard thousands of engineers (developers, DBAs, Windows users) who run thousands of interactive sessions every day. That easily adds up to 5,000+ hours of recordings per month, which is too much for humans to review proactively.