Protecting Keys: Find, Fix, and Prevent

A practical checklist for how MSPs handle API keys, secrets, tokens and certificates.

In a recent series of incidents, attackers used an open-source AI pentesting framework to search public code for exposed secrets. They then signed in as apps with valid credentials, which MFA doesn’t cover, and read secrets from Azure Key Vault. In one case, it took five minutes to go from GitHub to stolen data (Microsoft Threat Intelligence, November 5, 2026).Anyone who finds a key can use it. This two-page guide shows how to find the keys already exposed across your environment and your clients’ tenants, how to fix them, and how to keep new ones from leaking.

Exposed Keys: Find, Fix, and Prevent

What it covers

  • The 8 most common ways keys get exposed, with the fix for each. These include public repos, AI-built sites, .env files, RMM scripts, tickets and docs.
  • How to find exposed keys. Scan the full history of every repo for secrets, then review app registrations and sign-ins in Entra.
  • What to do when a key leaks. Revoke it first and investigate second. The guide also shows how to limit the damage from future leaks.
  • 5 next steps for your own environment and every client tenant.

‍

Stay on the Cutting Edge of Security

Subscribe to our newsletter to get our latest insights.