By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Secrets hygiene for agent workflows

Agents read files and print output into transcripts, so a secret in a repository, shell history, or .env file can land in a model context or a log. Keep secrets in a manager, inject them at runtime by reference, and scan for leaks before and after commit. Agent transcripts and MCP config files are new places that need scanning.

Read in this order

  1. OfficialOWASP Secrets Management Cheat SheetStart here: the baseline practices for storing, rotating, and auditing secrets.
  2. OfficialGitHub: Push protectionHow push protection blocks a leaked token before it reaches the repository.
  3. Open sourceGitleaksA scanner you can run locally and in CI against repos and agent output.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.