GDPR For Video Surveillance Guide

Author: Charles Rollet, Published on Apr 12, 2018

The European Union’s General Data Protection Regulation (GDPR) comes into force on May 25, but there is much confusion and no clear guidelines on exactly how these new regulations will impact the video surveillance industry.

We have compiled the following guide, based on our own research into the primary sources for the regulation as well as numerous discussions, covering the following:

  • GDPR basics
  • Surveillance industry concerns
  • New regulations / no legal precedent
  • GDPR terms defined
  • Public signage requirements
  • Design concerns
  • Impact on recording video
  • Usage of biometrics / facial recognition / gender / age recognition
  • Dealing with data requests from people
  • Dealing with cybersecurity / vulnerabilities
  • Who has 'exceptions' to the GDPR
  • Do I need to get certified?
  • Do I need to hire a Data Protection Officer?
  • Do DPOs need a certification or some sort of qualification?

When finishing this guide, you should be able to answer our 10 question quiz on GDPR.

GDPR Basics And Industry Concerns

The GDPR regulates all companies processing the personal data of people in the EU, regardless of where the company might be based. Because video footage of someone is considered their data, the video surveillance industry is directly impacted by the GDPR.

The GDPR gives data subjects in the EU significant new rights to access and remove their data while imposing restrictions on how this data can be collected. But the GDPR itself makes no mention of how it applies to video surveillance and threatens tough penalties on misconduct.

Surveillance Industry Concerns

That has led to a significant amount of uncertainty and fear for video surveillance, an industry where unprepared companies could find themselves subject to big fines. GDPR provisions like the right of people to request their data be removed or the need to obtain consent from data subjects also raise significant logistical hurdles in video surveillance, especially in areas like Artificial Intelligence / AI / Deep Learning where attempts are made at categorizing people by face, age, gender and ethnicity.

Warning - Regulations New / Imprecise / No Legal Precedent

Before reading this guide, you should be aware of the following factors:

  1. GDPR regulations are imprecise and can be interpreted in a number of ways. Most importantly, the GDPR makes no explicit mention of video surveillance, so we have yet to see exactly how GDPR regulations will be applied to the security industry.
  2. The GDPR only goes into effect on May 25th, so there are no legal precedents we can refer to in order to interpret its regulations.
  3. Despite 1 and 2, manufacturers, consultants, and many others often claim to provide fully accurate insights GDPR compliance, something which can require paying them substantial fees. Taking their advice at face value may present risks, so we have compiled our guide using primary EU documents to the fullest extent possible rather than the opinions of third parties.

*********** *****’* ******* **** ********** ********** (****)***** **** ***** ** *** **, *** ***** ** **** confusion *** ** ***** ********** ** ******* *** ***** *** regulations **** ****** *** ***** ************ ********.

** **** ******** *** ********* *****, ***** ** *** *** research **** *** ******* ******* *** *** ********** ** **** as ******** ***********, ******** *** *********:

  • **** ******
  • ************ ******** ********
  • *** *********** / ** ***** *********
  • **** ***** *******
  • ****** ******* ************
  • ****** ********
  • ****** ** ********* *****
  • ***** ** ********** / ****** *********** / ****** / *** recognition
  • ******* **** **** ******** **** ******
  • ******* **** ************* / ***************
  • *** *** '**********' ** *** ****
  • ** * **** ** *** *********?
  • ** * **** ** **** * **** ********** *******?
  • ** **** **** * ************* ** **** **** ** *************?

**** ********* **** *****, *** ****** ** **** ******** *** ** ******** **** ** ****.

GDPR ****** *** ******** ********

*** **** ********* *** ********* ********** *** ******** **** ** people ** *** **, ********** ** ***** *** ******* ***** be *****. ******* ***** ******* ** ******* ** ********** ***** data, *** ***** ************ ******** ** ******** ******** ** *** GDPR.

*** **** ***** **** ******** ** *** ** *********** *** rights ** ****** *** ****** ***** **** ***** ******** ************ on *** **** **** *** ** *********. *** *** **** itself ***** ** ******* ** *** ** ******* ** ***** surveillance *** ********* ***** ********* ** **********.

Surveillance ******** ********

**** *** *** ** * *********** ****** ** *********** *** fear *** ***** ************, ** ******** ***** ********** ************** **** ********** ******* ** *** *****. **** ********** **** *** ***** ** ****** ** ******* their **** ** ******* ** *** **** ** ****** ******* from **** ******** **** ***** *********** ********** ******* ** ***** surveillance, ********** ** ***** **** ********** ************ / ** / Deep ******** ***** ******** *** **** ** ************ ****** ** face, ***, ****** *** *********.

Warning - *********** *** / ********* / ** ***** *********

****** ******* **** *****, *** ****** ** ***** ** *** following *******:

  1. **** *********** *** ********* *** *** ** *********** ** * number ** ****. **** ***********, *** **** ***** ** ******** mention ** ***** ************, ** ** **** *** ** *** exactly *** **** *********** **** ** ******* ** *** ******** industry.
  2. *** **** **** **** **** ****** ** *** ****, ** there *** ** ***** ********** ** *** ***** ** ** order ** ********* *** ***********.
  3. ******* * *** *, *************, ***********, *** **** ****** ***** claim ** ******* ***** ******** ******** **** **********, ********* ***** can ******* ****** **** *********** ****. ****** ***** ****** ** face ***** *** ******* *****, ** ** **** ******** *** guide ***** ******* ** ********* ** *** ******* ****** ******** rather **** *** ******** ** ***** *******.

[***************]

GDPR *****

*****, ** *** * ****** **** ** *** *** **** affects ***** ************, **** *** **** *** **** *****, ********* in **** ****** *****:

  • **** ***********
  • **** **********
  • **** ********
  • ********* ****

Data *********** - ***** ************ *** *****

**** *********** *** *** ********* **** ******** ******** ** *** GDPR; **** ** *** ****’* ********** ****** ***** ** **** controllers. *** **** ** * **** **********?********* ** *** ****, **** “********* *** ******** *** ***** ** *** ********** of ******** ****.” ** *** ***** ************ *******, **** *********** are *** *****: * ******** **** ******** **** * ******** camera ******, *** *******, ** *** ********** ** *** ***** surveillance **** ** ********. (****: ********* **** **** ******** **** on ***** ********* *** **** ********** **** *********** ** **** specific **** ***, ** **** ** *** *** ********* *** “data ***********” ** **** ****** *******.)

Data ********** - ***** / *****, ******** ***********

