Camera Systems and VERBİS: Inventory Fields and Registration Information

How are camera recordings entered in the inventory and VERBİS? Data category, purpose, recipient groups, retention period and measures fields; the inputs IT needs to provide.
Technical summary
Technology
KVKK Law No. 6698, VERBİS, personal data processing inventory, VMS, NVR
Topic
Reflecting camera processing in the inventory and VERBİS registration
Level
Beginner–intermediate
Prerequisites
  • Camera device inventory
  • VMS user and role list
  • Coordination with the compliance/legal unit
In this article7 sections

When cameras are dismissed with a single line in the inventory, the first question asked in an audit goes unanswered: which camera, for what purpose, how many days, open to whom? Every camera is a continuously running personal data processing activity. Defining this activity correctly in the personal data processing inventory and, if the organization is obliged, in the Data Controllers’ Registry Information System (VERBİS) ensures that the privacy notice, retention period and technical measures tell the same truth. Below we explain field by field how to reflect camera processing in the inventory and VERBİS registration, and which technical inputs the IT team needs to provide.

The personal data processing inventory and cameras

The personal data processing inventory is the record showing which personal data the organization collects, for what purpose, on what legal basis, from whom, to whom it transfers it and how long it keeps it. The Regulation on the Data Controllers’ Registry defines the inventory as the main source to be used for VERBİS registration. Cameras are often a single line in this inventory: “Camera recordings – security.” Two problems come from this in an audit.

First, cameras working for different purposes are lumped into the same line. A building entrance camera, an occupational safety camera on a production line, a license plate recognition camera and a checkout camera have different purposes, different groups of data subjects and often different retention periods. Second, the information in the inventory doesn’t match reality in the system. A common picture: the inventory says 30 days, while the NVR keeps recordings until the disk fills. Or only “authorized bodies” are listed as recipients, while a private security company does remote live monitoring. The paper and the console contradict each other.

The right approach is to define camera processing in the inventory as separate activities by purpose and to match each activity with camera groups. The camera inventory (device list) and the personal data processing inventory are separate documents; the link between them is made with a single field showing which processing activity each camera belongs to. For the structure of the device list, see the camera inventory guide.

How the VERBİS obligation is assessed

Article 16 of KVKK regulates registration of data controllers with the registry; the Board can exempt certain data controllers from this obligation according to set criteria. In practice, the assessment is done with three questions:

  1. Are the organization’s annual number of employees and annual balance sheet total below the thresholds in the Board’s decision?
  2. Is the organization’s main field of activity processing special category personal data? If so, being below the thresholds may not be enough for exemption.
  3. Is the organization in a group separately exempted in Board decisions?

Because threshold values and the scope of exemption change over time, we don’t give figures here. Current decisions are followed on kvkk.gov.tr, and registration procedures on the VERBİS portal. The key point is this: a VERBİS exemption removes only the obligation to register with the registry. The obligations of informing, data security, retention and destruction, and answering data subject applications apply to every data controller using cameras. Exemption from registration isn’t exemption from the law.

Inventory fields table for cameras

The table below shows the main fields camera processing corresponds to in the inventory and VERBİS registration, and the input expected from the IT team. Example values are only to illustrate the format; each organization must write its own real configuration.

Field Content for cameras Technical source
Processing activity Building entry-exit security, production area occupational safety, car park vehicle tracking List of camera groups
Group of data subjects Employees, visitors, supplier staff, drivers Camera locations and frames
Data category Visual recordings; audio recordings if audio is processed; vehicle plates for LPR Camera and analytics capabilities
Processing purpose Ensuring physical premises security, occupational health and safety activities Project justification
Legal ground The KVKK Article 5 sub-paragraph determined by the legal unit Legal/compliance unit
Retention period Example: 30 days; incident recordings until the incident is closed NVR/VMS retention setting
Recipient groups Private security company, authorized public bodies, maintenance company List of access accounts
Transfer abroad If a cloud VMS or P2P service is hosted abroad Service provider contract
Technical and administrative measures Role-based access, audit trail, encryption, network segmentation Security configuration

In VERBİS, data categories and purposes are largely selected from predefined lists. In practice, camera recordings are mostly associated with categories such as visual and audio recordings and physical premises security; verify the current names of the options in the system. If audio isn’t recorded, adding “audio recording” without justification means declaring processing that doesn’t exist. If audio is recorded, it should appear explicitly. The particular risks of audio are covered in the audio recording in cameras article.

Recipient groups and transfers

