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

ACRE Acquires RS2, Explains Acquisition Strategy on Apr 19, 2019
ACRE continues to buy, now acquiring RS2, just 5 months after buying Open Options. One is a small access control manufacturer from Texas, the...
Access Control Course Spring 2019 - Last Chance on Apr 19, 2019
This is the last chance to register for the Spring Access Control Course. IPVM offers the most comprehensive access control course in the...
Door Operators Access Control Tutorial on Apr 17, 2019
Doors equipped with door operators, specialty devices that automate opening and closing, tend to be quite complex. The mechanisms needed to...
Alarm.com Favorability Results 2019 on Apr 15, 2019
The once dot com startup has evolved to become a core provider for home security and is now expanding into commercial. In their first entry in...
UK Camera Commissioner Calls for Regulating Facial Recognition on Apr 15, 2019
IPVM interviewed Tony Porter, the UK’s surveillance camera commissioner after he recently called for regulations on facial recognition in the...
ISC West 2019 Report on Apr 12, 2019
The IPVM team has finished at the Sands looking at what companies are offering and how they are changing their positioning. See below for 50+...
Pole Mount Camera Installation Guide on Apr 11, 2019
Poles are a popular but challenging choice for deploying surveillance cameras outdoors. Poles are indispensable for putting cameras at the right...
Spring 2019 50+ New Products Directory on Apr 08, 2019
We are compiling a list of new products for Spring 2019 and have over 50 already. Contrast to Fall 2018 New Products Directory and Spring 2018...
Spring 2019 IP Networking Course- Register Now on Apr 04, 2019
Register now for the Spring 2019 IP Networking course here. Just $299 for the course. This is the only networking course designed specifically...
Startup GateKeeper Aims For Unified Physical / Logical Access Token on Apr 04, 2019
This startup's product claims to 'Kill the Password' you use to keep your computers safe.  They have already released their Gatekeeper Halberd...

Most Recent Industry Reports

Access Control Course Spring 2019 - Last Chance on Apr 19, 2019
This is the last chance to register for the Spring Access Control Course. IPVM offers the most comprehensive access control course in the...
Riser vs Plenum Cabling Explained on Apr 18, 2019
You could be spending twice as much for cable as you need. The difference between 'plenum' rated cable and 'riser' rated cable is subtle, but the...
Verint Victimized By Ransomware on Apr 18, 2019
Verint, which is best known in the physical security industry for video surveillance but has built a sizeable cybersecurity business as well, was...
Milestone Drops IFSEC on Apr 18, 2019
Milestone has dropped out of Europe's largest annual security trade show (IFSEC 2019), telling IPVM that they "have found that IFSEC in EMEA no...
The Fastest Growing Video Surveillance Sales Organization Ever - Verkada on Apr 17, 2019
Verkada has the fastest growing video surveillance sales organization ever. In less than 2 years, they already have more salespeople in the US...
Door Operators Access Control Tutorial on Apr 17, 2019
Doors equipped with door operators, specialty devices that automate opening and closing, tend to be quite complex. The mechanisms needed to...
Securadyne CEO: IPVM 'Entertaining For An Ignorant Few' on Apr 16, 2019
Securadyne's CEO Carey Boethel is unhappy with IPVM's report - Failed Integrator Rollup, Securadyne Sells to Guard Giant Allied. Indeed, he...
Dahua Repositionable IR Multi-Imager Camera Tested on Apr 16, 2019
Dahua has released their first repositionable multi-imager camera, the Multi-Flex 4x2MP, claiming integrated IR, true WDR, and flexible...
Strong ISC West 2019 For Manufacturers But Concerns For 2020 March Move on Apr 16, 2019
ISC West 2019 was strong for manufacturers, according to new IPVM survey results of 100+ manufacturers, consistent with 2018 results. However,...
Axis Supports HD Analog on Apr 15, 2019
In 2017, Axis declared 'Everything is IP': Now, in 2019, Axis has released support for HD analog, with their new encoders.  Why the change?...

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