Following a $50 million funding round, GitGuardian CEO Eric Fourrier discusses why secrets security is becoming a much bigger problem in the age of AI-generated code and autonomous agents. As more organizations rush to deploy coding assistants and AI agents, Fourrier argues that the number of exposed credentials, API keys and tokens is rising just as quickly, creating new risks for DevSecOps teams already struggling to manage software supply chain security. Fourrier explains that AI agents need access to data and systems to be useful, but many organizations are still handling that access the old way by handing over secrets. That, he says, is accelerating an already serious problem. Secrets are ending up in code, collaboration tools, tickets, developer laptops and other places where they can be exposed, reused or stolen. While early concerns focused on whether large language models themselves might reveal secrets from training data, Fourrier says the bigger issue now is how humans...
It’s 2:47 a.m. Your phone buzzes. An alert fires again. You acknowledge it, diagnose the issue half asleep, patch it, write a quick note and crawl back to bed. Three hours later, you’re at your desk like nothing happened. If that sounds familiar, you’re not alone. On-call duty is one of the most important — and most mismanaged responsibilities in engineering. If done right, it protects your systems and distributes the load fairly. If done wrong, it destroys team morale and drives your best engineers to the door. According to the 2024 State of Engineering Management Report, 65% of engineers reported experiencing burnout in the past year. On-call stress is a major contributing factor, and it compounds quickly when rotations are poorly designed, alert noise is high and there’s no automation to catch the easy stuff. This guide covers the on-call best practices that high-performing SRE and platform engineering teams actually ...