Which statement best describes handling times for historical data during audit analysis?

• A. Always use local times for readability.
• B. Convert to UTC and annotate DST when analyzing historical data.
• C. Ignore DST and assume standard time.
• D. Convert to the most recent event time zone.

Answer: (B)

When auditing historical data, you need a single, unambiguous reference for every timestamp. Converting all timestamps to Coordinated Universal Time (UTC) and annotating whether daylight saving time was in effect for each moment provides that consistency. UTC remains constant regardless of local clock changes or DST rules, so events from different regions and time periods align correctly when you compare them. Annotating DST shows the exact offset that applied at the time, which is crucial for reconstructing the true sequence of events and for verifying the audit trail.

Using local times for readability can create confusion when data sources span multiple time zones, and DST can shift the local clock, causing events to appear out of order or at the wrong moment. Ignoring DST and assuming standard time would misplace events during DST periods. Relying on the most recent time zone’s rules is also risky because historical offsets and DST rules frequently differ from today’s, leading to inaccuracies.

Therefore, converting to UTC and noting DST status for each timestamp is the robust, reliable approach for historical audit analysis.