How many physical controls ISO/IEC 27001:2022 has and what they cover at entry points
Annex A of ISO/IEC 27001:2022 contains 93 controls in four groups: 37 organizational, 8 people, 14 physical and 34 technological. For the information security officer the physical group matters most, because this is where the auditor looks for evidence at the doors, not in the documents.
This group includes, among others, security perimeters, physical entry, securing offices and rooms, and working in secure areas. The control added in the 2022 edition, physical security monitoring, means in practice that a statement such as “we have locks” is no longer enough: the auditor expects proof that entries are observed and recorded.
- 93 controls in Annex A, including 14 physical ones
- Entry to a room is a separate control that requires operational evidence, not only a policy
- Physical security monitoring is a control added in the 2022 edition
Questions about zones and physical entry
The most common auditor question is which rooms you treat as secure and how you know who may enter them. The answer has two parts: a list of zones with an owner for each, and a list of people or roles authorized to enter. A list of zones without the authorizations is a declaration, and a list of authorizations without the zones does not show what it applies to.
In access control systems the evidence is a summary: room, role, validity period of the permission. If the site has one access control system and separate work permits, the auditor will ask whether the two sources agree. That is why it helps to show that a card read from the access control system is linked with qualifications, permits and attendance, and does not exist as a separate list next to them.
Does the auditor expect one system for all doors?
No. The standard requires controls that match the risk, not one product. A site may have an access control system at the gate, locks in the server room and a separate permit process for external companies. What matters is that for every zone it is known who decides on entry and where the trace is left.
Is a list of authorized people without dates enough?
Usually not. The auditor checks whether a permission has a validity period and whether entry stops working when it expires. The weakest evidence is a list that keeps growing but is never cleaned up.
Annex A controls of ISO/IEC 27001:2022 by group
Questions about the entry log and monitoring
The second group of questions concerns what actually happened. The auditor picks several days at random and asks for the entry log of a given room: who, when, for what purpose, who left. If the log is kept in a paper book, the officer assembles it by hand from several notebooks and photos, which takes hours and is often incomplete.
In InnerWeb every scan at the security screen is an audit act and is written to the entry and exit log. A scan of a QR badge or an RFID card gives a verdict based on valid trainings, qualifications, a permit in progress and an active account. Security sees the verdict and the list of missing elements, without having to interpret the full permit view. For the auditor this means the same record is both evidence of the control and evidence of the decision.
If the server room door is served by the access control system of an external vendor, InnerWeb does not replace its readers or swap them for its own. It receives card read events through a webhook and links them with qualifications, permits, attendance and working time records, so the officer has one summary instead of several exports.
Questions about permission changes and the audit trail
The third group of questions concerns accountability: who granted a permission and when. Changes to 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 trail answers the question who changed the data, so it can be shown as proof that the permission list does not change without an owner.
It is worth knowing the limits of the trail. Entities written only by the system, such as device heartbeat signals or 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; entries from the winter seasons 2023/24 to 2025/26 are shifted by one hour. This should be explained to the auditor in advance, before they find it themselves when comparing times.
- Each change saved with the author and the time
- System entities excluded from the trail, because their history is source data
- Entries from the winter seasons 2023/24 to 2025/26 shifted by one hour
Questions about roles, authentication and the limits of the standard
The auditor also checks who may grant permissions. In InnerWeb, permissions 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. This answers the typical risk that a local administrator gives themselves broader rights. Multi-factor authentication, a code sent by e-mail or TOTP, is enabled per installation, with a trusted device period.
The last point concerns the limits of the standard. An ISO/IEC 27001 certificate does not prove compliance with the Polish act on the national cybersecurity system or with the NIS2 directive. 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 network and information systems and their physical environment, and paragraph 2 lists access control policies among the measures. The same set of evidence from the entry log and the change trail serves both audits, but neither of them releases you from the other.
How to prepare the evidence package for the audit day
The package for the auditor should fit in one folder and answer four questions: what is a zone, who has the right to enter, who entered, who changed the permissions. For each of them prepare one export and one sentence of commentary. Periodic reports with tables and a PDF attachment carrying the organization logo, sent daily, weekly or monthly, let you have a ready summary without assembling it at the last moment.
The InnerWeb installation can run in the client's server room as an independent system that complements existing systems: access control, working time recording, HR and ERP. For the officer this matters, because the entry data stays within the organization and the evidence does not depend on an external service.
Checklist
Video
Frequently asked questions
Is the entry log in the system enough for the auditor instead of a paper book?
Yes, if the log is complete for the zones in scope, has an author and a save time for each entry, and can be exported for the selected days. A paper book may remain as a fallback solution, but its entries should be added to the system.
Does InnerWeb replace the access control system?
No. InnerWeb does not manufacture or replace readers. It receives card read events from the client's system through a webhook and links them with qualifications, permits, attendance and working time records.
Does the system help meet NIS2 and ISO/IEC 27001 requirements at the same time?
It provides evidence that can serve both audits: the entry log, the change trail and periodic summaries. It does not replace the auditor's assessment and does not guarantee compliance.
Must entry data leave the site?
No. The installation can run in the client's server room as an independent system complementing existing solutions, so entry data stays within the organization.
Sources
Let us prepare the evidence package for your audit
We will show how the entry log, the change trail and periodic summaries form a package for an ISO/IEC 27001 auditor. Arrange a conversation with the InnerWeb team.
Let's talk