GDPR For Access Control Guide

Author: IPVM Team, Published on Jul 03, 2018

Electronic access control is common in businesses plus organizations are increasingly considering biometrics for access control. With GDPR coming into force this Spring, it is important to understand how this will impact these systems.

IPVM has already published an extensive guide about the GDPR’s effect on video surveillance. This new 13-page guide covers GDPR’s effect on the access control industry since much of the data collected for access control purposes – e.g., names, addresses, fingerprints – are personal data whose processing is clearly regulated by the GDPR.

The guide has the following core sections:

  • Where Access Control Providers Fit into GDPR categories of controllers and processors
  • Why Processors Aim To Keep Distance
  • Legal Basis for Processing Access Control
  • Impact of Biometrics on Access Control GDPR Requirements
  • Dealing With Employees Who Refuse Biometrics Consent
  • Access Control Systems Excluded From Biometrics Claim
  • Guidelines for Storing Access Control data
  • Handling Right to be forgotten/Right to information requests for access control systems
  • Encrypting / Anonymizing access control information
  • Concerns with AD / LDAP integrations
  • Data breach response for access control
  • Data Protection Impact Assessments for access control systems
  • Dealing with Data Specific to Access Control, e.g. Physical Activity Log
  • Manufacturer GDPR guides including Avigilon, Brivo, Genetec, Lenel, Paxton, RS2, S2, Tyco

Introduction

To start, it’s important to realize that the GDPR is a broad set of regulations which do not mention particular industries, including access control or its products.

Therefore, anyone claiming to provide “GDPR certification” for particular products in access control or any other industry is wrong. (See IPVM’s previous report: Dahua Products Are Not GDPR Compliant, No Products Can Be.)

Data Controller and Data Processors

The GDPR creates two distinct categories – data controllers and data processors. Controllers are the firms which gather and control the use of peoples’ personal data, and processors are the ones who process that data on behalf of controllers.

The distinction is important as data controllers typically have more responsibilities under the GDPR; for example, only controllers have a duty to report data breaches to authorities.

Access Control GDPR Category Examples

As in video surveillance, access control end users would typically be considered “data controllers.” For example, if a pharmaceutical company buys an access control system for a new building and its employees, the pharma company is the data controller.

Data processors are the companies which handle the personal data collected by end users. For access control, in most cases this means firms like Genetec, Lenel, Software House, S2 Security, etc..

Access control integrators/installers could also be considered data processors depending on whether they handle their end users’ personal data or not. For example, an integrator with temporary access to employees’ personal addresses for maintenance purposes would be considered a data processor in this instance.

Processors Keep Distance

Many data processors in the access control industry emphasize that they can only provide the means to comply with the GDPR’s provisions, rather than assuring compliance in and of themselves.

Because access control involves data which is very easy to immediately identify people with (unlike video surveillance), processors are keen to distance themselves from end users/data controllers in case those end users mishandle the data.

For example, S2 Security says in its public GDPR guide that it may not be considered a data processor in some cases because “on-premises deployments of access monitoring and video management systems often do not involve a Data Processor because the Data Controller handles all personal data.” S2 is correct when it comes to on-premise deployments.

However, it is worth remembering that firms providing cloud-connected access control solutions would be considered data processors under the GDPR. Moreover, as more systems are moving to the cloud, either for hosting, management or access, access control providers are more likely to fall under the data processor category.

Main Points of Compliance for Access Control

Legal Basis of Processing

********** ****** ******* ** ****** ** ********** **** ************* *** increasingly *********** ********** *** ****** *******. **** **** ****** **** force **** ******, ** ** ********* ** ********** *** **** will ****** ***** *******.

