Current approaches to managing machine identity for infrastructure like Kubernetes Clusters and CI/CD workflows rely on outdated security mechanisms like passwords, shared secrets, and other manual processes that are error prone and increase the risk of breach.

This session on March 15th will focus on the existing vulnerabilities and downsides of using shared long-lived secrets to access key pieces of infrastructure programmatically using GitHub Actions and how you can eliminate those secrets using Teleport Machine ID. As GitHub Actions has matured as a product and more and more companies rely on it for their CI/CD workflows, an exposed secret in the repository can be the difference between a team being able to efficiently test/deploy code, and an infrastructure breach of nightmarish proportions.

In this episode, we will demonstrate:

• Production-like Teleport Github Actions integration highlighting Teleport’s rich audit logging, Kubernetes management, and secure access capabilities.
• Workflows that apply Kubernetes manifest updates directly to the cluster upon commit to your repo.
• Security best practices assigning individual identities to humans and worker nodes without the use of any static credentials.

Leave shared secrets and passwords behind with Teleport Machine ID, allowing your devops engineering team to sleep easier at night by replacing GitHub secret management and reducing your organization's attack surface.