The field most often left incomplete in camera processing is recipient groups. A recipient is the person or organization to which data is transferred or made accessible. In camera systems, this transfer often happens not by sending files but by opening a user account. Every outside party with an account in the VMS is a recipient. Write these situations into the inventory as recipients:

  • Private security company: Staff with live viewing or recording review permissions.
  • Maintenance and service company: Technicians with admin access to the NVR/VMS; they can see recordings during maintenance.
  • Building or complex management: Management staff with access to common area cameras.
  • Group companies and headquarters: The central monitoring team in multi-site structures.
  • Cloud service provider: Video flowing through or stored on a cloud VMS, VSaaS or manufacturer P2P service.
  • Authorized public bodies and institutions: Transfers made at the request of the police and judicial authorities.

For cloud-based services, the IT team should clarify in which country the data is hosted and from which country the provider’s support team can access it; the transfer-abroad assessment is based on this information. A P2P cloud service left enabled unnoticed at installation is also part of this problem. The access model for outside parties is explained in detail in the third-party camera access guide.

Mapping technical and administrative measures

In VERBİS, measures are also selected from a list. The problem is that the ticked measure isn’t applied on site: “access logs are kept” is ticked, but the VMS audit trail is off; “network security is ensured” is ticked, but the cameras are on the same VLAN as the user network. Map every declared measure to a piece of evidence. A measure without evidence is just a declaration.

Declared measure What it means in the camera system Evidence
Permission matrix and access restriction Role-based VMS users, camera group restriction Role–permission export
Keeping logs Audit trail of viewing, playback and export events Sample log output
Network security Camera VLAN, ACLs, no direct access from the internet Network diagram, ACL rules
Retention and destruction Maximum retention period per channel, destruction record Settings screenshot, record
Update management Firmware tracking and application log Version inventory
Confidentiality undertaking Undertakings from monitoring staff and the service company Signed documents

This mapping also forms the evidence set for camera controls in ISO 27001 or TISAX audits; you don’t do the same work twice. When you document the measure and evidence structure together with the camera recording retention, deletion and destruction policy work, the inventory, policy and configuration are fed from a single source.

Keeping it up to date

The inventory and registry entry aren’t a one-off job. The camera system lives; if the inventory isn’t updated with it, it carries wrong information six months later. These changes should trigger a review of the inventory:

  • Starting to monitor a new area or location, or a change in a camera group’s purpose
  • Introducing a new capability such as video analytics, license plate recognition or audio recording
  • Moving from a local NVR to a cloud VMS, or starting a remote monitoring service
  • A change of private security, maintenance or building management company
  • A change in the retention period, or storage capacity no longer meeting that period

The method that works is simple: add the question “is there a KVKK inventory impact?” to the change request form for camera projects, and forward the answer to the compliance unit automatically. Also, at least once a year, compare the camera lines in the inventory with the device inventory, the VMS role export and the retention settings. The gap between what’s written in the inventory and what’s configured in the system is one of the findings most easily spotted in an audit and hardest to explain.

Short checklist for the annual comparison

  • Is at least one camera group mapped to every processing activity in the inventory; is any camera left unmapped?
  • Is the retention period in the inventory consistent with the actual oldest recording date on the NVR/VMS?
  • Is every outside party with an account in the VMS among the recipient groups?
  • Does every declared technical measure have current evidence?
  • Are the privacy notice and warning signs consistent with the purposes and categories in the inventory?

Frequently asked questions

Does every company using cameras have to register with VERBİS?

No. The registration obligation is assessed according to exemption criteria set by the Board; these criteria are based on measures such as number of employees, annual balance sheet total and main field of activity, and can be updated over time. Using cameras alone doesn’t create a registration obligation; organizations within the exemption are still subject to KVKK’s other obligations.

If we aren’t registered with VERBİS, do we need to prepare an inventory for cameras?

The Regulation on the Data Controllers’ Registry sets the inventory obligation for data controllers obliged to register. Even so, defining the camera processing activity with a written inventory record, so the privacy notice, retention period and technical measures are consistent with one another, is good practice regardless of the obligation.

Under which data category are camera recordings shown in VERBİS?

In practice, camera recordings are usually associated with categories such as visual and audio recordings and physical premises security. Which option is used is determined by the processing purpose and the current list of options in VERBİS; if audio is recorded, this is reflected separately.

Does the VERBİS registration need updating when the number of cameras increases?

An increase in the number of cameras alone may not change the registration information. If there’s a new purpose, a new data category, a new recipient group, a cloud service involving transfer abroad or a change in the retention period, the inventory and registry information are reviewed and updated.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles