The most sensitive asset in a camera system isn’t the cameras but the recordings. What time an employee entered where, whom a visitor met, all the details of an incident are there. Even so, a common setup is: two levels of permission (“user” and “administrator”), an “operator1” account shared by three people and a VMS log nobody reads. In this picture, asking who took a recording out goes unanswered. Below we explain, in order of implementation, a role-based permission matrix, camera group restrictions, the audit trail and periodic permission reviews for VMS and NVR environments.
Put permissions in order of risk
The “user / administrator” split doesn’t see the difference in risk between watching a recording and exporting it. One looks at it on a screen; the other takes the data outside the system. Before starting permission design, rank the permissions your VMS offers by risk, as below:
| Permission | Risk | Reason |
|---|---|---|
| Live viewing | Intermediate | Momentary observation; doesn’t leave the system |
| PTZ control | Intermediate | Affects coverage and recording by changing camera direction |
| Playback from recording | High | Retrospective tracking becomes possible |
| Export | Very high | Data leaves the system’s control |
| Locking and deleting recordings | Very high | Affects the retention period and evidential integrity |
| Lifting masks | Very high | Opens an area hidden for privacy |
| Configuration and user management | Critical | Can change all other controls |
Locking recordings (protecting an incident recording from loop deletion) should be a separate permission. When an operator sees an incident, they should be able to protect the recording; but the same person doesn’t need to be able to export it. If your product can’t grant these permissions separately, record the situation as a risk and plan a compensating control; for example, making export possible only from a specific workstation. Don’t be misled by PTZ being “medium” risk either. A PTZ that has been turned away doesn’t tell anyone about the area it isn’t recording.
Role-based permission matrix
Permissions are given to roles, not people; people are assigned to roles. The matrix below is a starting suggestion for a medium-sized production facility; it’s adapted to the organization’s structure.
| Role | Live / PTZ | Recording playback | Export | Configuration |
|---|---|---|---|---|
| Security operator | Yes / Yes | Last 24 hours | No | No |
| Shift supervisor | Yes / Yes | Throughout the retention period | No | No |
| Incident investigation lead | Yes / No | Yes | Yes, with a logged request | No |
| VMS administrator (IT) | For troubleshooting | On request and approval, time-limited | No | Yes |
| KVKK / compliance officer | No | No | No | Reading the audit trail |
| Maintenance company | During the maintenance window | No | No | Limited, time-limited |
Two principles stand behind the matrix. The first is segregation of duties: the person managing users and permissions shouldn’t be the person exporting recordings. Otherwise, someone grants themselves permission, takes the recording out and cleans up the trail. The second is least privilege: limiting the operator’s playback window to the last 24 hours reduces the risk of retrospective tracking while still allowing incidents within a shift to be reviewed. If your VMS can’t limit playback by time window, this restriction is applied administratively with an escalation procedure to the shift supervisor.
For authentication, integrate the VMS with Active Directory or LDAP. A leaver’s account is closed centrally; no forgotten local account remains in the VMS. Local VMS accounts are kept only as emergency accounts, with passwords stored in a vault, and their use raises an alarm. Shared accounts (“operator1,” “security”) make the audit trail meaningless. Remove them. The need for fast login at shift changes is met with personal accounts and a short session timeout. For remote users and administrators, apply multi-factor authentication directly if the VMS supports it, and otherwise at the VPN or access gateway layer.
Restrictions by location and camera group
A role answers the question “what can you do”; a camera group answers “on which cameras.” In multi-site structures, the security supervisor of one facility shouldn’t see the recordings of other facilities. Within the same facility, cameras are also grouped by sensitivity:
- General areas: Perimeter, car park, entrances and corridors
- Operational areas: Production lines, warehouse, shipping
- Sensitive areas: Cash office, server room, R&D, sample areas
- Management areas: Executive floor entrances, meeting area corridors
A permission is defined as the intersection of role × camera group: readable rules emerge such as “the warehouse shift supervisor can play back recordings on warehouse cameras.” If camera groups are set up together with a naming standard (location code, area code, sequence number; for example IST-WHS-014), a newly added camera goes into the right group. A failure common on site starts here: the integrator adds a new camera named “Camera 37,” and it goes into no group or drops by default into the group everyone can see. Put a “group assignment” line on the camera addition work order.
Events to record in the audit trail
The audit trail is the proof that the permission model really works on site. Enterprise VMSs generally record user actions; but which events are recorded and in how much detail varies by product and setting. Don’t trust the default log setting. At a minimum, these events should be recorded:
- Login, failed login and logout (user, source IP, client type)
- Start of playback: which camera, which time range
- Export: camera, time range, format, destination, request number if any
- Locking, unlocking and deleting recordings
- Lifting masks and taking over PTZ control
- Changes to users, roles, camera groups and retention settings
- A camera dropping out of recording and recording stopping
For the record to be meaningful later, each event needs to carry common fields. If you forward the VMS log to a SIEM or central log server, you can design the normalized record with a schema like this:
{
"time": "2026-11-03T14:22:07+03:00",
"user": "ayilmaz",
"role": "incident-review",
"source_ip": "10.20.5.31",
"action": "export",
"camera": "IST-WHS-014",
"range": "2026-11-02T21:10/2026-11-02T21:40",
"request_no": "INC-2026-118",
"result": "success"
}
If the timestamp isn’t reliable, neither is the log. VMS servers, cameras and the log server should be connected to the same NTP source. Check the time source and drift with w32tm /query /status on a Windows-based VMS server and chronyc tracking on a Linux-based server. On cameras, the NTP server is often left at factory settings, or there’s no access to NTP from the camera VLAN; the camera clock drifts by minutes within days. In an incident review, the recording is searched for in the wrong range and isn’t found.
Protecting and reviewing logs
An audit trail that exists only in the VMS database is a record the VMS administrator can delete. For integrity:
- Forward logs in real time to a log server or SIEM outside the VMS; the VMS administrator should have no delete permission on that system.
- Keep logs longer than video; the access history should remain queryable after the recording is deleted.
- Match export events to an open incident or request record. An export without a request number is a trigger for review.
- Define alarm rules for after-hours playback, many cameras being played back in a short time and repeated failed logins.
If the log is opened only when an alarm arrives, patterns aren’t visible. Prepare a short monthly report: number of exports and their reasons, administrator access, emergency account use. The compliance officer reviews and signs the report. A log nobody reads is as useless as a log nobody keeps. How an exported recording is handled afterwards is explained in the camera recording incident investigation and chain of custody guide.
Periodic permission review
Permissions accumulate over time. A person who changes role keeps their old role, temporarily granted access becomes permanent, the maintenance company’s account stays open after the contract ends. The review runs in these steps:
- Export the current list of users, roles and camera groups from the VMS. If there’s AD integration, also take group memberships; for example
Get-ADGroupMember -Identity "VMS-Recording-Playback" -Recursive | Select-Object Name, SamAccountName. - Send the list to each role’s business owner (security manager, facility manager); ask for a “keep,” “change” or “remove” decision for each person.
- Flag accounts that haven’t logged in at all since the last review.
- Implement the decisions and verify they were implemented with a second export.
- Keep the review record with the date, participants and decisions.
The fourth step is the one most often skipped. The decision is made, sent by email, and nobody checks whether it was implemented. This record is direct evidence for the access rights (5.18), privileged access rights (8.2) and logging (8.15) controls in ISO/IEC 27001:2022 Annex A; the standard itself is available from ISO’s standard page. How to document the review so it’s accepted in an audit is covered in detail in the access review evidence guide. For other control areas specific to cameras, see the TISAX and ISO 27001 camera controls article, and for managing outside companies’ access, the third-party camera access article.
We review and redesign the role and log structure of your existing VMS against this model under our camera recording access rights and audit trail service; in organizations with a certification goal, this work should be planned together with TISAX and ISO 27001 video surveillance controls.
Frequently asked questions
Should the VMS administrator be able to watch recordings?
Technically, in most VMSs the administrator can do everything; however, under segregation of duties, system administration and recording playback should be assigned to separate roles. If the administrator needs to open recordings for troubleshooting, this access is granted on request and approval, for a limited time, and appears in the audit trail.
How long should the camera audit trail be kept?
The law doesn’t set a single period for the camera audit trail. The practical rule is to keep logs longer than the related video recordings; that way, who accessed a recording can still be queried after it’s deleted. Set the period together with the organization’s recording retention policy and any sector requirements.
Why does using a shared operator account cause problems?
With a shared account, the audit trail shows the account, not the person; who exported a recording can’t be determined. The need for fast login at shift changes is met not with a shared account but with personal accounts and a short session timeout.
How often should permissions be reviewed?
Reviewing every three months for sensitive permissions such as recording playback and export, and every six months for other roles, is a common starting point. On leaving the company, a change of role or the end of an outside company’s contract, access is removed that day without waiting.