**** *** ******* ********* *********** ***** ***** *** ****’* ****** ** ***** ************. **** *** **-**** ***** ****** ****’* ****** ** *** access ******* ******** ***** **** ** *** **** ********* *** access ******* ******** – *.*., *****, *********, ************ – *** personal **** ***** ********** ** ******* ********* ** *** ****.

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

  • ***** ****** ******* ********* *** **** **** ********** ** *********** and **********
  • *** ********** *** ** **** ********
  • ***** ***** *** ********** ****** *******
  • ****** ** ********** ** ****** ******* **** ************
  • ******* **** ********* *** ****** ********** *******
  • ****** ******* ******* ******** **** ********** *****
  • ********** *** ******* ****** ******* ****
  • ******** ***** ** ** *********/***** ** *********** ******** *** ****** control *******
  • ********** / *********** ****** ******* ***********
  • ******** **** ** / **** ************
  • **** ****** ******** *** ****** *******
  • **** ********** ****** *********** *** ****** ******* *******
  • ******* **** **** ******** ** ****** *******, *.*. ******** ******** Log
  • ************ **** ****** ********* ********, *****, *******, *****, ******, ***, S2, ****

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

** *****, **’* ********* ** ******* **** *** **** ** a ***** *** ** *********** ***** ** *** ******* ********** industries, ********* ****** ******* ** *** ********.

*********, ****** ******** ** ******* “**** *************” *** ********** ******** in ****** ******* ** *** ***** ******** ** *****. (*** IPVM’s ******** ******:***** ******** *** *** **** *********, ** ******** *** **.)

Data ********** *** **** **********

*** **** ********** ******** **********– **** *********** *** **** **********. *********** *** *** ***** which ****** *** ******* *** *** ** *******’ ******** ****, and ********** *** *** **** *** ******* **** **** ** behalf ** ***********.

*** *********** ** ********* ** **** *********** ********* **** **** responsibilities ***** *** ****; *** *******, **** *************** * ****** ****** **** ******** ** ***********.

Access ******* **** ******** ********

** ** ***** ************, ****** ******* *** ***** ***** ********* be ********** “**** ***********.” *** *******, ** * ************** ******* buys ** ****** ******* ****** *** * *** ******** *** its *********, *** ****** ******* ** *** **** **********.

**** ********** *** *** ********* ***** ****** *** ******** **** collected ** *** *****. *** ****** *******, ** **** ***** this ***** ***** **** *******, *****, ******** *****, ** ********, etc..

****** ******* ***********/********** ***** **** ** ********** **** ********** ********* on ******* **** ****** ***** *** *****’ ******** **** ** not. *** *******, ** ********** **** ********* ****** ** *********’ personal ********* *** *********** ******** ***** ** ********** * **** processor ** **** ********.

Processors **** ********

**** **** ********** ** *** ****** ******* ******** ********* **** they *** **** ******* *** ***** ** ****** **** *** GDPR’s **********, ****** **** ******** ********** ** *** ** **********.

