Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

This is the second video of our series 'How to Build a Discord Bot'. In this video, we will be learning about what Wordle is and how it works as well as building out the logic for the bot and testing it out. Stay tuned for the next video where we start using a database to store the Wordle results! Each video will be published one week from the previous.

Watch the full video for more...

Join Sasha Klizhentas, CTO of Teleport, as he discusses the critical challenges in authorization and access control, and introduces an innovative approach using policy as code. Learn how this new methodology can help prevent misconfigurations that lead to data breaches, and see a live demo of Teleport's new policy as code features with Dave Sudia. In this talk, you'll discover.

Join a dynamic workshop session from Teleport Connect where users and team members collaborate to shape the future of Teleport. This interactive session captures real user feedback about current frustrations and desired features for 2025 and beyond, using a structured brainstorming approach with color-coded post-its and group discussions. In this session, you'll see: Key themes that emerged: Chapters.

Watch the full video for more...

Join Jason Shire (COO of Infusion Points) and George Tal (Secure Systems Architect) as they share valuable insights on implementing security compliance with Teleport. Learn why traditional DIY approaches to compliance often fall short and how Teleport can streamline your compliance journey, from FedRAMP to SOC 2. This talk covers practical solutions for common compliance challenges, including access controls, audit logging, session management, and FIPS requirements. Perfect for security professionals, compliance officers, and engineering teams looking to simplify their compliance implementations.

Introducing The GitGuardian Secret Analyzer GitGuardian has always helped you find your leaked secrets, but now GitGuardian can also quickly reveal the permissions of your secrets. One of the first questions any security team needs to ask itself when a secret is leaked is "What exactly could an attacker do with it?" Does it grant read-only access or does it have permissions to write or delete data? At the same time, understanding the correct scope needed for replacing a credential can take a long time, as all too often, the permissions originally granted are poorly documented, if at all.