**** ********** *** *** ********* **** ******* ******** **** ** behalf ** **** ***********. ** ***** ************, ***** ********* ******* personal **** ** ****** ** ** *** **** *** ****** to ** ********** **** **********. *********** ** ************* ***** **** be ********** **** ********** ** **** ******** ****** ***** ********* data ** ****** ** *** *** ****. *** *******, ** an ********** ******** ** *** ****’* ***** ********* **** *** maintenance ********, *** ********** *** ** ********** * **** ********* under *** ****.

Data ******** - ******

***** *** *** ****** ***** ******** ** ******. *** **** creates * **** ** *** ****** *** **** ********.

Biometric **** *******

*** ********** ***** “******** [**********] * ******* ******”. ***** ********* techniques **** ****** ** *** *********** **** ***** **** ********.

Surveillance ****** / ********** **************

*****, ** ******* *** ****'* ****** ****** ** ***** *** areas:

  • ****** *******
  • **** ********** ****** ***********
  • ******* *********
  • *** ** ********* **** (****/******/***)
  • **** ********
  • ***** ********/************* *********
  • *************/******* *******
  • ********** ************

Public ******* **** *********

******* *** **** ******************* ** ******* ************* ************ ********** ****** ********** *******, ** ** **** ********* **** **** *** ************ ********* to ****** *** ****** ** **** *** ********* ***** ** them. **** *** ** **** **** * **** ******* ****** that **** *** ***** ******* ** ******* **** *** ******** contact *********** ** **** ******** *** ****** **.

***** *********** *** ******** **** *** ***** ** *** **** least *** ** ***** ********** **** ***** ************ ** ****** place,** ******* ***** **** ******** **** ******* *** **** *** ********* ******* should **** ** ******** (“*********** ** ** ******** ***** ******** data *** ********* **** *** **** *******”):

  • *** ******** *** ******* ******* ** *** **** **********
  • “*** ******** ** *** ********** *** ***** *** ******** **** are ******** ** **** ** *** ***** ***** *** *** processing”
  • “*** ****** *** ***** *** ******** **** **** ** ******, or ** **** ** *** ********, *** ******** **** ** determine **** ******”
  • ********* **** ******** ** ***** “***** ** ***** * ********* with * *********** *********”
  • *** ********* ** *** ***** ** ******* ******, *************, *** removal ** *** ****

***, ** **********, **** *****:

  • *** ******* ******* ** ***, ** *** **** ***
  • ** *** **** **** ** *********** ** ******* *******, *** relevant ********** ** *****
  • ********** ** *** ******** **** (** ***** **** *** *** user)
  • “*** ********* ** ********* ********-******, ********* *********... ***, ** ***** in ***** *****, ********** *********** ***** *** ***** ********, ** well ** *** ************ *** *** ********* ************ ** **** processing *** *** **** *******.” (**** ***** ****** ***** ** things **** ****** *********** ** ***** ********* **********)

*** ***** ****** **** ****** *** **** ** *** ******* visible *** ** ******* *******.

Additional ****** *********** / **** ********** ****** **********

*** **** ******* *** ****** ************ ** ****. ** *** case ** “********** ********** ** * ******** ********** **** ** a ***** *****,”******* ** ** *** ************ **** * “**** ********** ****** **********” (****) ** ** conducted ****** *** ****** ** *********, *********:

  • “* ********** *********** ** *** ********* ********** ********** *** *** purposes ** *** **********, *********, ***** **********, *** ********** ******** pursued ** *** **********”
  • “** ********** ** *** ********* *** *************** ** *** ********** operations ** ******** ** *** ********”
  • “** ********** ** *** ***** ** *** ****** *** ******** of **** ********”
  • “*** ******** ********* ** ******* *** *****, ********* **********, ******** measures *** ********** ** ****** *** ********** ** ******** **** and ** *********** ********** **** **** ********** ****** **** ******* the ****** *** ********** ********* ** **** ******** *** ***** persons *********.”

***** **** ** ********* ** **** *********** ***** ** *** processing ********* ***** *****. *** **’* ******* ** ******* ***** has************* ******** ***** ** ** *********** *** ***** ** ** published ** **** *********** ********, ** ********** ********** ** ***** a ******* ** *** **** ** * **** ********. ******* where ** ****** ** ********* ** ********* (******** ******, *******, local *********, ***).

************, “***** * **** ******* **** ******** *****, *** **** controller **** ** ******** ** **** ***** ************ *** *** processing **** *** *********** *********”.

No ******* ******* *********

*** **** *** ** *** ****** ** *** **** **** should ** ****** *** ****** **** **** ****** *** ** kept *** ****** **** ** ********* *** *** ******** ********. The **** **** ****** ****** ******* ******* *** “****** ********, scientific, ** ********** ******** ********” (******* *) ** *** **** **** ************ ****** *** ***** ********** is ****** ** ********* ** *** **** ****** ** *** prove ** ** ****** ********* ** ***** *******.

Usage ** ********* **** ********* ********** (****/******/***)

*** ** ***** *** ********** ****** ********* **** ********* ********** and *** ********** ********* * ** *** ****.

********** ** ******** **** ********* ****** ** ****** ******, ********* opinions, ********* ** ************* *******, ** ***** ***** **********, *** the ********** ** ******* ****,biometric **** *** *** ******* ** ******** *********** * ******* ******, data concerning health or data concerning a natural person’s sex life or sexual orientation shall ** **********. [emphasis added]

The ********* ** ********* ***********

*******, *** **** ********** * ****** ** ********** ** **** prohibition. *** ***** ************, *** ******** ********* ** *** *******-****** “reasons ** *********** ****** ********.” ********** ** ****** ****** *** currently ******** **** ***** ****** ******** ******* ******** ****. ** far **** *** ****** ******* ** *** *********** *** ***** prevention.

*** *******, ***** *** ****, * ******** **** ***** ****** be ********** **** ***** ****** *********** ** *** ******* ** identify **** ******* ******* ******* ***** ****. * ******** **** could *********** *** ****** *********** ********** ********* ********* ** **** as ** ** ****** ** *** ** ****** ***** ** be:

  • “********* *** ******* ** *********** ****** ********”
  • “************* ** *** *** *******”
  • ********** ** *** “*** ******* ** *** ***** ** **** protection”
  • ******** “******** *** ******** ******** ** ********* *** *********** ****** and *** ********* ** *** **** *******.”