******* ****** ******* ******** **** ***** ** **** **** ** immediately ******** ****** **** (****** ***** ************), ********** *** **** to ******** ********** **** *** *****/**** *********** ** **** ***** end ***** ********* *** ****.

*** *******, ** ******** **** ***** ****** **** ********* ** *** *** ** ********** * **** ********* ** some ***** ******* “**-******** *********** ** ****** ********** *** ***** management ******* ***** ** *** ******* * **** ********* ******* the **** ********** ******* *** ******** ****.”** ** ******* **** ** ***** ** **-******* ***********.

*******, ** ** ***** *********** **** ***** ********* *****-********* ****** control ********* ***** ** ********** **** ********** ***** *** ****. Moreover, ** **** ******* *** ****** ** *** *****, ****** for *******, ********** ** ******, ****** ******* ********* *** **** likely ** **** ***** *** **** ********* ********.

Main ****** ** ********** *** ****** *******

Legal ***** ** **********

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

*** ****’******** ******* ******* ***** ***** *** **** **********, ** ***** *** of *** ********* ***** ** ****** *******:

  • *** **** ******* *** ************** *** ********** ** *** ** *** ******** **** *** one ** **** ******** ********
  • ********** **necessary *** *** *********** ** * ********** ***** *** **** ******* ** *****
  • ********** ** ********* *** *** *********** ** * **** ******* outin *** ****** ********** ** *** ******** ** ******** ********* ****** ** *** controller
  • ********** ** ********* *** ***purposes ** *** ********** ********* ******* ** *** ********** ** ** * ***** *****, ****** ***** **** ********* *** ********** ** *** ********* or *********** ****** *** ******** ** *** **** ******* ***** require ********** ** ******** ****, ** ********** ***** *** **** subject ** * *****.

Biometrics *** *******

********** (************, **** *****, ****** ***********, ***) *** ** **** that **** ****** **** ****** ******* ***** ******* ** ****** with *** ****’* ********* ******* ************.

********** ********* ** ********** ***** *** **** **** ******* **********. The **** **** ***** ***** ** ****** ******* *** “*********** public ********” *** “******** *******.”(******* *).

*********, ****** ** ****** ******* **** *** *********** ***** ********** gathering *** * “*********** ****** ********,” ** ***** **** ** make *****, ******-*****, *** ******** ******* * ********. **** *****:

  • ******* ***** **** ** ********* * *******, ***********, ************ *** ****** ********** ****, ***** clear *** ***** ********(******* *)
  • **** ******** *** ******* *** ***“******** *** ** *** ******* ** *** ****” **** ****(******* *)
  • ** ****** ********* *, *** ******* ***** **** ******* **** **** ** ********** are ***** **** *** ***
  • ******* **** ** “****** *****”, *.*. “******* ****** *** ** ******** ** ****** ***** ** *** data ******* *** ** ******* ** **** ****** ** ** unable ** ****** ** ******** ******* ******* *********.” (******* **.)

**** ***** ** * ********** **** ** ********** ****** ******* for *** ********* ***** ******** **** *****, ** ***** ** obtain ********, *****, *** ******-***** ******* **** ****.

Refusing ******* *** **********

************* *** **** * ******* **** ********* ** ****** ** their *********-***** ****** ******* ****** ********* ********:

******* ****** *** ** ******** ** ****** ***** ** *** data ******* *** ** ******* ** **** ****** ** ** unable ** ****** **withdraw ******* ******* *********. [emphasis added]

** **** ***, ** ** ******** **** ** ************ *** fire ** ****** ***** *** ** *** **** ******* *** their ********* *********** ** ** ****. ** *********** *** ******* non-biometric ***** ****** ******* *** ***** *** **** *******.

**** *****, ** **** ** ** ***** *** ********** **** and ** **** ****** ******* ******* *********** **** ******** *** clear ******** ** **** ***********. *******, ************* ****** ********* ******** the ************ ** ******* ** **** ***** ********** *** ****** control.

Access ******* ******* ******** **** **********?

**** ****** ******* ****** ********* ******* **** ***** ******* ** not **** ***** **** ******* ******* **** **** ***** **** that ****** ** **** ** ******** ****** – ****** ******* a **** ***** ** * **** ** ***********, *** *******. This *** ** ****** ** * **** ** *************.*** **** ***** ********* ************, *** **** ********* *** ****** by *** ****** ** ******** ** *** ****** ******* ****** entirely, *** *** **** **** ******** ** *** ****** ****** is * ******* ** **** **** ****** *********** * **********.******, **** ********* ******* (**** ***** **** ** ‘************’ *****) may *** ***** ********* **** ** *** ****** ****** ** all, *** ****** ********* *** **** *** ****** ** ********** cards ** ****** ******-***** *********.

**** ** * ***** *** ******** ******** ** *** **** itself **** *** **** *** ********** ** **** ** ********* to ** ********* ****, ** **** ** ** ** “********* data *** *** ******* ** ******** *********** * ******* ******” (******* *) - ******* **’* ********** ** ***.

****** ******* ********* ****** *** ** *** **** ** ******* when ******* **** *** ********** ***** *** “******* ******** ** personal ****” ****** ** *** ****. ** *** **** * GDPR *********/******* ** ***** ******* ******* ****** **** **** **** strings *** ********** ********** ***** *** **** ** ***.

Storage ****** ******* ***********

