Stage 1: what the declaration covers
ISO/IEC 27001:2022 has 93 controls in Annex A in four groups: 37 organizational, 8 people, 14 physical and 34 technological. The statement of applicability indicates which controls the organization applies and why. In the physical group the auditor pays attention to security perimeters, physical entry, securing offices and rooms, and working in secure areas.
The auditor's first step is to match the declaration with reality: which rooms are secure zones and whether the list in the declaration agrees with the list in the operational documentation. A discrepancy at this stage is a finding, before the auditor opens any log.
Stage 2: the policy and its counterpart in the system
The second step is to check whether the access policy has a counterpart in the configuration. Permissions in InnerWeb follow from roles with inheritance and a scope matrix, and roles are granted along a seniority ladder: nobody can grant a role higher than their own. The auditor compares the wording of the policy with the list of roles in the system and looks for roles that the policy does not foresee.
The control question: can someone grant themselves broader rights than the policy allows? If the answer is no, because the system does not allow it, the evidence is the configuration, not a statement.
Groups of controls in Annex A of ISO/IEC 27001:2022
Stage 3: the permissions of specific people
The third step is a test on people. The auditor selects several people with a permission to a room and checks whether they have valid trainings, qualifications and an active account. A scan of a QR badge or an RFID card at the security screen gives a verdict based on these elements, so the same mechanism that decides on entry also gives the auditor the answer.
For external companies the auditor looks for a permit or a planned visit with a supervisor. At the gate, a planned visit replaces the one-day permit requirement, but trainings, qualifications and an active account still decide on entry. The electronic work permit contains the task, the place and the time window, so the auditor can check whether the entry fell within the window.
Stage 4: the entry and exit log
The fourth step is a test on events. The auditor draws dates and asks for the entry log of a given room. Every scan at the security screen is an audit act and is written to the entry and exit log. If the door is served by the client's access control system, card read events reach InnerWeb through a webhook and are linked with qualifications, permits, attendance and working time records.
InnerWeb does not manufacture or replace access control readers. It is an independent system complementing the client's existing systems. For the auditor this means one summary instead of several exports from different tools.
Stage 5: the change trail and its limits
The fifth step concerns changes. Changes of permits, the taxonomy of dangerous work, training results, automation rules and inspection routes are saved together with the author and the time, and the list of audited objects is visible. The audit trail answers the question who changed the data. The auditor picks a change of a permission and asks for its author.
The limits of the trail must be known. Entities written only by the system, such as device heartbeat signals and notification logs, are deliberately excluded from it, because their history is itself source data. The log stores local time of the Europe/Warsaw zone from October 2026, and entries from the winter seasons 2023/24 to 2025/26 are shifted by one hour. The internal auditor should know this, so as not to treat the shift as manipulation.
Stage 6: review and the limits of the standard
The last step is the review: whether someone regularly looks at the log and the change trail. Periodic reports send an e-mail daily, weekly or monthly with tables and a PDF attachment carrying the client's logo, and optionally an XLSX file, with a separate scope of locations and recipients for each rule. A sent report is proof that the review took place.
The internal auditor should also remember the limit: an ISO/IEC 27001 certificate does not prove compliance with the Polish cybersecurity act or with NIS2. The standard is used as an evidence framework for the audit, not as a substitute for the requirements. NIS2 Article 21 paragraph 1 requires measures protecting the physical environment of systems, so the same evidence from entries serves both purposes, but the compliance assessment for each of them is made separately.
Checklist
Video
Frequently asked questions
Is the statement of applicability enough as evidence?
No. The declaration indicates intent and scope. The evidence is the configuration, the event log and the change trail, which the auditor can check on a sample.
Can the internal auditor use the same evidence as the certifying body?
Yes, and that is the goal. A well-prepared package lets you repeat the external auditor's sample at an earlier stage.
Is physical security monitoring only about cameras?
No. It covers any means of observing and recording physical events, including the entry log and alarms. The choice depends on the risk analysis.
Sources
Pass the auditor's test in advance
We will show how the entry log, the change trail and periodic reports form evidence for physical controls. Arrange a conversation with the InnerWeb team.
Let's talk