Course contentsShow
← Security
Lesson 1345 of 3,05227. Application Security - Secrets ManagementFree lesson

Automated vs Manual Rotation

Comparing manual rotation processes with automated approaches, and understanding when each is appropriate.

Automated vs Manual Rotation

What you'll learn: You'll understand the differences between manually rotating secrets and automating the process, and when each approach makes sense.

Core Concept

Secret rotation—changing credentials periodically—can be performed manually by a human or automatically by systems. Manual rotation means an engineer logs in, generates a new password or API key, updates all systems that use it, and verifies everything works. Automated rotation uses tools (like HashiCorp Vault or AWS Secrets Manager) to generate, deploy, and verify new secrets on a schedule without human intervention.

Manual Rotation

Manual rotation involves human operators following runbooks to update secrets. You might manually rotate:

  • Critical production database passwords quarterly, with a change control board reviewing each rotation
  • Root certificates that require careful coordination across many systems
  • Third-party API keys where the vendor requires manual regeneration through their portal

Pros: Full human oversight, suitable for infrequent changes, works when automation isn't possible.

Cons: Error-prone, slow, doesn't scale, creates "rotation debt" where teams avoid rotating due to complexity.

Automated Rotation

Automated rotation uses scripts or secret management platforms to rotate credentials on schedule (daily, hourly, or on-demand). Modern secret stores can generate new database credentials, update application configurations, and verify connectivity—all without human intervention.

Pros: Consistent, frequent rotation reduces blast radius of compromised secrets, eliminates human error, scales effortlessly.

Cons: Requires upfront engineering investment, needs careful testing, can cause outages if misconfigured.

When to Use Each

Start with automation for high-value, frequently-accessed secrets like database passwords and service accounts. Use manual rotation for rarely-changed, complex secrets like root CA keys or when third-party systems don't support automation.

Key Takeaway: Automated rotation is the security best practice for scalable, frequent secret changes, while manual rotation remains appropriate for infrequent, high-ceremony updates requiring human oversight—aim to automate wherever technically feasible.