← Problem Library
Security L6 SECURITY-1465 · 12 min

An OPA bundle verifies and still serves stale policy because the verifier keeps a revoked JWKS key until max-age expires

Bundle freshness is fine, but the in-memory verifier still trusts a key that left the JWKS set.

SecurityPlatform ReliabilityLevel 6Pro12 min
Scenario

One sidecar still accepts bundles signed with a revoked key even after JWKS rotation.

What to check first
  • Identify the primary failure signal in the The Bundle Was Fresh and the Verifier Kept Trusting a Key That Had Already Left scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect JWKS refresh behavior and verifier cache lifetime before reissuing bundles.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.