Why a register when the KD system has logs
The logs of the access control (KD) system show technical events, but they do not answer procedural questions: who accepted the report, when the decision was made and who approved it. The report register adds a layer of responsibility to the logs.
InnerWeb is a software producer and runs alongside the client's KD system: it receives punch events through a webhook and links them with qualifications, permits, attendance and time recording. A report register can therefore refer to records from both systems, but the procedural entry is kept by a person according to the plant's procedure.
Entry fields: the minimum that reconstructs the case
A good entry has several fields which together allow the course of the event to be reconstructed without asking people. Below is the minimum set.
The field for the time of the report and the field for the time of the block together give a measure of the risk window. This is the only number an auditor wants to see at once, because it shows how long the card remained active after the report.
- entry identifier and the date and time of the report,
- the person reporting (role, not sensitive personal data) and the person who accepted the report,
- the circumstances of the loss and the last known place of use,
- the time the block was ordered and the person who ordered it,
- incident classification: lost, stolen or cloned,
- the result of the review of swipes and a link to the ledger records,
- the replacement card or temporary badge issued, with the date,
- the date the case was closed and the person who approved the closing.
Completed register fields per year, calculation
Recording rules: what is allowed and what is not
The register should not contain values that by themselves give access. The badge token is printed only on the label and does not appear in any response of the security panel, so it should not end up in a register kept by hand either. For the same reason, do not record the card number if the entry identifier is enough.
Changes in the register should leave a trace. The audit trail in InnerWeb records who and when changed permits for work, the taxonomy of hazardous work, training records and automation rules. The same principle, who and when, should apply to every entry about a lost card, also when the register is kept outside InnerWeb.
Retention: how long to keep the entries
The retention period is set by the plant, taking into account its data protection policy and the auditor's requirements. For the security event register, station events such as completing or interrupting a group training are recorded in the event log with names from an allowed list, described in a catalogue for SIEM systems, which makes it easier to feed them into central monitoring.
A practical rule: the retention period of the register should not be shorter than the audit cycle, and entries about suspected theft or cloning should be kept longer than ordinary losses. Specific periods should be agreed with the legal department and the data protection officer.
An example of scale
According to the sample calculation, a plant with 500 employees and an annual loss rate of 3 percent handles 15 events a year, roughly one every 3 to 4 weeks. A register with eight fields therefore comes to about 120 completed fields a year. That is not much, but a single missing entry is noticed in an audit.
Checklist
Video
Frequently asked questions
Can the register be a spreadsheet?
It can, if changes leave a trace and access is limited to the roles named in the procedure. For larger plants a system with a change log is better.
Should we record the personal data of the person reporting?
A role and an internal identifier are enough. Minimising the data makes it easier to set the retention period.
Where do we find the scan records?
In the gate ledger and in the punch events sent from the KD system. The register contains only a link to them.
Compare your register with this model
We will review the fields of your register and show how to refer to the gate ledger.
Let's talk