SkillVaultskills Browse all 500 skills

Security · Version 1.6.0 · Reviewed 2026-08-02

Secrets Rotation Planner

Find and prioritize exploitable risk in credential rotation and certificate renewal with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Plans zero-downtime rotation for passwords, keys, certificates, signing secrets, and dependent workloads with dual-validity windows.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Credential rotation
  • Certificate renewal
  • Dual-key migration

How Secrets Rotation Planner works

You provide

Code, configuration, and the deployment trust model

It inspects

Reachable input-to-sink paths for credential rotation

It decides

A certificate renewal finding ranked by blast radius

You verify

Re-attempt the exploit path after remediation

What it checks first

Secrets Rotation Planner plans zero-downtime rotation for passwords, keys, certificates, signing secrets, and dependent workloads with dual-validity windows. Use it when the work involves Credential rotation, Certificate renewal, Dual-key migration.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Establish the current state and the constraint that actually limits credential rotation.
  2. Separate the requested solution from the underlying problem in certificate renewal, and name the assumptions carrying the most risk.
  3. Compare only viable options for dual-key migration against weighted constraints, cost of reversal, and operational ownership.
  4. Commit to a sequenced recommendation with success criteria, guardrails, and the observation that would reverse it.

Deliverables

  • Credential rotation assessment
  • Certificate renewal decision and action plan
  • Dual-key migration verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We need to rotate the database password used by thirty services without an outage or a coordinated restart.

Expected output

Create a second credential first, grant equivalent permissions, deploy consumers to accept the new secret, verify usage telemetry, then revoke the old credential after the longest rollback window...

Boundaries and compatibility

Ideal for

  • Credential rotation: produce a decision or artifact grounded in supplied evidence.
  • Certificate renewal: produce a decision or artifact grounded in supplied evidence.
  • Dual-key migration: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.