What the audit trail should cover
The audit trail covers entities changed by people: personal data, permissions, permits, settings and templates. Entities written by machines are excluded, because their history is source data, not documentation of an action. In the review, the scope of the trail grew from 60 to 107 entities, which shows that the initial set omitted many changes that matter as evidence.
For the plant's IT, a practical rule is this: if a specific person can influence a change and that change may be the subject of an explanation after an incident, it should be in the trail. If a record is created automatically from a device stream, the audit trail does not need it, because the record itself is the evidence.
Why one table can dominate the audit
One audit table for machine data grew to 6331 MB, which is 95% of the size of 59 audit tables together. It did not document any human action, so it was excluded from the audit. The remaining 58 tables took about 5% of the space and contained all the significant traces of human activity.
The conclusion for IT: check the size of audit tables every month and look for tables that grow out of proportion. Most often these are machine data that entered the trail through an overly broad rule.
Scope of the audit trail
Time zone: Europe/Warsaw
The time zone of audit stamps is Europe/Warsaw since October 2026. Before that, a fixed offset shifted winter entries by one hour, and old entries were not recalculated. This means that when analysing an event from before the change, you must allow for a possible one-hour difference.
When comparing system logs with the logs of other systems, for example access control or mail, establish which zone each of them writes in. A one-hour difference is most often a zone offset, not a real delay.
- Establish the write zone in every system taking part in the analysis.
- Treat entries from before October 2026 as written with a fixed offset.
- In analysis reports, state the zone next to every hour.
Maintenance practices for IT
Set a retention period for the trail that is consistent with the plant's policy and with the obligations arising from the security documentation. Treat backups of audit tables the same as production data.
Once a quarter, review the scope: new entities introduced by an update should be covered by the trail if a person changes them. A difference in the number of entities between reviews is a good signal to discuss with the vendor.
Size of audit tables
Checklist
Video
Frequently asked questions
Why are not all tables in the trail?
Because machine-written entities have a history that is source data, not documentation of a human action. Auditing them adds no evidence and greatly increases the size.
Were old entries corrected by one hour?
No. The Europe/Warsaw zone applies since October 2026, and earlier entries were not recalculated.
How often should the audit scope be reviewed?
Every quarter and after each update that adds entities changed by people.
Let's plan the audit trail for your plant
We will go through the scope of the trail, the retention period and the time zones with IT, which need to be described in the documentation.
Let's talk