*** **** *** ** ******* ********** ** *******, ********** ****** ** ***** **** ******** **** ****** *** ** ****** for "****** **** ** ********* *** *** ******** *** ***** the ******** **** *** *********".

** ****** *******, **** ***** **** ****** ***** ******** ***** storage *** ****** **** **'* *** **** ****** **** ** indefinitely ****** *** *** ***** **'* *** “****** ********, **********, or ********** ******** ********”. **** ***** ********* *** ***** * firm ****** **** ***** **** ******* ********.

**** ******* ** *** ********** ************ ***********, **** ** ****** logs ********* **** * ******** ****** **** ******* * **********. However, ** **** ****** **** ** *** **** ** * specific ******, ** ***** ****** *** **** ***** *** **** and **** ** ******** ******* **********. (*** **** ** ****, see***** ** **** ******** ** ****** *******.” *****)

Right ** ** *********/***** ** *********** ********

*** **** ***** ***** ****** *** ****** ** ****** *** delete ***** ******** **** ********** *******, ** ****** ******* ***** **** ** **** *********** ********** to ******* ***** ******** *** *** ***** **** ** ***** of *** ** *** ****.

***** *** **** ******** ** ****** ******** **** ******* **** justifications **** ****** ********* *** ****, *** **** ******* ** least *** ***********, **** ******* *** **** ** “** ****** necessary ** ******** ** *** ******** *** ***** **** **** collected” (******* **.)

*** ****** ******* **** **** **** **** **** ********** **** how ** ********* *** ****’* ****** *** ******** ************. ** would ********* **** ****** *** ***** *** ***** ****** ***** access ******* ******** ** ***** **** ******** ** *******, ****, and ****** ***** *** ****. *** *******, ******** **** **** company ****’* ******** ********** **** ****** ********** ********* ******** ***** “****** **” ********.

*** ****** ******* *******, **** ********* ** ****** ***** *** deletion ** *** **** *********** *** ********, ******** *** ***** needed ** ** **** *** ***** ****** ****** ‘**** *******’ functions ****** ********* *** ***** ** ********** *******.

*** ****** ** ‘*********** *******’ *** ******* ** * ****** may ******* * ***** ****, *************, ** ******* ********** ****** simple ******** ** ****** *******, *** ** ***** ******* *** shared **** ***** ***********, **** ** ‘**** & **********’ ** ‘Visitor **********’****, **** ******** ****** ******** *** ******* *********** **** multiple *******.

***** ********* **** *** ***** ** ** ********* *** *** right ** ***** ******** ****. *** **** ******* ** **** the **** ******** *** ****, *** *** **** *******’* ********** status. *******, **** ***** *** ** ******** ** *** ********’* personal **** *** **** ******* ********* *** ** *** ********* from * **** – ** ****** ** **** ** ********** with *** ****’* ******* *************** (*** “*******.”)

*******, **** ** **** **** ***** ***** ** **** ** respond ** *********** ********, **** **** * ***** ** ** so, ***** *** ** ******** ** ********** * ******. **** also ** *** **** ** ******* **** ** **** *** “manifestly ********* ** *********.” (******* **.)

Encryption *** *************

******* ****** ******* ********* ****** *********** ******* ** ********* *** special ******** ****, ****** ********** ** ***. *** **** ********** encourages ****** ********** ********* **** ****** *******’ ******** **** ** *********, ** **’* ****** important *** ****** ******* ********* *** ***** ** **** **** they *** ******** ***** ********* *** ******** ****-**** ********* **** General ****** **** **.******* **** ********** ***** ***-****** **************, ********* ***** ********, ** default *********, ***.

*******, **** ****** ******* ******* ******* ************ **** ********* ****** Directory ** **** ** ******** ***** *********, *** ***** ******* utilities *** *** ** ******* ** **********. ** *****, ****** control *******, ********** ***** **** ** ***** ********** *** *****-******** deployments **** *****, ******** *****, *******, **, *** ******** *** may ** ** ****.

*************/**************** ** **** ********** ** *** ****. ***** ***** **********, which ****** ****** **** ***’* ** *********** **** ** ****** people, ** ****** ** ** ******* ********* ************ ** **** of * ******. *** *******,******* *********** **** ********** **** ******** *** *** **** ** ** contacted ** *********** ************* ********** *** ****.

