AI Securityintermediate11 min · 9 steps
API Key Rotation
Replace credentials on a schedule with an overlap window so nothing breaks, then revoke the old key — and practise the emergency version before you need it.
leak useful for∞
errors during swap0
dataheavy workrequest
metrics are illustrativeProblemStep 1 of 9
Every long-lived key eventually leaks
Keys end up in repos, CI logs, laptops, screenshots and old containers. A stolen model provider key is especially attractive: attackers use it to run up your bill or resell access to your quota.
Compliance frameworks require rotation, and incident response needs a fast, practised way to replace a key. A key created on day one and never changed is useful to a thief for as long as it exists.
Watch outYou usually learn a key leaked from the invoice or a scanning alert — after it has been used.
What changed
- +Key copied from a CI log
- ~Provider bills you for the thief's traffic
Lesson 14 of 22 in AI Security