** * ******** **** ***** **** *********** ** ***** *********** only *** ** *** *** ** ****** ** ** ****** GDPR *********** ********* ** *** ** *****’* ************** ** *** aforementioned ******. *******, * **** ***** **** *********** ** *** shoppers **** ** ********** ****** ******** **** ***** ****** ** in ****** ** *** ****. (*** ****** *** **** ******* 2(g) ********* *)

Dealing **** **** ******** **** ********

******** **-** ** *** **** ***** **** ******** ********* ****** to ***** *** ****,********* *** ******* ****** *** ******** **** ********* ***** **** *** *** right ** ******* **** **** **** ** ******* (“*** ***** ** ** *********”) ***** ******** **** ** ******** ** ********* **** ** charge. ***** ************ *********, ** **********, **** ** ******* *** give **** ******' ******** **** **** **** ****** **** **** requests, *** ******* ** ********* ***** ** * **** ******* that ********** ***** ****** ** ****.

***** *** **** ***** ** ***** *********, ***** *** ************** concerns **** *** ************ ******** **** ***** ****** **** ** impossible ** ****** **** ** ********.

*******, ***** ****** **** ********* ************** **** ***** ****** ***** in *** **** ** ***** ************, ******** *** ******, ***** of *** ******** *********** ** **** ********** *** ******* ** Information ******** *** **** ********** ******* ** ******* ** **** LLP. *** ***,*** **** ********** ** *** ******* ** *** ***** *** *** *** user “** *** ** * ******** ** ******** *** **** subject” ** ** *** ********* ** ******. ********* *** **** deny ** ****** **** *** ******** **** *** “********** ********* or *********.” *** ***** *** **** *** ********* ** ****** if *** **** *** ********* ** *** ****** ********, ********* likely ** ***** ** ***** ************ ** ****** ******. *** denial ** * ******* ** * **** ******* **** ** explained.

********* **** ******* ***** ** ******* ** **** ************ **** ********. ***** **** ***** ************ **** ** **** for **** **** * *****, **** ***** **** ******** *** video ************ **** **** ****** ** **********. *** *** ***** period ** **** * ********* ******** **** *** ***** *** exploit ** **** *********** ********. ********** **** * ******** *** be ***** ***** ** ***** ** *********** ** ********* *** spirit ** *** ****, *** **** *** *** ******* **** we **** ****** ** **** ****** **** **** ** ***** it.

Dealing **** ***** ******** / ***************

*** **** ******** ********* **** ********. ******** **** ** ******** if **** “**** * **** ** ** **********’* ****** *** freedoms." ** **** *** ****** ** ***** ******** *** ******** breached ** ***, *** **** **** ***** ** ** *****.

**** *********** **** ** ***** ** ****** ***** *******’* **** protection ********* ***** *** ****** *** ** *** ****** ******** affects ******* **** ********, ** **** ****** **** ** ****. However, ** *** **** ********** *** ********* ********** ******** ** place ** ******* *** **** ** ** ****** ****** ** materialize,** ** *** ********* ** ****** **** ******** ** *** risk ** ***** ******** ****. ** ********* ***** **** ******* ** * ****** ** logistically *********, *** **** **** ****** “* ****** ************* ** similar *******” ** ** ******.

**** ********** **** **** ****** **** ******** ** ***** **** controllers, ******** *** **** **** *** ******* * **** ***** in ***** *****.

** ** ******* *************** **** **** ******** **** ************** ***** ** ******** ** ***** ********** ** *** ****. The ****** *********** **** ***** ** **** *********** *** **********, and ** ** *** **** *** ** ************* (*** ** not ******** ****** *** ******** **** ** ****** ** *** EU) **** **** ***** ***** **********, ****** *** ***** *********, which ** ****** ********** **** **********.

*** **** *** ** ********** ******* ******* **** ******** **** be ******** ********* ** *********** *********** ** ***. ** *** very *****, **** *********** **** ****** ** ********* *** ****** to ******* ********* ** ** ******* ** *********** **********.

When ** *************/******* ******* ********?

*** ****’* ******* ** *********** “**************** *** **********” ** **** ** ****** **** **** protection ** “** ****** *** ** *******.” ******* ** ***** caveats, ** ***** *** **** **** ********** **** ******** ****. In ***** ************, **************** (*.*. *************) ***** **** ****** *********** ** ******** *** ***** ** **** ********.

*** **** **** *** ********** ***** **** ************* ** ********. However, ** ********* ** ******* **, *** **** ** *** GDPR ** **** “**** ******** **** ***** *** ********* *** each ******** ******* ** *** ********** *** *********”. **** ***** that ******** ******* ** *** ********, ******** ****** ** *** camera ****** *** ** ******** (*.*., ******** ******* ** *** background ** * *****) ** ****** ** **********.

What ********** ** ********?

*** **** ********* ********* ********** ********* “***** **** ****** *** ******** **** ************** ** *** person *** ** *** ********** ** ****** **.” *******, ** is ******* ******* **** **** ***** ** ***** ************. ** likely ******* ***** ****** ****** **** ***** ******** *******, **** as ******* *********, ******* **** ***, ***, ** ***** ************ access. **** ******** ******* **** *********** ***** *** ********** ********** ****** *** ********, *** **********.

Do * **** ** **** * **** ********** *******?

***** ** **** ******* **** ***** ******* ***** ********* *** data ** ****** ** *** ** **** **** ** **** a ****-**** **** ********** ******* ** ************* ****** *** *******’* data ******** *** ****-*********.

*** ** ********** *** ********** ** * *******’* “**** ********** ******* ********** ** ********* data ** * ***** ***** ** ******* ***** *****, ******* and ********** ********** ** ***********” ** ****** **** * ***. A *** ** *********, *** *******, *** “* ******** ******* responsible *** ********** ******** ******* *** ****** ******,” *** ** Commission ******.

** **** ***** ***** ****** **** *** ***** ***** ******* large ****** ****** **** **** ****. *******, ******* *** ** Commission *** *** **** ******* **** “***** *****” ******** *****. Additionally, **** *** ** ********** **** ***** ********* *** *** even ** * ***** ****** **** *** ****’* *** *****; they *** **** ****-**** ** ****.

Do **** **** ************* ** ***** **************?

******* ** *** **** ** ** ****** **** **** **** any **** ** ****** ************* ** *************.

*** **'* ******* ** ******* ***** (** ******** ** ******** body)********* **** ************ **** ** ******** *** ****** **** "**** ****** **** expertise ** ******** *** ******** **** ********** **** *** ********* and ** **-***** ************* ** *** ****. ** ** **** helpful ** *** *********** *********** ******* ******** *** ******* ******** for ****.” ** **** ***** **** "*** ******** ***** ** expertise [** * ***] ** *** ******** ******* *** ** must ** ************ **** *** ***********, ********** *** ****** ** data ** ************ *********."

** ***,*****’* **** ********** *********** *** ***** *** **** ** ******* ** ******* ********* *** ************* *********** ******** * ****-**** **** *** * ******* ****** ** work ********** (**, ** *** *** *** ** **** **********, at ***** *** ***** ** ********.)

Do * **** ** *** *********?

***** *** ****, *** **** ** ************* ******* *** ******** voluntary (******* **, ******* *). ********* **** ********** ********* *********** **** ** ***** ******** *** ********* ** **** ********* by ***** ***** ******* *************, *** **** ************** *** *** *********. ***** ************** *** carried *** ******* ** ******** ******* *** *** ** ********. Do *** ** ****** **** ******** *** **** ** ************* is ********* ** ** ********** **** *********, *** *** *****, integrators, ** *************.

Are ***** ********** ** *** ****?

******* ** ** *** ********** ** ****** ****** *** ***** ** ******** **** ** core **** **********, ********* *** ***** ** ** *********, *** right ** ****** *********** ******** ** * **** *******, *** the **** ** **** ******** *** *********** *********** ***** **** sort ** ********** ** ***** **. ***** ********** ******* ******** security, *******, ****** ********, ******* ***** *****, *** ***** **********.

** ** ******** **** ********** ** ****** ****** **** ** considered ** ********* ****** ********, ********* ************ ********* **** *********** burdens. *******, ** **** ** *** **** *** ** **** extent “****** ********” ******* ** ***** ************.

**** ** ***** **** ******* ** ** ****, *** *******, someone ******* **** ******* * **** ****** ******* **** *** bank ****** *** ***** ************ ******* ** *** ***** *** right ** ** *********, *** ** ********** ****** ******* *******-********* agencies ** ****** *** ***** ********** **** **** ** ***.

****

****** ****'* ** ******** **** ** ****.

Comments (56)

**** ** * **** **** ***** ********* ******* **** ****. There *** **** ** ********* ****** ** *** **** ******** by *** ******* ** **** *****. ******* **** ********* ***** to ** **** ** ******* *** ********. ***** **** ******* to ******* **** **** *** ****** ** ******* ********* ** this *****. ********* ***** ** ********** ****** *** *** ** deadline.

**** **** *******!

*´* **** ** *** * ******* ******:

************* *** ******* **** *********** ** ** *** *** **** of *** ******!
*** *** **** **** ** ***** ** *% / *% of *** ********* ***** ******** ** *** ********/*******.
(****** ** €** * / €** *)