****** ******* ********* ***** *********/**** *********** **** ** ****** *** impact ** * ******, *** ********. ***** *** **** ** anonymized ** ********* **** ****** * ****** *** ******* ** referring ** **** ******** ** ***** **** ****.

Data ******** – ********** ***** *** ******* ******

****** **** ** ****** *******, *** ***** *** **** ****** to ** ********** **** ***********, ***** ****** ****** ******* ***** like ******* *** **** ****** ** ** ********** **** **********.

***** *** ****, *********** **** ** ***** ** ****** *********** in *** **** ** * ******. *********** **** *********** **** inform ********** **** ******** ** **** ** **** *** ****** poses* **** **** ** *** ****** *** ******** ** ******* persons”(******** **&**.)

**** *********** **** ****** ** * *** ************ ************* **** either ********** ** ****** **** *** ***** ** *******. ************* of **** ******** *** *** ********, ********, ** ****** ********** with ******* *************, *** **** **** ********* ********* *** ******* breach ************ ************.

****** ******* ********* ***** ********** ****** **** *** ******* ********* to ****** ********* ************, ** *** **’* ******* ** ******* Party, ** ******** ** ******** ****,*** ********* ****** ********* ********** ** ************ **** ****, **** ********* ************ of ********** **** ******** ***** **** ***********: “** ******* ********** ** ******** **** [**********] *** ********* ******, the ********** ****** *** ******* ***** ***** ** ******* *** breach *** ** *********** ** ** *** *********** *********.”

**** ********** **** **** ************** ** *** ***** **** **** are **** ******* ** ******* **** ***********, ****** **** *********** and **** ********, ****** ** ***** ** ******* ** * breach ***** ********* ******** **** **** ***********.

Data ********** ********

***** ** ** *** ********* *** *** ****** ******* ***** to ******* * *** (******* ****** **** ********** **** **********), an ****** ******* **** ***** ********** *** **** ** ** so.

*** **** **** *** * ********* ********* ****** **** **** ** ** *********, ********* **** “*** **** ********** ** *** ********** ** *** ********* ******* of ********** ** * ***** ***** ** ******* ********** ** data [**** ******** **********]”.

***** **** ****** ******* *********’ ********** *** ** ********* ***********, appointing * *** ***** ** ****. **** **** *** ** especially **********, ** *** **** ****** **** * *** *** be ********** ** ** ** ******** ******** ****** **** *** more ****.

Data ********** ****** ***********

******* ******** **** ***** *** ******** ** ***** “****** ** ****** ** * **** **** ** *** ****** and ******** ** ******* *******”, ********** **** "********** ** * ***** ***** ** ******* categories ** **** [*.*. **********]" ***** *****.

*******, ***** **** *** **** *****’* ****** “***** *****” *** that ********** ***** ** ******* ** “********** ********” – **** access ******* – ** *** ****** ** ****** ** * risk ** ******’* ********, ** ***** ******** ***** ***** ** required ** ***** ******** ** ****** *******.

******* ** ***** **** *** ** *** *** ** ********* will ***** ***** **** ************ ** ********, **** ***** ******. So *** **** *** **** ** ******** ** ****** ******* firms ********* *** ********* *****.

Data ******** ** ****** *******, *.*. ******** ******** ***

*** **** ********* ******** ****, ** "*********** ******** ** ** identified ** ************ ******* ******". (******* *). *******, ***** *** ***** ** **** ** ****** ******* which **** ***** * **** ****, ************ *** **** ** physical ******** **** ****** ***** **** ******* **** * ********* to ***** * ********, *** *******.

****** ******* ***** ********* ** **** **** **** *** *** consider **** **** ** **** ** ** ******** ** ********* data, ***** ** *** ***** ************* ** * ******** ****** and ***** *** ** **** ** ******** *******. **** ***, if *** ******* ** ******** ****** * *******, *** **** controller ***** ****** *** ******** *********** *** **** *** *********** anonymous ******** *** (** ** ******* *** ******** *** **** firms).

***** *** ********** ** ******** **** ***** ** *** ****, this ******** ***** *****. *******, ** ******* *** **** ********* realize **** *** **** **** ******* ***** *** ** **** to ******** * ******** ****** ***** ***** *** ****** ******* of *** ****.

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

**** ****** ******* ******** ********* **** ********* **** **********, ****** generally **** *** ***** ** *** ********* ** ****'* ****** on ****** ******* *******. ***** *** ***** ** ****** **** ********** ** ****** ******* *****, **** relevant **** **********:

******** **** *********:******** ********** (**** ** ******** ******* ****** (***) ***** ********** software) ****** ****** ** **** *********, *** ********** ********* **** consider *** ***** ******** *** ********* *** ****** *********** ** deploying *** ********* * **** ********* ******. ******** *** ***** care ** ****** **** *** ***** ******** ********* ******* ******** and ************* **** **** ******* **** **********.”

**** *******: ******** ********* ****** **** *** **** ** ** provide *** ***** ** **** ********** ****** **** *** ********** itself.

***** **** *********:“*********** **** **** ****** ** ***** ***** ** *********** ***** Brivo ************ *** ********** **** ********. ***** ***-***** *** ** some ***** ***** ********* *** ********** **** ***********. ***** ** a **** *********.”

**** *******: **** *** **** *********** ** *** **** ***** ******* ** ****** control. **** **** ***** ** *** *********, ***** ********* ** has ********* * *** *** ***** ** ***** ** ******* them **** **** *******.

******* ****** **** *****:“**** ******* *** ***** ************ *** ********* ***** ** ********* who ****** **** ******** **** ****** ***. ****** **** *** data *** ******* ** ********* ******* ************ ****** ** *** first **** ** ********* *** ****. *** ********* ******* *** the ***** *** **** ** ****** **** *** *** ******** and ****** ** *** ******** ******* ** ***** *******.”

“**** ****, *********** *** *** ******* ****** ** * **** of *** **** ** ************ *** ********* ***** ****. ********** *********™ ******* ******** ********** ******** ***** **** *** *** ***** to ******* ** ***** ********. ** ******** * ****** ***-***** portal ***** *** *** ****** *** *********** ***** ******* ****. It **** *** ******* *********** ****** ** ***** ******** *********** in * ********** *** ****** ******.”

**** *******: * ******** ** *******’* ***** ** *** ******* video ************ ****** **** ****** ******* *********, ******* ** ******** identifies *** ********** ** ****** ************* ********* *** ******** ******** to **** **** ********** ******.

***** **** *****: “***** *** ******** *** ******** ** ***** ********* ** *** them ** ****-********* ****. ***** ******* ****** ******* ****** ** security ** ******* *** ******** **** ** ********* *** ********. Respected ******** ********* *** ***-********* ********** ******* *** ** ********** in *** ***** ******* ****** **** ** ******* ******* **** and ******, **** ******* ****** *** **********, ****.* ******* ********** and ******, *** ***** *** * ****** ******** **********. ********, Lenel ******* ******** ************* ****** ************ ** ***** ****** ** authorised ********* *** ******** *** *********** ** ******* **** ******, to **** ***** ** ********* ******** *** *** ****** ** function.”

**** *******: *****'* ***** *** *** ** *** **** ******** and ******** ***** ****'* ****** ** ****** *******.

****** **** *********: “** **** **** **** **** *** ******** **** ******* *** tools ******** ** ***** ********** ** **** *********, *******, ****** is *** *********** *** * ****’* ********** **** **** *** do *** ***** ****** ** *** ** ** *********.”

**** *******: ****** **** ********* ***** **** ***** ** *** give *** ***** ** ****** **** ****, *** ******** ****** automatically ****** **.

*** **** *********: “** *** **** ** ****** ** ***** *** ***** ******** Data ** **** ***** ***, ** ** ******* **** ** delete *** *********** ***** ***, *** *** ******* ** ** emailing ***@***.***. ** **** *********** **** ******* ****** *******-*** (**) hours *** ****** ** ********. *** ******** *.*.*. **** ******* to ***** ******** ****** * *****, **** * *********** ** extend **** ****** *** ************ ******* ******** ** ********** **** Applicable ***. ** **** ****** **** *********** *** ** **** as **** ******* ** ******, ** ****** ** ******* *** services, ** ** ****** **** *** ***** ***********, ******* ******** and ******* *** **********.”

**** *******: **’* *** ******** ********* *** *********** ** ********** to ******* ** ***** ******** ****** ** *****, ***** ** the **** ******** ** ****** ********. *** **** ***** *********** and ********** ** ** * ****** ** ******* ** ***** requests.

** **** *****: “*** ******** ********** ****** ***** ** *** **** **********, *** entity **** ******* ***** ******** **** ** ******* *** *** the ******** ************** *** ************ **.”

“********* **** ****** ***** ********* ******** **** *** ******* ****** issues. ****** *** ***** ****** ** ******** **** *** **** for ******** **********. ****** **** *********** *** *** ******** ****** of **** *********. ***, ******* **** ***********, ** *********** ***** your ******** **** *********.”

**** *******: ***** *** *** ******* ********** *** ********* *** heavier ********** ****** *** ****** ******* *** *****/***********.

