In organizations preparing for ISO/IEC 27001 certification or the automotive-specific TISAX assessment, the camera system is usually remembered in the last week. When the auditor asks “who monitors the server room entrance, who accesses the recordings, how many days are they kept?”, the answer is often not on the NVR screen but in a default setting nobody knows about. This guide explains what cameras can support in these frameworks, what they can’t cover on their own and what evidence can be prepared. It isn’t a guarantee of certification or audit results.
The two frameworks in brief
ISO/IEC 27001 is the international standard that defines requirements for an information security management system (ISMS); the controls in Annex A include topics such as physical security perimeter, physical entry, secure areas and physical security monitoring. TISAX is an assessment and exchange mechanism in the automotive industry based on the VDA ISA (Information Security Assessment) catalogue and run by the ENX Association; it includes sector-specific requirements such as prototype protection.
Control numbers and wording change with the version of the standard and the VDA ISA catalogue; mapping should be done with your ISMS team against the current version. In ISO/IEC 27001:2022, physical controls are grouped in theme 7 of Annex A, and physical security monitoring is a separate control. Going into an audit with a mapping table prepared for the old version is a common and easily avoidable mistake.
What do cameras support?
A camera isn’t a control in itself; it’s evidence for and a complement to a control. A door lock prevents entry; a camera verifies who entered and when. This distinction shapes almost all the questions asked in an audit.
| Control area | Contribution of video surveillance | Example evidence |
|---|---|---|
| Physical security perimeter | Monitoring the perimeter and entry points, intrusion detection | Coverage plan, analytics rules |
| Physical entry control | Verifying door and turnstile events with video | Access control–VMS integration, event samples |
| Secure areas / protected areas | Recording entries to the server room, archive and prototype area | Camera list by area |
| Delivery and loading areas | Monitoring these zones and separating them from interior areas | Coverage and recording samples |
| Visitor management | Visual record of visitor entries and exits | Reception and entrance cameras |
| Physical security monitoring | Continuous recording and event notification | Health monitoring, notification flow |
The “sample evidence” column in the table is the most neglected part. The coverage plan should be a document with each camera’s position and field of view marked on the floor plan; a camera list taken from the NVR doesn’t replace it. The plan should match the list of protected areas: if an entrance is on the list but no camera appears for it on the plan, the auditor will find it.
The recordings themselves must be protected too
Camera recordings can contain both personal data and (in prototype areas) confidential information. That’s why in audits the video system itself is also treated as an information asset:
- Access control: Personal user accounts, role-based permissions, export approval (access and audit trail)
- Logging: Logs of viewing, export and configuration changes
- Retention and destruction: A defined period, automatic deletion, controlled retention of incident recordings (retention and destruction)
- Network security: Segmentation, secure remote access, firmware management (camera VLAN)
- Physical protection: NVRs and recording servers located in a locked environment
- Maintenance: Evidence of recording continuity and fault management
Prototype areas carry an additional risk. The camera can record the very information you’re trying to protect: vehicle design, test rigs, a drawing on a screen. In that case the recording server also becomes a system carrying prototype information, and its access must be limited to people authorized for that area. Pointing the camera at the entrance instead of into the area is often the better choice. The same logic applies to keypad access panels: a camera that clearly sees the keypad records PIN codes.
Common audit findings
In the pre-audit checks we do on site, the same topics come up again and again:
- Shared admin account: The security team, IT and the service company log in with the same username. There are logs, but it’s unclear who did what.
- Exports without logs: Recordings are copied to USB sticks, and nowhere does it say who took them and why.
- Retention left to capacity: The policy states a specific number of days, while the NVR records until the disk is full. The real period is sometimes more, sometimes less.
- Drifting clocks: Camera, access control and NVR clocks differ. Door events and video don’t match.
- Permanently open remote access: The maintenance company’s connection has been open for years and nobody has closed it.
- Unlocked recorder: The NVR sits under the reception desk, where anyone can reach it.
None of these findings require new hardware. Most are a matter of configuration and procedure. They can be closed with an internal check a few weeks before the audit.
What don’t cameras cover?
- They don’t replace physical barriers (walls, doors, locks, barriers).
- They don’t replace the access control system and the visitor procedure.
- If nobody reviews the recordings and there’s no incident procedure, the control’s effectiveness is weak.
- ISMS processes (risk assessment, policy, internal audit, management review) are separate work.
The auditor’s question isn’t “is there a camera?” but “what happens if the camera captures an incident?”. If the incident review procedure isn’t written down, it remains unclear who will watch the recording, who they will notify and which recording will be preserved for how many days. A recording alone isn’t a control.
Steps to prepare for the audit
- Scope and areas: A list of facilities in the ISMS scope and security/protected areas.
- Gap analysis: For each area, current camera coverage, recording and access status.
- Improvement: Missing points, integration (access control integration), permission and retention arrangements.
- Procedures: Incident review, export, permission review, maintenance.
- Evidence file: Coverage plan, permission matrix, log samples, screenshots, maintenance reports.
When preparing the evidence file, make sure screenshots are dated and taken from the real system. In the permission matrix, username, role, accessible cameras and export permission should appear in separate columns. The date and outcome of the last permission review should also be in the file. Showing one export log entry and one configuration change log entry as log samples proves that logs are actually kept.
Balancing with KVKK
Expanding camera coverage for security controls shouldn’t conflict with the principle of proportionality. The distinction between entrances to prototype and secure areas and private areas should be clear, employees should be informed and recordings limited to the necessary period (KVKK and camera recordings).
In practice, this means a written answer for every new camera to “for which control, which area, for how long?”. The answer should be the same in both the KVKK and ISMS documentation. When two separate teams write two different retention periods, it comes back in the audit as a contradiction.
Frequently asked questions
If we install a camera system, will we pass TISAX?
No. Cameras are only one part of physical security controls. A TISAX assessment covers the information security management system as a whole and all physical measures for protected areas; the result is up to the accredited audit provider.
Should there be cameras in the prototype area?
It’s assessed according to prototype protection requirements and customer requirements. If cameras are used, access must be tightly managed, since the recordings themselves may contain confidential information.
What evidence does the auditor ask for?
Usually documents such as a coverage plan, an access permission matrix, sample access and export logs, retention and destruction rules, the incident procedure and maintenance records. The exact list varies with the audit scope.
To prepare the video surveillance side for the audit, see our TISAX and ISO 27001 video surveillance controls service; for ISMS and standards consulting, see Eretek Compliance’s TISAX and ISO 27001 services.