** ** ******** ** **** *** ********* / ********** ***´* be ***** (** ***** *** ********).

*** *** ******** ******** ** *****-* ********* *** ******* ** system ****** *** ***********-*********** *************.
******* **** ************* *** *** **** *** **** *** **********/********* in ******* ** *** *** ************ ** **** ** ********* GDPR *********** ** ****** ****** ** *************.

** *******, ********** **** *******!

* ***** **** ** ***** ***, *******, *********** ******** ***** *** **** **** *********** *** **********. ** **'* not **** *** ***** (*.*. **** ***********) *** ***** **** themselves ******* ** **** *****; ************* ** *********** *** *** considered **** ********** ***** **** ** *****.

** *******, ***´** ********* *****,

*** ********* * ************ ** *** **** ** "****** ************" can´t ** **** *********** ** ******** ** ****.

*** *** ********** ** ********* ** *** **** ** "****** installer" ***´* ** ***** ** ******* ** ******** ** **** for ***************** ** * ******.

**** ** **** *** ************ ** ****** ************ ****** ********* like *.*. *****-*******, ** *** ** *****, ** *** ******* doesn´t ****** ** *** *****.

** ** **********, **** **** **** ** ***** ********** ******, may ** ***** ***** *** ******** *** **** ******** ********* to *** *******.

** ** ********* *** *** *** ******** ** **** * very ********* ************* ** ****** **** ******** ** ******** ** GDPR.
*** *** ******** ***** *** **** ** ** ***** *** any *******.

** **** *** ** ******** ** *** * ************ **** the ********* ** **********, ** *** ******** ******** * ***** (OR *************), **** ****** ************* ****´* ***** *** ************.

** ************* **** ******** ********* *** *** ********!

***, ***** *** *** **** ** *** **** *********.

**** *********** *****. *'** ********* * *** ***** ********** **** new **** ***. ***** ** *** *** ********* *** ********* level ** ***** ****** ** ** *** ********.

****** **** ** *** ** ****** ***** **** ******** ** actively ******** * *********** *********?

** ******, ****** *** **** *******. * ***** ****** ** the **** ******* ******* *********** ********** ** *** ****: ** hopes ** ****** ***** *** ****** ********** **** ****** ** comply ("******'* ******** **** ********** ***** *******")

*****'* **** ******** ***** ********, *** ******************* ******* **** *********** *** ******** ***** ********** ** *** GDPR ** ***** ******** **** *********** ** ****.

** ***,

******* ***** ********** (** ***********) ***** ** *** **** **:

• ******** ********;

• ******* (** ******** ;-)

• ****** ********

• *** **********, *************, ********* ** *********** ** ******** ******** or ******** ** ****** ** ********* ***********

***** **** **** ** ***** ** * ********* ** *** an *********.

***** *** *** ****! **** **** ***********

**** *** *** **** ********* * ******* *******

**** ** *** ****** ** *** ****** ******* **** ***** and *********

***** ****

***** ********

***** ********

****** *** ***** *** *** **** ********

********* ** ***** ** *** ******* **** *** ***** *****

** ****,

*** ** *****'* ****** **** *** ******* *********** ** *** GDPR ** *** ********. *******, **'* ***** *********** **** **** American ********* *** ***** ******** ** *** ****, ** *** legislation ****** *** ******* ***** ********* *** ******** **** ** EU ******** ********** ** ***** ** ** *****.

** ** **** ********* ***** *** *** *********** ********** *******, the **** **** *** ******* *** *** ** *** ******** technology ** *** ********. *******, ** ***** ******* ***** *** vulnerable ** * ******** **** ******, **** *** *** *** risk ** ******* ** ****** **** *** ****'* ********** ** breaches**** *** ** ******* **.** ***, **'* ******** * **** **** ** ******* **** systems.

**** ** * ******** ***** ** *** ********** ****** ** the ******** *********** ** *********.

***** *** ~**** ******* *********** ** *** **, *** ******* in ************* ******** *********** ***** ** ** ********* ** ****** and ** ****. **** ** ***** **** *** ******* *** really **** ** ****** ********** ** ******** ****** *********.

**** ** ****** ****** ** * ********* **** ******** ****** compliance, **** ** * ********* ***** **** ** *******. **** is **** ** *** ********** ** ***********. ****** **** ***** and **** **** ** *** *** ******* ******* *** ******* research.

** *********** (*** **********) **** ******* ** ******** * ****** and ***** *** ****** ********** **** ****** ** *** ******* of ****** ******* ************ *** *** ********** ******* *** ******** based ** **** ******* ******. ** **** ** ********* **** in *********** **** *** **** ********* **** ** ** ***** by *** ******* ********** *****://********.*****************.***/ ** ****** *** * ******** event ** ***. * **** **** ** ** * ***** at *** *********** ********** ** ****** ** **** ********** ******* 2.0 **** ***** ******* ** **** ****** **** **** *****. http://www.cvent.com/events/identiverse-2018/event-summary-4d21a5f6b479493fb0168947827a6a3f.aspx