*** / **** ************ ******* *** ******** ***** ***** *** same **** ****** (*.*.*****) *** ***** ****** ******* ***** ****** ***** ** ** for ***** ************:“** ** ********* ** **** **** ******* ***/** ******* ********* are *** ** ********** **** *********. *** ******* **** ** subject ** *** **** **** **** ** ****** **** ******** and ********** *** ******** ** ****** **** ***** **************** ***** the **********, *** ** *******, ********* *** *** ******** ***/** product ********* ** * ****** **** ** *********.”

“******* ********’ ***** ******* ********* ******** * ****** ** ******** and ********* **** *** **** **** ******* ** **** ********** ************ *** ************ *** ******** *** ********** ** **** processed. **** ******** *** ******* **********, ****-***** ****** ******* ** limit ***** ***** *** ****** ****, *** **** ** ***** provide ***** ****** *** **** ****** *** *********. *******, ********** with *** **** *** **** ** ******** ******* ********** ******* and ******** ******** ******* ************ ** **** *** *********** ***** of **** ********** ********. *********, **** ********** ****** ** ****** by * *******’* ******* ***. ***** *** *******’* ******* *** can **** **** ********** ****** ** *******, ***** **** ********** be ********** ******** *** ******** ******** ******* ******** ** ****** compliance **** *** ****. **** ******* **** **** ******* ************ about ***** **** ** ******, **** *********** ** ****** *** user ******* ************ **** ******* ******** ****** *******.”

