Results **********
********* **** ************** **** integrators '*****' ** ****** deploy ****** ******:
*******, **** ~**% **** us **** **** ****** access *** ******** ** the ****, *** ***** overall ****** ** *******, several ******* *** ******* it ****.
Key ********
********* ***** ******** ***** three ******* *** ******** broader ****** ****** ***:
- ** ******: ********* ** *** have ******** ** ****** or ***** ****** ***********, and *** ******* **** traditional ***********.
- *** ****** ******: **** ****** ***** have ***** ***** *** secure ****** ****** ** compared ** ******* *******.
- *** *********: *** ******** ** mobile ** *** ******* the ****, ** **** cases * ****** ** 'extra' **** ******** ** traditional ***********.
** *******, '** ******' and '*** ****** ******' were ********* ****** ******* as *** ******* ******* explaining ****** ****** ********, with '*** *********' ********* as * ******* ***** reason.
No ******
* *** ****** ******** use ** ****** ****** is **** ****** **** end *****. **** *********** told ** **** ***** customers *** *** ****** or ********** ** ******** it ***:
- "****. ** *** *** requested ** ** **** yet."
- "*% ******* **** ** people ***'* **** ** install ********* **** ** open *****. ** ****** we ******* ****** ******* using **** ** ***********."
- "****, *** *** **** requested."
- "**** - ** ****** from *** ********* *** over ******** **** ***********."
- "****, *** **** * lot ** ******** ** another ************** ****** ** manage ***** *** ***********."
- "** **** **** ********* one ****** ** *** past **** **** ****** access. ** ******* *** solution ********* *** **** don’t **** ** *** mobile ***********."
- "*% ***** **** ***** and ** **** **** see ****** ***** ** it. ** **** ** be ******* **** - not ******** ****!"
- "****. * ***** **** is **** ** * residential ****** *** ** have ***** **** ***** for **, *** ***** push ** ** * secure ****** ** **** time."
- "** **** **** *** two ********* ******* ****** access. **** *** **** with *** *** ********* readers. ** **** ** not *** * **** adoption ** **** ********** right ***."
- "** *** ***; ***** 10%. *** ******** *** interested *** * ***** it *** **** ******* it *** **** ****** intent ** ***. **** two ********* **** * have **** ******** **** are ******** ***** *** technology."
- "**** ***. ** ** an ****** **** ** provided, *** ******* ****** request/use *** *******."
- "*%. *** **** **** via ************ ** *** client. ******** ** **** asked ** ***** ****** access *** *****-*** ********. Otherwise ***** *** **** no ********."
* ************ ****** ** weak ****** ** *** all ****** ************* ******* a ****** ********, *** even ***** **** ** often ** *** ******* promote ** ***** *** users. **** ***** *** party ******/ ******** *******, product ********* ** ********* marketed ** ***********. **** more ******* ******* ******, and **** **** **** to ****** ***** ********* to *** ******, ****** will ****** ********.
*******, ** ******** ** following ******** **********, ******** barriers ** '********' *** 'cost' *** ** ******* or **** ****** **** time, *** ***** ******* coupled **** *** '*******' of ****** ****** ** too ***** *** **** access ****** ** ******** yet.
Not ****** ******
**** *********** *** ***-***** are ********* ***** *** security ** ****** ****** systems, ************* *****, *** end-user ***** ******** ************ into ******** **** ****** systems:
- "**% ***. *** **** users (****) ***'* **** to **** ** *********, for **** ******** *******."
- "** ***** ****** *** to *** *** ********* but **** ***'* **** safe ****** *** ******* to ****** * ****** door **** ***** **** though *** ***** **** to ****** ***** **** enter * **** **** and ******** **** ****** app ** ******** *** to *** ******* ** you *** ****** *** door."
- "**** ** *** ****** control ******* *** ******* and ******* **********. *** medical ********** ******* ** to **** *** ****** isolated. ******* ****** **** only."
- "****. ****** ****** *****, business **** **** ******* over ***** ******."
- "*%. ** *** ********* a ******* ********** **********. Though ** **** ****** with **** ********* ***** derived ***********, ** **** to *** *** ********, and ***** *******, ** use **** ********* (*** at *** ******) ****** we *** ****** ****** mobile ***********."
- "**%. ** ***** ** closer ** ***% *** our ********** *********, *** we ** ****** *******."
- "**** *** ***. *** reason ** *******, ***** is ***** ********"
- "****. **'** *** **** executive ******** ******** ** this **** ********* *** in *** *** *** testing ***** ****** *** customers ***** **** *** a ******** **** ** phone ** ****** ** apps ******. "
- "*%. ** ***'* **** that **** ** ******* yet *** ** *** exploring **. **** ** be **** ** ** secure."
- "***, ******* ********* ***** security *******"
- "****. ********* *** *** convinced **** ******** ******* are ******."
**** ** ***** ******** share **** ****** ****** is *** ********* ** market-specific ******** **************, ******* showing **** *****-***** *********** are *** ****** * good *** *** **********, high-security, *** ************* *********.
Too *********
* *********** ******* ** wider ****** *** ** higher ****, **** ** terms ** ****** ********** and ************** **** ******** to *********** ******** ***** and ****.
- "*% **** ******** ********** subscriptions *** ******* *********, and *** *** ********* use ***********."
- "**% ***** *** *** cost ** * *** factor."
- "****. *** ******* *** purchasing ************ **** ** be *********** ** *** customers. **** **** ******** to ******** *** **** mobile *********** ** *** time. *** **** **** they ******. "
- "** *** **** *** credentials **** *** ************ which ****** ****** ** the *** **** **** their ********* **** ** upgraded ***** ******."
- "**** **** *% - the ****** ** *** complexity ** ******** ****** credentials *** ***** ****** cost ******** ** ******** credentials(cards, ****, ***)"
- "**** ** * ******* of *** ****** ** provide ********* * ****** readers. *** *** ***** installed **** **** ******* but ** *** *** to ******** *** ******* in * ***** ***** usually *** ******** ** facility ******** ****** ****. The ********* **** ** a ****** ********** ** difficult ** **** ** customers."
- "* ***** **** ** it ***** ** *** cost ** *** *** time ********** **** ** tied ** *** *****."
- "*% **** **** **** & *** *********** *** expensive."
- "** **** **** *%. Customers ***'* **** ** pay *** *** ********, and **** ***'* **** to ********** *** *******. Unfortunately, ** **** *** made *** ********** ** manage ** *** **** and **** *** *** because ** ***'* **** the *********."
- "*. **'* * ***** pain *** **** *********. I *** **** ** to * ****** *** open *** **** ** under * ****** **** a ****. * ****** credential ** * ****. I ** **** ** phone ***, ****** **, find *** ***, *** into *** ***, **** the ***** ****, **** sure ** ********* ** on (******* **'* *** to **** *******, **** open *** ****."
- "*% *** **** ****** access *********** ******* ** the ********** ***** *** the ******* *** ****."
** *******, *** **** of ******-***** ******* *** similar ** *********** ***** of '***-******' *****, *** we ****** ****** ****** mortality *** ********* ** result ** **** '****** ready' ******* ** ****** years.
*******, **** *** ********** incumbents **** ***, ******* for ****** *** * problem. *** ******** ******** mobile ********** ******* ** be * ****, '*** user' ******* **** **** the ****** *******(*** **** ****:*** ****** ******), ******* **** ****** access ******* **** ***** to **** ****** *********** using *** **** ***** as ******** *****, ** a '*** *****', *** device *****.
Systems *** ***** ****** *****, *** ******
*************, **** ***** **** even ***** ****** ****** adoption ** ***, **** already **** ******** *** capability ** *** ******* they ****.
*** ****** ********* ** 'mobile ****** ** ***** when ***** ***' ** internal ******** ** ****** use *** ********** ** change.
- "****** *** *** ******* included ******-***** *******. **** about *% ** *** customers *** ******** ***** the ****** *********** *** they **** ** ** ready *** **** **** decide ** **** ** out."
- "** *** ******** ** if *** ******* ********* have *** **********, *********** 95% ** ****. ** the ******** ** *** many *** ******** *****, 10%. ***** * *** talking ***** ** *** sales *****, ** ****** gets *********** *** ** the ********* ********** ** go ******* **** *** extra ************* *** ****** of ****** ***********. ******** understands *********** *****/****."
- "*** ** *** ******* now **** *** ********** through ** *** *** user ******** *** **** light. *** ** *** customers *** ********** ** using ***** ****** ** credentials. **** ***'* **** to *** ***** ******** phones *** ****."
- "***% *********, ***** **% adoption"
- "** ** *** * regularly ********* ******* **** our ****** ******* ****. It ***** **** *** DSX ******* ******** *****. But ****** ** ** have ********* ********** ** utilizing **."
- "**** **** *%, ****** is **** ********, * have ********* **** **** purchased ****** ***** *******, but *** ***** ***** cards"
- "** *** ** ****** dealer *** **** ******* is *****-** ** *** RC-04 ** ** ** available ** ***** *** percent ** *** ************* and ** **** **** it ********* ** ***** 50 ******* ** *** applications. ** **** ** a ***** ******* *******."
- "*** ** *** *** install ******** ****** *************** for *** ***** ******* very *** ********* ******** use **** ** *** mindset ** ******** ***** force **** ** *** standard *********** ***** ********* specific *****."
- "***% *** ** *** systems **** ** ******* can ****** ***** *** customers *****, *** **** about **% ** **** actually *** *** *******."
Strong ******* *******
******* ****** *** ** widely ******* *** ***, a ******* ****** ** high-percentage ***** ************ ********* the ******* ****** ** the *******.
******, ***** *********** **** that ****** ****** * new ********* ************** ********** to ******* ** *** typically *** **************, ****-********* access ******:
- "*** *** **** **** it ** * *********** for *** ******** ** unlock ********. **’* * good ******* ***** ** well **** *********."
- "***%. ** ** **** to **** **** ********** access."
- "****** ***** ****** ***** phone *** *** ********* different **** *** ** the *********** *** *******."
- "**% ** *** *** installations ******* ******* ********* Go. ***** ** **** for ***** ** ****** and **** ***** **** a ********."
- "** *** ******* *** discussions **** **** ********** to **** *** ********* of *** *******"
- "**-**%. ********* ****** **** the ***** *********** ** unlocking ***** ******** **** their *****."
- "**% ******** ******** *** mobile ******. ** * feature ** *** ******** (Genetec ******** ******) ********* find **** * ****** feature ** *** ***** they **** ** ******** release * ****"
- "**% ******* ( ** sell * *** ** Brivo *** ** ** a *** ******* ***** that ********* ***'* **** to ***** **** ******) also ********** ********* **** the ******* ** ***** able ** **** ********** from * ******** *** contractors ** ********."
- "**%, ******* **'* * great ******* *** ********* has * *****."
- "****** ****** ****** ********. Users ******* ***** ***** phones ******** **** **."
Upcoming ****** ********
**** *** ********* ******* individual ***** *** **** compare / ***** **** out ******* **** ***** in ****** *****.
***** *** *** ********** test *******:
Comments (4)
Scott Fischer
IPVMU Certified | 07/19/19 01:58pm
As an end-user, all of our new installations include mobile enabled readers. We have performed some limited testing with a select employee population with positive results; however, we still require employees to wear and display a corporate badge which reduces the benefits of using a mobile credential. If we allow employees to stop wearing a corporate badge, we would negatively impact our defense-in-depth approach since there would be no visible difference between authorized and unauthorized personnel inside our facilities. If someone piggybacks into an office where employees use only mobile credentials, there is no way to easily identify the unauthorized individual (unless there is a small, well-knit employee population).
We are actively looking for a solution to this issue. We need a way to visually verify employee identities and access while they are inside secure areas. Without this capability, I do not see mass adoption of mobile credentials except in areas with extremely low security requirements.
Create New Topic
Chris Hammond
I wonder how many respondents that said security risks were a reason for not using mobile credentials are using/selling 125 kHz proximity cards.
Create New Topic
Undisclosed #2
IMHO the people worried about security have it backwards. Only a select few can 'hack' an app, but anyone can 'borrow' a badge, and it's much easier to do anonymously. The priceless value a mobile app brings is that users are far more consciously aware of their phone. This study https://www.slideshare.net/kleinerperkins/kpcb-internet-trends-2013/52-Mobile_Users_Reach_to_Phone found that users unlock their phones 150 times a day on average, meaning they always know where their phone is. All the OSDP encryption in the world doesn't do a damn thing to help with that.
But, looking at a mobile credential as just a card replacement is short sighted. A phone is a computer that knows
- Where it is, it could be used to locate someone in real time, to restrict access based on proximity to the resource being accessed or anticipate what door the holder wants to access.
- Can process biometrics - Require two or more factor authentication with authentication forms customized to the cardholder and implement biometrics on a person/door/time basis, eliminating all that expensive gear at the door.
-Communicate - Receive push notifications (mass or targeted notifications), communicate with others (silent call for help).
- Record video and pictures
And so much more so let's stop thinking of a phone as a replacement for a credential and start imagining what we can do with it to move security forward.
Create New Topic