********* ****** ** ***** ** *** ***** ******** **** ** a **** ******.

**** ********** ** * ************** (*** *********) ******* *** *****´* require *** ********* ********.

**** ** ***** ****** ***** ** **, ** ****** ** the **** ** ********** ******* ************* ******** (******** ********, ******* control, ********,...).

* ***’* ***** * ********* **** **** ****

******** ******* **** ***** **** ** *** ***** ********* **** many ** ***** ******* ******* *** *** **** ** *****

****** **** * ***** *** *********** ***** ******* *** ** push ** ********* *** ** ***** *** ** ***** *** for *********** **** ****** ***** ********* *** ***** ********* ***** are ********* ** *** ***** **** ******* *** **** ****

**** ******** ******** ** *** *** ***

***** ****** ** ********

** *** ******** ***** **** ** *** *** *******

** ****

*** *** ** ***** ****** *** ** **** ** ****** to **** *** ** *****.
** **** **** ** *** ********* ** *** ** ** set ** *** *** ************* *** ** *****.

* **** *** **** ******* ***** *** **** * *** of ******** **** (** **************, **** ************* ***** ** *** and ** **** *** ****** *** ****).

*** *** ***** ***** **** ** ***** ***** **** ** shared *** **** **** ********* ** ** ****** ** ******. Frankly, *'* ***** ***** **.

***** **** ** ** ** ********, ** ** ********** ****** attention, ********** ** ***** ** *** ******** *******. ** * non-EU ******* ******* ** *** *****, **** *********:

- **** * ******** ******* ******** ****** ** *** ****-******* standard? *** *******, **** ******* **** ***-*****/*****?

- ***** *** ***** ******** ** ****, **** ***** ** a ****************************** **** **** ********** ****** *** ** ******-*****?

- ***** ** ** *** *********** ****** ******* ******** ********* being ********* ** ***** ** *** ****. *** *** **** itself *** ********* **** *** ********* ** ***** * "****** standard" ** *****.“** **** ** *** *** ****** ********,” *ě** ******á, *** European ************ *** *******, **** ********. (*** "******'* *** **** ********** ***** ****** ******* ********* *********.")*** ******* *** **** ****** ***-** ********* ** ****** (** long ** ****'** ********** *** **** ** ** ********), ** effectively ******* **** ********** ********** ********* ** * ******* ****** too.

************, *** ************** ********* ** ******** **** ** * ***** ******* *** only **** ***** ** **** ******* ** ******* "** ******** level ** [****] **********." ** ***, *** ******** ********** ***************** ** ********* - ********* *** ** *** ****** - as ********* **** ********, *** *** ******** ***** ***** **** the ** ** **** ******* **** ***** ***** ** ******** data **********. **** *** *** ** ********* **** ***** ************* ******** **** ********** *********** ** **** ******* ******** *** GDPR ** ** ****** ** "******** ********" **** *** **.

- * ***** *** **** ****'* ***** ** *** ** the **** ************ *************** ** *** **** *** *****. ** based *** ************** ********* ** *** **** *** ** *********, rather **** *** ******** ** ***** *******.

*** ******* ***** ** ********** ******* ******* ********, ** ** still ** *****. *** ***** **** ** **** ** ***** with **** ** ******* ********** *** ***** ******* ********** ** which *** * ******* **** *** ** ** ***** ** the *****.

******* **********

**** ********** * ** ********* ** ***** ********** *******.

** * **** ********* ****** ****, *** ** * ****** plug, *** *** **** **** ** **** ** **** **** we *** ***** ** ***********.*** **** ********** * ** * Co-Founder

**** *** **** ** **** **** ** ***** *** ** particular *** ** ******* ********** ********* *** ****** ****** ******** across ********** *******,**** ******** ***********-**.* **** ************ ********

**** **********, * ** **** ********* *** ***** ******.

***** *** *** **** ***** *********** ******** **** **** *** into *** ******

****** *** *******.

******: ******* ******** **** ** ****** **** ********.

******** * **** ******, ** ** ** *** ***** *** is *** ***** ** ** *** ********* *** **** *********, to ** ********** **** *** ***** ******** ** ****** *** "service ********". **** ****, **** **** ****, ******* ** ** on * ******, * *** **** ** ****.

*** ** *** **** ******* ** *** ******** ***** ** this ***. * ********** ** ****** ********* ********** *** **** of ** ******** **** ****** ** *** ** ********** ** where *** ******* ** *****. **** ***** **** ** ** citizen ******* ******* *** ** ** ********** ** * ******* outside *** **? *** ********* ***** ******* **** **** ***** bound ** *** ***?

** ****, **** ********. *** **** ****** *****'* ******** **** any ******* ** ******** ** *********. ** **** *** **** it ****** *** ******* ***** ********* *** **** ** "**** *********** *** ** *** *****" (******* *.) ** **, ** *****'* **** **** * ******* ********** the ******** **** ** ** ******** ******* *** ** (******* expats ** ********) ***** ** ******* ** *** ****.

*******, ***** ** ******* * *****, ***-**-******* **** * ******* or ***** *** ** ** *** ** ** *** **** of *** ********** ** ********** * "**** *******" ********* ** the ****.

***** *** ******* * **** ** *******’* **** ****** ** gdpr

*** **** **** **** ** *********

** ***** ** ******** **** ** **** *** ****** ** their ********

*** ** ********** *** ****** * ****** ** ****** ** having "******** **** **********" *** *** ******** **** ** ** data ******** *** ** **** **.

"*** ******** ********** *** ** *** ********** *******, *********, ****** (commercial *************), ***** *******, ********, ******, **** ** ***, ******, New *******, ***********, ******* *** *** ** (******* ** ********** ****** *********) ** ********* ******** **********. ******** ***** *** ******* **** Japan *** ***** *****," ("******** ** *** ********** ** ******** **** ** ***-** *********")

* ****** ***** ***** ***** ** ********** ** **** ******** data **********. *******, **** ******'* *********** ****** ******* ********. ********, these *********** **** ***** *** ******** ** ******** ****. ******* it's **** ** ***** ** ***, * ***** ****** ** only ******** ** **** ** **'* ************ *** ******** **** of ** **** ******** ******** ** ******* ** ******* ******* not ** *** **'* ****.

** *** **** ** ***** *** *******

****** ** ***** *********

****** ***** **** ******* *** ** ******* ** ******* ** china

***** **** **** ****** ***

**** *** *** ****** ***** *** **********. ** **** *** store ** ******* *** ****. ** ********* **** **** * DDNS ***** ** *** *** ***.

**** *****, **'* *** ********* ** *** *** *** ****** to *** *** ****** ** ********.

** *** ** *******

**

**** ***** ** ***** *** ** ***

***** ** ***’* ***** ****** ******* *** ******

*** ****** ** ***** ** **** *** ************ ** *********

*** **** **** ****** ** **’* ***** ******* ** ** it *** **** **** *** **

**** *** *** ** ******* ******’* **** **** **** ***** previously

******* **** **** **** *** ****

**** *** ***** ********* *** ******** ** ********** ** **** is

*****

**** ******* '**********' ** ******* *** "********** *** ******** *** means ** *** ********** ** ******** ****.."

**** **** ******* '*********’ ** ******* *** ********* ******** **** on ****** ** *** **********"

**** **** ******* ********** '**********' ** *** *** ****, *** 'processor' ** *********** ** ***** ******* *********. ****** ****** *** not ********.

*** *** ****** ****** *** **** ** ******** ********, *** may ********* '**********' ** *** ****** ***** ******* ****** ***** designed *** ******, ********* "********** *** ******** *** ***** ** processing ** ******** ****..." ***** *** ******* *** ********** ***** services *** ******* ********* **** **********, *** *** **** ********* camera ***** ** * '*********'.

** *** ***** **************, ****** ****** *** **** '**********' *** 'processor'.

* ***** ** ******** *** *** ********, ****** ** ********** references, ** *** *********** ** *** ***** **************.

** *****,

*********** ******. *******, **** ***** *** **** **********, * ***'* think ****** ****** ***** ***** ** **** ***********. ***********"********* *** ******** *** ***** ** ************ ******** ****" ; ***** ************* ********* ** *** **** *** ******* over *** ******** ******** **** ******** ** * ******, **** can't ** **** *********** ** **** ********. ****, **** *********** have * *** ** ************** ***** *** ****. ** ************* like ********* **** ********** **** *********** ** ***** ****** *********-**** camera ** *** **, *** ********** ********** ***** ** *******/********** to ******.

