← Problem Library
Security L7 SECURITY-1561 · 11 min

An Elastic transform is corrected and one rule still misses hits because the timezone script uses the retired alias for one index family

The rule is right, but one transform still rewrites timestamps using the old timezone alias for a subset of events.

SecurityIncident ResponsePlatform ReliabilityLevel 7Pro11 min
Scenario

Only one index family stops matching time-based detections after transform fixes.

What to check first
  • Identify the primary failure signal in the Incident Response 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 timezone alias mapping before changing the rule window.

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.