**** *******: **** ******* *** ******** *****, **** ***** ** Johnson ********, ***** *** ******* ******* ** ****** ******* ***** distancing ********** **** *** ***** **** ** ***** ** **** compliance, ****** **** ******* ******** ***** ****** ****** **********.

Future *******

**** **** ******* ******* ******* ** *** **** ******* ****** control *********** ****** *** ** ***** ********* **** *** ****** control *** *******.

Comments (0)

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

Backboxes for Video Surveillance Tutorial on Aug 15, 2018
Backboxes are a necessity in surveillance, whether for managing cable whips, recessing cameras, adding wireless radios. But it can be confusing to...
SimpliSafe Violating California, Florida, and Texas Licensing Laws on Aug 14, 2018
IPVM has verified that DIY security system provider SimpliSafe, founded in 2006 and acquired in June of 2018 at a billion dollar valuation, is...
Cut Milestone Licensing Costs 80% By Using Hikvision and Dahua NVRs (Tested) on Aug 13, 2018
Enterprise VMS licensing can be quite expensive, with $200 or more per channel common, meaning a 100 camera system can cost $20,000 in VMS...
Nortek Sues SDS, Battle Over Unpaid Bill and Cancelled Lines on Aug 13, 2018
Nortek and SDS legal battle continues. As IPVM reported, SDS sued Nortek alleging bribery and antitrust violation. However, Wave fired back at SDS,...
Axis / Avigilon Legal Battle Rises on Aug 09, 2018
In what is shaping up to be high-powered, will-not-back-down battle, Axis and Avigilon are squaring off in multiple legal contests. In 2017, IPVM...
Camera Focusing Tutorial on Aug 09, 2018
A camera's focus is fundamental to quality imaging. Mistakes can cause important problems. In this guide, we explain focus issues and proper...
Hikvision PanoVu Mini Tested (Multi-imager + PTZ For ~$500) on Aug 07, 2018
Hikvision has released their first PanoVu Mini multi imager, the PanoVu DS-2PT3326IZ-DE3, with four 1080p imagers, including a PTZ and integrated...
Struggling Ascent Hiding Under Brinks on Aug 07, 2018
The market cap of Brinks Home Security, Monitronics, MONI, Ascent Capital Group (whatever one calls them) is down 96% over the past 5 years as the...
RealNetworks Free School Facial Recognition on Aug 03, 2018
The company that created RealPlayer is moving beyond media delivery and into the security space with a new facial recognition platform they have...
Camera Cable Whip Guide on Aug 03, 2018
Cable whips are one of integrator's least favorite camera features but seem to be unavoidable, now commonplace on dome, turret, and bullet cameras...