*******, **'* *** **** ************* ****'* ******** ** *** ****. They *** ****** ** **** ********** ** **** ********** **** it ***** ** ***** *********, *** *******. *** *** ************ (or *** ***** ********) **** ********* ** *** ** ** considered *** "**** **********" ** ***** *********' ******** ****.

**** **** *****.

*******,

* ****** ** ************* *** *** ******** **** **** **** 'P2P' ** ***** ********** ********. ***** *** *** **** ***** / ***** ******* *** *** '*****' **** ******* ** *** devices (*.*.,********* ***** ******* (***** / **********) ******). *** *** ** * ************'* ******* **** ** ********* to ***** ******** *** ** ********** ********** **** **. ****'* the *********** ** ****** ** **** ***** *** ****?

**** ** **** *** ****** ***** *******. ** **** ****** their *********. *** *** **** ****** ** ***** *** **** or *** ***-***** *****.

** ****** ** ***/*** ****** *** **** ****** ** ****, how *** *** ** *** *** *** *** ** ** determines *** **********.

*** **** ***** ******** ** **** ****** ** ******* * Chinese ***** ******* ********** **** ***** *****, ** *** *** yet.

*** ********** * ***** ** ********* ***

******* ****** ** ******** *********

***** ******* **** * ***** ***

**** **** ***

**** ** ****

*** ****

**** ** ***** ***** *** ***** ****** ****

***** ** **** * ********* ** **** *****

*** *** ******* *** **** *** **** ** ****?
***** **** **** **** ***** **** *** ***** *** ****** that **** ********* *** ***** ** **** *** ******.

**** '*****' ** **** **** *** *****/*****, *****/***** *** *****.
* *** ** ****** *** ** ************ ***** * *****.

***** *** ****** ******* **************, ****** * **** ******** ** VMS *** ** *** **. **'* ***** *** ****** ******* but *** **** ** **********, ******** * ** *** ****** the ******** *** ***** ***** *** ****.

* *** ** ********** *** ****** **** *** **** ** most ** ***** ********* ** *** ****. *'* **** *** end **** ** ***** ** *** **** ****** :).

** **** **** ******* ***** ***

*****

****** *****

*** ***** * ***** ** ** ** *** *** * dvr **** **** **** ** ********* ********* ** * ************ system

** ***** ****** ** **** ****** *******

***

********** *******

** ******* ** *** ******** ****** ****** *** ******** ** margins **********

**** ********* *** ** ** ****

** * ***

***** **** *** *** ** *** ****** ****

** ***

** ********** ******* ******* - ******* *’** **** ** *** has **** ******** ** ****** (**). *** * **** ** we **** ** ***** **** ******* *********** **** *** *********..

**********:

**** ******* ********** ****** **** *** **** ********* "*** ********* processing *** ******** **** ** ** ********". *******, *** **** makes ** ******* ** ** ********, ******* ******* **** ** applies ** "**** ******** *** *** ** *** *****" (*********** *****, ******* *.) **** ***** *** **** ******** ****** *** ** ** the **, ********** ** ***** ***********. ** ****** *** *****.

"** *** *****" ** *** * *** ******** ** **** means ********** *** **** ******* *********** ********** ** ********.

****** *** *** ******* *********. * ***** ***'** ***** ** the ***** **** *** **** ***** ******** **** ******** *** go ******* *** ** ** **** *****; **** ******* ** whether *** ********** **** ***** **** **** **** ** *** EU. *** *******, ** * ******* ******** ** ***** * was ****** ** ***** *** * ************ ***** ** *****, GDPR *********** ***** ***** ***** ******* *** ********** **** ***** in *** **.

*******, ** ***** **** *** **** ***** ** **** ********** in ***** *********, ** ** *** ******* ** ******* ******* in *** ** *** *** ********* **** **** (** **** as ***** *****) *****. ** *** ***, * ******* ** by ***... * ********** **** ******** ****, ** * ********* you *** **** ** ***** *** **** ** *** ***** at ***********.***

***********, ****** ***. *'** **** **** ************** ********* ** ****:"********* ** ****** **** ** ********: **** *** **** **** GDPR *********** ** ****?"

*******, *** **** ****** ***** ******** ** ******** (** *********) and **** ** **** ******* ** "**** ******** *** *** ** *** *****" ********* *.

******* **** ***** ***** ** ** ******** ******* *** ** isn't ***** *** * ***** **'** **** ** **** *** implementation *** **** *******.

**** ***** ** ** ** *** **** *** (** **********).

********* ******* - *** *** **** ******* *** ********* **** to ** ** **** *********, *** *** *********** *****'* **** to ** ** *** **** ***** **********. *** ********** **** the ***** ******* ******* ** ***** **** ******* *********** *** be *****, **** ** * ******* ****** *** *** **** controller/DPO ** ******* *******.

**** *** * ******** * ************ ***** ** * **** foundation ****** **** *********.

** ********* ****** *** ******* **** **** ******* ****** ******* contact ******* *** ******* *********** ***all the system's intended usage on the signs, as a minimum, and these should be placed at all entry points to the establishment/estate etc. Typically, any signage that currently meets DPA 1998 and best practice guidance would meet GDPR - our experience is that in practice (at least in the UK) many systems fail to provide signage to meet the current requirements let alone GDPR.

** ** ******* ** *** ****** ** **** **** ****** news.

****** *********** ******* *** ****

******** ******* ******* *** ****** *********** ** ****** *** **

******** ** ****** *********** *** *****.

****** ******...

***, *** ** **** ** ******* ** ****'* ******? *** article ********** ***** ************* ********** ******* *** (***** *** ******* ** ***** *** in ****).

* ********* ***** **** ****** *********** ****** ******* *********** ******** but ******** *** *** **** *** **** ****. *** *******, Nest *** * ****** *********** ******* *** ******** ** ** Illinois *** **** **** ******.

****** *** ***** *****. * ********* **** *****. ***** *** Illinois **** ** ** ******* ** * ********** *****'* ************ I ***** ** ***** ** *** *** **** *** **** Facebook's ******** *****. **** * ***'* **** ** ***** *** a ****** *** ****** **** * ******* ******. **** ** a ********** ******* ** *** ***** *** **** ******** ****** that *** ****** ****** ***** ***** ** *** ** ***** and *** **** ** * **** ********* ***** **** ******** compliant ******.

** ***,

*'** **** ***** ** ******* **** ******** *** * ***** of ***-**** ******** ******** ** * ********** ** ****** ** a *** *****. ** *** * *********** ** ** **********-***** integrated ****** ******* *** ***** ****** **** ** **** *** over *** ***** (*** ************ ** ******).

*'** **** *** ****** *********** ********** **** *** *** ************ and *** **** ****** ** ********** ***** ** **. *** what * ***'* ***** ********** ** *** ******** ********** ****** control *** ***** ******* **** ** ******** ** *** **** rules.

** *** **** *** ******* ** *** ******** ******* ** access ******* *** ****** ** ****?

*** ******** ***** ** ***********

*****,

****'* * **** **** ********. ** **** ***** ************, *** GDPR ***** ** ******* ** ****** *******; *******, *** **** of **** ********* *** ****** ******* ******** ***** **** ***** the ******** **** **** *** **** *********, ***** ** ** "information ******** ** ** ********** ** ************ ******* ******". **** of *** ****** ********** ** *** ***** ************ ***** ***** apply ** ****** *******. ****'* * ***** ******* ** * few **** ******:

Data *******: while there's no defined limitations on storage, ******* ****** ** ***** **** **** ****** *** ** ****** *** "longer **** ** ********* *** *** ******** *** ***** *** personal **** *** *********". ** ****** *******, **** ***** **** having ***** ******** ***** ******* *** ****** **** **'* *** kept ****** **** ** ************ ****** *** *** ***** **'* for “****** ********, **********, ** ********** ******** ********”.

Consent *** ************: access control is an industry where processing is based more on consent than video surveillance. In such industries, the GDPR mandates that clear consent be given (******* *), ** **** **** ********* ** ******** ******* **** ** access ******* ******** *** **** ***** ******* ** ***. *** consent **** ** ****-******** ** ****, ** *** ********** ** Article ** **** ** ****** ****** ** ***** ** **** subjects ** *****, ***** ********.

Right ** ** *********/**** ********: same as video surveillance - make sure there are mechanisms for people entered into the access control database to be able to request and remove their data.

