A significant share of the accounts connecting to a camera system don’t belong to the organization’s own employees: private security operators, the service company that installed and maintains the NVR, the building’s management company, shopping mall or office tower tenants, outside teams doing central monitoring in multi-site structures. If a “service” account opened years ago still sits there with admin rights, the problem isn’t in the contract but in the console. Below we look at third parties’ access to live and recorded video in terms of contracts, permissions and technical controls, and give the access model by type of party and the closing of access step by step.
Third-party access scenarios
Third-party access isn’t one-size-fits-all. Risk varies with what the party sees, what it can do and where it connects from. Common scenarios:
- On-site private security: Security company staff do live viewing from the client in the organization’s control room and play back recordings during an incident.
- Remote monitoring center: A company providing alarm verification or after-hours monitoring connects over the internet from its own center.
- Maintenance and service company: Accesses the NVR/VMS with admin rights for firmware updates, disk replacements and troubleshooting.
- Building or complex management: Owns or operates the common area cameras; the tenant organization wants access to recordings of its own area.
- Tenants: Businesses in shopping malls, office towers or organized industrial zones that want to see their own entry points.
- Software and cloud service providers: Providers offering cloud VMS, VSaaS or analytics services with technical access through the platform.
Answer three questions in writing for each scenario. Which cameras can the party see? Which of the permissions for live viewing, playback, export, PTZ control and configuration does it have? Over which network path, and with which authentication, does it connect? If these three questions have no answer, there’s no access model either.
Data controller and data processor relationship
Under KVKK, the data controller is the party that determines the purposes and means of processing; the data processor is the person or organization processing data on the controller’s behalf on the basis of authority given by the controller. Article 12 of KVKK provides that the data controller is jointly responsible with the data processor for taking data security measures with respect to the data the processor handles. Saying “the security company does the monitoring” doesn’t release the organization from responsibility. Responsibility isn’t transferred.
In camera scenarios, the characterization often takes this shape; even so, each case should be assessed on the specific relationship:
- A private security company and a maintenance company monitoring on the organization’s instructions are typically data processors.
- Building management that installs and operates common area cameras on its own decision may itself be the data controller for those cameras; giving recordings to a tenant organization has the nature of a transfer.
- A cloud service provider is usually a data processor; its infrastructure being abroad also requires a transfer assessment.
Whatever the characterization, third parties should appear as recipient groups in the personal data processing inventory. The inventory structure is explained in the camera systems and VERBİS article. The KVKK text and Board guidance are followed on kvkk.gov.tr.
Access model by type of party
The table below is an access model you can use as a starting point for common types of party. It can be narrowed according to the organization’s risk assessment. Broadening it requires a written justification.
| Party | Scope of permissions | Connection path | Identity and duration |
|---|---|---|---|
| On-site private security | Live viewing, limited playback; no export | Control room client, local network | Personal account, per shift |
| Remote monitoring center | Alarm-triggered live video and event clips | VPN or the VMS’s secure gateway | Personal account, MFA |
| Maintenance company | Configuration; playback and export off | Time-limited remote access opened on request | Time-limited account, session recording |
| Building management | Common area cameras; the organization’s area excluded | A separate VMS user group | Personal account |
| Tenant | Own entry point only, live viewing | Web/mobile client, restricted role | Personal account, renewed annually |
| Cloud provider | Platform operation; content access limited by contract | Provider infrastructure | Contract and audit rights |
The principle behind the model is that the role-based permission matrix applies to third parties exactly as it does internally. Separating live viewing, playback, export and PTZ permissions is explained in detail in the camera recording access permission model guide. For outside parties, the most important distinction is the export permission. An exported clip leaves the VMS’s audit scope, can be copied outside the organization’s control and can’t be recalled. Once a clip is out, it’s out.
Clauses the contract should contain
The service contract or an additional data processing agreement is the legal counterpart of the technical configuration. A common gap is a contract that only covers the service fee and fault response time and never mentions access. Contracts with third parties that have camera access should cover at least these topics:
- Scope of processing: Which cameras, for what purpose, at what permission level; a ban on processing outside the scope.
- Acting on instructions: The party doesn’t use recordings for its own purposes and doesn’t take recordings out without the organization’s written instruction.
- Staff obligations: The list of staff with access, confidentiality undertakings, the notice period for staff changes.
- Security measures: Personal accounts, password and MFA rules, security of the devices connecting, a ban on shared accounts.
- Subcontractors: Whether the party can pass access on to another company, and making any such transfer subject to prior approval.
- Breach notification: The time limit and method for notifying the organization of unauthorized access, a recording leak or loss of credentials.
- Audit right: The organization’s ability to audit access logs and the party’s practices.
- Termination: Closing accounts when the contract ends, return or destruction of recordings still held, and written confirmation of this.
Technical controls and monitoring
A contract without technical controls can’t be enforced. Use these controls together for third-party access:
- Personal accounts: Remove shared accounts such as “security” and “service.” On a shared account, the audit trail doesn’t show who did what; it only shows that “someone” did something.
- Camera group restriction: In the VMS, define a separate user group for the party and a role that sees only the relevant camera group.
- Restriction at the network layer: Parties connecting remotely reach only the VMS server’s client ports, not the camera VLAN directly; direct access to camera web interfaces is closed.
- Secure remote access: Use a VPN, VMS gateway or privileged access solution instead of port forwarding and manufacturer P2P services. Architecture options are covered in the P2P cloud access vs. VPN comparison.
- Time-limited access: Maintenance accounts are disabled by default; they’re enabled for a set period after a request and approval, and closed again when the job is done.
- Audit trail and review: Review login, playback and export events of outside party accounts monthly in a separate report; flag after-hours and unusually high-volume playback.
Designing the remote access infrastructure and narrowing outside parties’ connection path can be handled under secure remote camera access, and role and log design together with our camera recording access rights and audit trail work. For general security principles of supplier connections, see also the supplier remote access guide in our network.
Ending access
The most common weakness in third-party access is accounts left open after the relationship ends. The company leaves; the account stays. When the security company changes, the maintenance contract ends, a tenant moves out or company staff leave, apply this list:
- Have all VMS, NVR and camera user accounts belonging to the party been disabled?
- Have VPN, remote access tool and cloud platform credentials been revoked?
- Have shared passwords known to the party’s staff (local admin, camera admin password) been changed?
- Is there any access path set up by the party that isn’t in the organization’s inventory (port forwarding, a P2P connection, a 4G modem)?
- Has the return or destruction of exported recordings still held by the party been confirmed in writing?
- Have the last 90 days of access logs been reviewed, and was any unusual activity found?
- Have the recipient groups in the personal data processing inventory been updated?
Staff changes happen far more often than company changes and are far more easily overlooked. That’s why the contract should require the company to report staff departures within a set period. Don’t rely on this and wait: compare outside party accounts with the company’s staff list yourself every three months. A name not on the list is an account to close.
Frequently asked questions
Is a private security company a data processor or a data controller?
It depends on how the relationship actually works. If the company monitors only on the organization’s instructions, with the purposes and means set by the organization, it’s usually a data processor. If it uses recordings for its own purposes or decides the processing method itself, the situation can change. Make the characterization together with the legal unit and reflect it in the contract.
Is it right to give a maintenance company permanent remote access?
No. Maintenance access should be given under a model where it’s opened on request, time-limited, done with a personal account and with the session recorded. A permanently open port or a shared admin account is a security gap and also makes it impossible to prove who made the access.
Can tenants watch common area cameras?
Instead of general access, access limited to cameras showing only the entry point of the tenant’s own area, and preferably restricted to live viewing, can be considered. Reviewing common area recordings should go through a request and approval process, via authorized building management staff.
What’s the first thing to do when the company changes?
Disable all user accounts belonging to the company’s staff, VPN or remote access credentials and shared passwords on the same day. Then confirm in writing the return or destruction of any exported recordings still held by the company, and review the access logs one last time.