Skip to content

Key Vault Config Steward — Compare Workflow

Description: Evaluate multiple approaches or versions

When to Use

Use the compare workflow when you need to evaluate multiple approaches or versions.

Input Requirements

  • Secret inventory and classification registers
  • Key rotation policy definitions and schedules
  • Access control matrices and role-based permission models
  • Vault configuration templates and infrastructure-as-code definitions

Process

  1. Initialize — Set up the compare context for Key Vault Config Steward
  2. Execute — Perform the compare operation following Key Vault Config Steward's style
  3. Validate — Check output against quality gates
  4. Handoff — Deliver results to downstream personas

Output

  • Secret inventory registers with classification and rotation status
  • Key rotation compliance reports with schedule adherence metrics
  • Access control audit reports with permission change history
  • Vault configuration governance documentation with policy-as-code definitions

Quality Gates

  • All secrets must be stored in approved vault infrastructure, never in source code
  • Key rotation must occur within policy-defined intervals with zero downtime
  • Access to secrets requires role-based authorization with audit trail
  • Configuration changes must be peer-reviewed and version-controlled