********:** *** ***** ************, ******** ** ******** **** **** ** reported ** *********** *** *********** **** ******** **********.

**********:***** ********** *** ********* ********** ********* *, **** *** ******* ** "*** **** ******* *** ***** explicit ******* ** *** ********** ** ***** ******** **** *** one ** **** ********* ********". **** ***** ********** ***** ** allowed *** ****** ******* ********, *** **** ** ******** ******* is *****, *********** *** ********* *** ***** ** ******* ** here.

*****:***** **'* ***** ***** **** ***** *** ******** *** *****-***** video ********** ** ********-********** ******, **'* *** ***** *** ** it's ******** ** ****** *******. ** ***** ** ******** ** the ****** ******* **** ** ***** ********* ****:******* ******** **** ***** *** ******** ** ***** ** "********** ** a ***** ***** ** ******* ********** ** **** [*.*. **********]". However, ******* *** **** *****'* ****** "***** *****" ** **** yet ** *** *** ** ********* **** ***** ***** **** requirements ** ******** *** ******* **** ***** ***** ** ****** control ** ***.

***** ** * *** ** **** *** ** ****** ******* requirements. *** ******* ***** *** ***** ***** *** *** ** physical ****** ******* ** ******* ******** *** *********** ******** ******* special *************, ** ** **** ****** ** ******* ******* **** the ******** ******** ************** ********. ***** ***** *** **** ******, as *** **** ********* ****, ******* ******* *******.

**** ** *** ******** ******** **** *** ***:

