← Problem Library
Security L7 SECURITY-1490 · 12 min

An Envoy mTLS path validates new CRLs and one cluster still accepts revoked certs because the SDS cache refreshes after the verification worker snapshot

The revocation list is current, but worker snapshots keep using the previous SDS view until the next hot restart boundary.

SecurityTLSPlatform ReliabilityLevel 7Pro12 min
Scenario

Revoked certificates continue to pass on one cluster after CRL rotation while others reject them correctly.

What to check first
  • Identify the primary failure signal in the TLS 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 SDS refresh timing and worker snapshot boundaries before rotating the CA.

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.