SOC Hunt time discrepancies: do not adjust an already correct indexed UTC instant
Reconcile the raw offset string, indexed instant and rendered instant separately.
Compare instants rather than strings
Reconcile the raw offset string, indexed instant and rendered instant separately. Do not move correct stored time again to compensate for a display problem. Truthound should compare instant differences after offsets, rather than wall-clock strings; agreement between source and index helps locate the display layer. [1, 2, 3]
An observed display and an unconfirmed cause
Beats #53788 contains a Security Onion 3.3.0 report where a +03:00 source timestamp and Elasticsearch indexed date agree, but the Hunt table displays an instant three hours later. Changing the display timezone to UTC did not resolve it. The responsible component, search filtering and sorting were not verified; ignoring the offset is a hypothesis. [1]
Three representations of one event
Normalize all three representations of the same event id into UTC instants and calculate the difference. Isolate timeline interpretation from the Hunt table for investigation. Retain display timezone and raw representations; displaying the same instant correctly in another timezone is not a failure. [1, 3]
The basis for 10800 seconds
Illustrative 2026-10-14T16:50:01.184+03:00 equals 13:50:01.184Z. A table showing the same instant gives difference 0 seconds. Rendering 16:50:01.184Z instead gives 3×3600=10800 seconds and fails. That discrepancy does not justify shifting the indexed value; it defines the display comparison. [1, 3]
Compare after decoding offsets
Truthound Core Python SDK 3.3.2 can compare prepared allowed_rendered_delta_seconds and rendered_delta_seconds using ColumnPairValidator with relationship="==". The operator calculates differences for matched events through an offset-aware parser, isolating unverified display observations. The SDK does not fix SOC UI or establish filtering and sorting impact. [1, 2, 3]
An interim response that preserves source data
Use verified indexed UTC for log correlation while the UI path is investigated. Do not strip offsets indiscriminately or subtract another three hours from correct source data. After a UI change, verify that both display timezones represent the same instant for the matched event. [1, 3]
Application conditions
Match the same event, preserve display timezone and derive instants using an offset-aware parser.
Alternatives
Use the verified indexed UTC as the comparison reference while investigating the UI path.
Limitations
The SDK does not fix the UI or establish filtering and sorting impact; different strings may represent the same instant.
Evidence
- Event checked
- Subject checked
- Modified