Most Recent Industry Reports

Chinese OEM Avycon Gets ADI Push on Aug 15, 2018
Who is Avycon? An American company? A Korean company? A couple of guys relabelling Chinese products? The latter is the best explanation. While...
Backboxes for Video Surveillance Tutorial on Aug 15, 2018
Backboxes are a necessity in surveillance, whether for managing cable whips, recessing cameras, adding wireless radios. But it can be confusing to...
Genetec Stratocast / Comcast 'Motion Insights' Examined on Aug 15, 2018
Comcast recently announced "SmartOffice Motion Insights", an extension to their Genetec OEMed cloud video service (covered by IPVM here). This...
SimpliSafe Violating California, Florida, and Texas Licensing Laws on Aug 14, 2018
IPVM has verified that DIY security system provider SimpliSafe, founded in 2006 and acquired in June of 2018 at a billion dollar valuation, is...
Ban of Dahua and Hikvision Is Now US Gov Law on Aug 13, 2018
The US President has signed the 2019 NDAA into law, banning the use of Dahua and Hikvision (and their OEMs) for the US government, for US...
Cut Milestone Licensing Costs 80% By Using Hikvision and Dahua NVRs (Tested) on Aug 13, 2018
Enterprise VMS licensing can be quite expensive, with $200 or more per channel common, meaning a 100 camera system can cost $20,000 in VMS...
Nortek Sues SDS, Battle Over Unpaid Bill and Cancelled Lines on Aug 13, 2018
Nortek and SDS legal battle continues. As IPVM reported, SDS sued Nortek alleging bribery and antitrust violation. However, Wave fired back at SDS,...
Uniview Intrusion Analytics and VMD Tested on Aug 13, 2018
IPVM's IP Camera Analytics Shootout featuring Avigilon, Axis, Bosch, Dahua, Hanwha, Hikvision created some ill will with a Uniview distributor who...
ADT Employees Protest ADT CEO on Aug 10, 2018
So many ADT employees were so upset with ADT's CEO speech reported on by IPVM, that ADT's CEO was forced to send a mass email to employees to...
Axis / Avigilon Legal Battle Rises on Aug 09, 2018
In what is shaping up to be high-powered, will-not-back-down battle, Axis and Avigilon are squaring off in multiple legal contests. In 2017, IPVM...

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