Three auditor questions and three groups of evidence
An auditor reviewing a closed card incident looks for three things: the event, the response and the timing. The event is the loss report or the suspicion of cloning, together with a record of when and by whom it was accepted. The response is the block of the card, the deactivation of the badge and the issue of a replacement. The timing is the interval between the report and each of these actions.
Each of these groups of evidence comes from a different place. The report and notifications are in the security system, the block of the card in the access control system, and changes of permissions in the audit trail. The security manager gathers them into one case file, instead of reconstructing them from memory when the auditor asks.
Evidence 1: record of the event and refusals
The first piece of evidence is the card punch log covering the period from the owner's last confirmed use, through the moment of loss, to the block. A gate scan is a control act: a green verdict records an entry or exit, while a red verdict records a refusal entry that does not count as presence on site. Refusals after the block prove that the block worked.
A refusal entry contains, in the verdict snapshot, the reason and the names of the missing trainings and qualifications, so the auditor sees not only that entry was refused but for what cause. InnerWeb receives card punch events from the client's access control system via webhook, so this log is available in one place together with presence.
Number of pieces of evidence by source
Evidence 2: trail of permission changes
The second piece of evidence answers the question of who changed the person's permissions after the incident. The audit trail records who changed work permits, the taxonomy of hazardous work, training records and automation rules, and when. If the case concerned a person authorised for hazardous work, the auditor will see whether anyone unauthorised touched their permits during the period of exposure.
Added to this is the history of badges. Deactivating a badge creates a new record instead of overwriting the old one, so the person's badge history stays in the system. The auditor sees that the badge was deactivated, when, and that the new one did not overlap the old one.
Will the auditor see badge tokens?
No. The token is printed only on the label and does not appear in any response of the security panel interface. The evidence is the fact of deactivation and its time, not the code itself.
Evidence 3: notifications and the register of reports
The third piece of evidence confirms that the right people were informed. A refusal sends a notification stating what is missing, so the system keeps a record of who received it and when. Events from registration stations go into the security event log under names from an approved list and described in a catalogue for SIEM systems, which makes it easier to feed them into the plant's central monitoring.
The case file also includes the entry from the loss report register: who reported it, when, who accepted it and when the case was closed. The detailed fields of such a register are set out on a separate page of good practices.
How to assemble the case file and how long it takes
The case file should be created on the day the case is closed, not on the day of the audit. For an event such as a lost card, a few minutes is enough if the log, the audit trail and the register are in one system. When the data has to be gathered from three places, the risk grows that data from the start of the period will be overwritten or archived.
The block of the physical card sits with the access control system, so the security manager obtains confirmation of the block from that system. InnerWeb is a software manufacturer and does not produce or replace readers, so the evidence of the card block comes from the client's system, and the evidence of access and presence from InnerWeb.
- An extract of the punch log covering the period from the owner's last use to the day of closing.
- A record of refusals after the block, with their reasons.
- An extract from the audit trail concerning the person during the period of the case.
- The person's badge history with the deactivation date.
- Confirmation of the block from the access control system, with the time.
- The register entry with the time of acceptance and closing.
Checklist
Video
Frequently asked questions
How long should the case file be kept?
The period is set by the plant in line with its retention policy and the guidance of the data protection officer. It is worth matching it to the audit cycle, not to a single case.
Should the case file contain personal data in full?
No, only to the extent necessary to show the event and the response. Fields the auditor does not need are worth masking.
Does the audit trail cover every change in the system?
It covers the designated areas: work permits, the taxonomy of hazardous work, training records and automation rules. The block of the physical card is confirmed by the access control system.
Prepare for an audit with the case file in one place
We will show how the punch log, the refusals and the audit trail come together as evidence after a card incident. Book a conversation with the InnerWeb team.
Let's talk