*** ********** ** ******** **** ** *** ****** ******** ********* and ************* *** *** ******** ** ******** ******* *** *********** security, *.*. *** ******* ** * ******* ** ** *********** system ** ******, ** * ***** ***** ** **********, ********** events ** ******** ** ********* ******* **** ********** *** ************, authenticity, ********* *** *************** ** ****** ** *********** ******** ****, and *** ******** ** *** ******* ******** ******* **, ** accessible ***, ***** ******** *** *******, ** ****** ***********, ** computer ********* ******** ***** (*****), ******** ******** ******** ******** ***** (CSIRTs), ** ********* ** ********** ************** ******** *** ******** *** by ********* ** ******** ************ *** ********, *********** * ********** interest ** *** **** ********** *********. **** *****, *** *******, include ********** ************ ****** ** ********** ************** ******** *** ********* code ************ *** ******** ‘****** ** *******’ ******* *** ****** to ******** *** ********** ************* *******.

*****-*** *** **** ***** *********

**** *******, *** *** * ******* ************ ** ** ****** place **** "***********"...

** ** *****, **** **** *** **** **** *** ***'* have ** ****** ** **** ** *** ***'* **********, ** that ***** **** ***'* *****. * *** ****** ******** *** that ******** ******** *** **** ********* *** *****. *** **** here ** ** ******* ** ********** *** *******. *** **** would ** **** *** *** ****** ****** ********* ** ***** justifications *** **********. *** ** **** ** ***** ***** ******* kicks **, ** ****** ** ******** ******. ***** ******* ******* as **** *** ******* ** *** *** ** ***** ***** are ******** ******** **** ** *** *** ********** *****.

*******,

*****-*** **** ****, **** ** **** ***********.

** ***** ** ***, *** ******* ******** ** **** ************ and ******* ********** ** * **** *** ****, ***** **** most ** *** ******* ****** **********. ************* ******* ** ****** is ******** *** ******** *** *****. *** **** **** **** are **** ************* ** ********* ******** *****.

**** ** *** **** ******** ***** *****. ** **** ****, as ** *** **** **** *** *** **** *********; **** are **** *** **** ********** *** **** ** ****** *** purpose *** **** * ****** ** ******* ****. ***** *** also * ****** ** ***** ****** **** **** ** **** place ********* ** *** ******* ********. *** **** ********* ***** to ********, *** ******* ** *** ** (***** ** ***** part ** *** **) **** ***** ***(**** ** ******** *** * *** *********** ** **** **** to *** **** ********** *** ** ****). *** *********** **** should *****, ** *** *******, **** *** *********** ** ***** ********* ******* *** *********** *** *** ******* ** ********.

**** ****** **** * ******** ********* *** **** ** **** privacy ******, ** ***** ** **** ** ****** ******* (*** seem **** ** ******** *** ** ** **** * **** important *******) *** ****, *****, ********* ** ******* *** **** a ****** ** ***** *********** ****** ******, **** (**** *******) control *** ***** *****. ***** ****** ** * ******* *** increasingly ********* *****.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

Last Chance - April 2018 IP Networking Course on Apr 19, 2018
Today is the last day to register for our IP Networking course. Register now. NEW - 2 sessions per class, 'day' and 'night' to give you double...
Rare Video Surveillance Fundraising - Verkada $15 Million on Apr 19, 2018
Fundraising in video surveillance (and the broader physical security market) has been poor recently. Highlights are few and far in between...
Security Camera Cleaning Frequency Statistics on Apr 18, 2018
150+ integrators told IPVM how often they clean cameras on customer's sites and why.  Inside we examine their answers and break down feedback...
Worst Access Control 2018 on Apr 18, 2018
Three access control providers stood out as providing the most problems for integrators. In this report, we analyze the answers to: "In the...
Key Control For Access Control Tutorial on Apr 16, 2018
End users spend thousands on advanced systems to keep themselves secure, but regularly neglect one of the lest expensive yet most important aspects...
Best and Worst ISC West 2018 on Apr 16, 2018
ISC West 2018 had strong attendance, modest overall new products, and a surge in Artificial Intelligence marketing. First, here are 20+...
Alarm.com Business Market Expansion on Apr 13, 2018
Alarm.com has millions of subscribers, but the company has traditionally been mostly a residential/home focused offering.  ADC's new Smart Business...
Axis Launches ~$100 HD Camera on Apr 11, 2018
Chinese manufacturers, led by Hikvision, have come to dominate the low end of the Western market, driven by ~$100 cameras. While Axis has...
Eocortex / Macroscop VMS Company Profile on Apr 09, 2018
Eocortex is the international brand of Russian VMS manufacturer Macroscop. Macroscop was founded in 2008, and the Eocortex name created in 2013. We...

Most Recent Industry Reports

Global Real-Time Video Surveillance - EarthNow on Apr 20, 2018
A new company, EarthNow, with backing from Bill Gates, Airbus and more, is claiming that: Users will be able to see places on Earth with a delay...
Dedicated Vs Converged Access Control Networks (Statistics) on Apr 20, 2018
Running one's access control system on a converged network, with one's computers and phones, can save money. On the other hand, hand, doing so can...
April 2018 IP Networking Course on Apr 19, 2018
This is the last chance to register for our IP Networking course. Register now. NEW - 2 sessions per class, 'day' and 'night' to give you double...
Rare Video Surveillance Fundraising - Verkada $15 Million on Apr 19, 2018
Fundraising in video surveillance (and the broader physical security market) has been poor recently. Highlights are few and far in between...
'Best In Show' Fails on Apr 19, 2018
ISC West's "Best In Show" has failed. For more than a decade, it has become increasingly irrelevant as the selections exhibit a cartoon level...
Security Camera Cleaning Frequency Statistics on Apr 18, 2018
150+ integrators told IPVM how often they clean cameras on customer's sites and why.  Inside we examine their answers and break down feedback...
Worst Access Control 2018 on Apr 18, 2018
Three access control providers stood out as providing the most problems for integrators. In this report, we analyze the answers to: "In the...
Axis VMD4 Analytics Tested on Apr 17, 2018
Axis is now on its 4th generation of video motion detection (VMD), which Axis calls "a free video analytics application." In this generation, Axis...
Arecont CEO And President Resign on Apr 17, 2018
This is good news for Arecont. Arecont's problems have been well known for years (e.g., most recently Worst Camera Manufacturers 2018 and starting...
Strong ISC West 2018, Says Manufacturers, GSX / ASIS Expected Weaker on Apr 17, 2018
Manufacturers say ISC West 2018 was strong, continuing the trend we have seen in 2017 results and 2016 results. However, those same 100...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact