Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The first thing GitGuardian ever shipped was a free warning. Now we’re making sure it gets heard.

Six AI agent security best practices for teams running coding agents and MCP servers: limit what a compromised agent can reach and catch credential misuse.

An AI agent runs with your credentials and acts before you can stop it. Nine incidents show what that costs. Six controls limit the damage: sandbox the agent, scope its credentials, lock its configuration, log every call, scan the workspace first, and deny by default.

AI coding assistants are unpredictable by design. Learn how AI hooks add deterministic controls and how GitGuardian ggshield blocks secrets before agents can use them.

The GhostAction supply chain campaign hit 772 public GitHub repositories between August 31 and September 30, 2026, targeting 2,577 secrets with the same injected workflow we documented last year.

A secrets vault controls the credentials you manage. Detection finds the ones that escaped. Here are six reasons mature secrets management programs need both.

Pasted a secret into a chat window and promised to clean it up later? Here's how SOPS works with age, AWS KMS, and HashiCorp Vault.

GitGuardian found a public GitHub repo tied to CISA leaking 844MB of live credentials. Agents Analysis flags which public leaks are actually yours.

AWS Dogwood brings stateful authorization to AI agents. Learn how it fits with workload identity, AuthZEN, IAM, and the move away from long-lived credentials.

This is the fifth post in our "Bring Your Own Source" series. The previous ones covered n8n workflow integration, Salesforce, GitLab CI, and GitHub Gists.