Service Account and API Key Inventory
Find and govern non-human credentials.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan an inventory and governance process for service accounts and API keys. Where credentials may exist (code repositories, CI/CD, cloud consoles, vendor tools): [LOCATIONS]. Teams: [TEAMS]. Known problems: [PROBLEMS]. Define discovery steps for each location using defensive methods only, a record format (owner, purpose, scope, creation date, last used, rotation date, expiry), classification by risk, and rules (one owner, least privilege, expiry, no sharing across systems). Provide a prioritised clean-up plan for unused or over-privileged credentials with a safe way to disable before deletion. Include rotation procedures, alerts for unusual use, and a policy for credentials in code repositories with a scan and response process. Output a table template and a first-month plan. Add a short template for a monthly report showing the number of credentials, those without owners, those unused for 90 days, and those rotated on schedule. Describe how to handle credentials found in a public repository: revoke first, then investigate, then rotate, and record the timeline for review. Assume I have permission only for my own environment. Give detection and prevention advice, and leave out instructions for compromising anyone else.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.