*** ********
*** ******** *** ******* *** ******, cited ** ****** **** ** *********:

***** *** ***** *** ****, *** use ******* **** *** **** * years ******* **** **** ***** ***** decreased ** *** *****:

*** ****** ****** ********** **** *** driven ** ******** ****** ** **** than **% ** ********** *********.
VPN - ****** *** ********
**** ** *** ********** ********* ********* using *** *** ******** ****** ******. The **** ****** ******* *** ***** VPNs **** ******* ********-******* (*.*. **********, privacy, ********** *******):
- "***. ** ******* ********* *** ******** is ** ****** ****** ******** ******* as ******** ** ********. **** ***** sound ********* *** *** ***********."
- "*** *** ******** *******. ***** ** similar ********* *** ***** ********* ** convince **** *********."
- "***'*. * ** *** * *** of *** ** **** *****. *** is **** ******, ********** **** *** Dahua's *** ********* *** *** *** OEM's. ** ** * ***** ******* that ** *** ** ****** ** one ***** *****. * ***** **** it ***** ************* ** *********** *****..."
- "*** - *** ******* ****** **** is *** ********* **** **** *** from ******* ******** **** *** ** manage"
- "** *** *** ** ** ****** a ********** ****** ****** ********** ** a ******** ****** *** *** ********* can ****** *** ******* ****** ****** as ********."
- "**** ******* ****** ****** ***** ***** via ****** ****, *** ***. ** they **** ** ****** ** ****** VPN **** ***** *******"
- "** ******* *** ** ***. **** secure *** ** **."
- "***** ***. ** ** *** ** the ******** *** ****** **** ** remote ******. "
- "***, ********* ****** *** ******** ******** (for ** ****** ************)"
- "***. **'* **** ****** **** ******** equipment ** ******** ***********."
- "***, **** *** ** **** *** Chinese ***** ********** ***!"
- "***. ** ******* ** * ****** network ***********."
- "********* *** *** ***** ******* ** all *************"
- "***. *** ******** ********"
- "*** ******* **** ** **** *** Programmers ****"
- "***. ******** *******"
- "*** - ***** *** **** *** security **** *******."
- "*** - **** ** ***."
- "***. ********."
- "*** ******** ************"
***** - ******* ** ********
************* *** ******* ** *********** ********* said **** *** ****** *** ****** connectivity *** ****** ** *** ********'* demand/requirements. ****, ******* *** ******** ******** were *** ******* ******* **** ********* selected *** ******** ****** *******. *** was **** ******** ***** ** * customer ******** ********:
- "******* ** *** ********'* ***** ** security. ***** *** ***'* **** ** anybody ****** ** **** **** *** default ***. **** *** ***** *** are **** ******* ***** ********* ** connecting ** *** ******* ** ******* only ******* ** *** *********/****** ****** IP *******. *** *** ***** *** wants *******. "
- "** *** **** *** ********* ** which ******. **** ** *** ******* systems, ****** **** *** ***** ** based *******. *********, ** **** *** up * *** ****. "
- "***** ********, ***** ******** *** ********* risk ******* (**** ***, **** ** remote ******)"
- "** *** ********* ***** ********* ** the ********. ** ** ** ** with * ***** ********* **** ** use ***** **** *******. ** ** sell ** **** ********* ****** ** use ***** **** **** *** ****** DDNS *******. ****** ** ***** **** do **** ********** *** ***** ****** passwords"
- "**** ** *** ********* *** ******, so *** *** **** ********* **** is ****** *** ***** ** ******"
- "****** ****** ** ********* ********* ** customer's ** ***** ** ***** ********** however ** ****** ********* ** ******* DDNS/VPN *** ** ******** **** ***** with *** ******."
- "***. ********* ******. *** ******* **** why *** * ******* *** ******** reasons *** ** ******** * ****** of ****** *******."
- "*** ** ******** ** ***** ************* with ******** *********** ** ** ***********."
- "****, ** **** **** ** **** day ***, ** **** *** ****** IPs *** *** ******* ****** ******* to *** ******* ** ******* **. VPN: *** ****** ******** ******* "
- "*** **** ********** ******** ** **** corporate ******* ******** ******** ********* **** approach"
- "** **** **** * *** ** commercial ********* *** **** ******* ** their ** ********. ** **** ** group *****'* ***** ** **** ** cannot ** ********. "
- "********* ** *** **** ****, ******** recently ****** ****** ** ***** **** in *** ***** ** *** ******* IT **********."
- "** *** ********'* ** ***** ******** VPN, **** **** ** *********. **'** not **** **** ** ******* *** own *** ** * ********* ***********."
- "** **** ***** ** ********** ** it *******. ***** ** ****** ********** ddns ** ****. ********** ** ******* leave ** ** *** **** ** Team ** ****** *** ******* *******.
- "*** ********* **** **** ******** ********, we ** *** ***** *********** ******* their ******* ******* *** ******* ****** Meraki ** *********."
- "*** **********, *** ********* ****** ************ is ***** ** ********'* ** ************."
- "**** ** *** ********* *** ********** who **** *** ***** *** *** configuration *** ****** ******"
- "*******. ********* ********* **** ********* ******* a *** *** ************"
- "***, ******** *********"
- "*** ** *** ******** *** **** of *** ******* ** *********** ******* it"
- "**** ***** ** ** ******** ****** based ** ***** ******** ** ************"
- "**** *** *** ********* ** ******* preference *** ************"
- "*** *** ** ** ******"
- "********** ********* *** ***** *** ********* VPN"
- "**** ** ***, ** ******* ** the ********* ***** ** ******** *********."
- "******* ** ****** **** ***** ** the ********* *** ***** ***."
- "** *** ***** **** *** ********* IT ********** ******* ******"
- "***, ******** *******"
**** - ********/********* ** ***
**** *** ***** ** **% ** systems **** *********** ******** ********** **** are ****** *** ********* ** *** than ****:
- "** *** **** *** *** *********** app *** *** *** (***** *******). Setting ** * ******** ** ***** phone **** * *** ** *** complex *** **** ** *** ********* to ******."
- "****. ** ******* ** **** *** manufacturer's ********* *** **** ******* ** needed, *** ** ** *** *** the ******* **** ******. ** **** something **** ********* ** **** ******* snooping, ***** *** ********* *** **** advised ** ****** *** ********* *********."
- "**** ** *** ***** ************* ******** bypassing * ***’* ***** *** ******* with **** ***** ** ******** ** my ********'* ********. * *** ******* VMS *** ****** ******* ** ******* camera"
- "** *** *** *** ** ***** DDNS. * **** ********* ****** ***** be ******** ** **** **** **** service. *** ****** ************ **** ***** free **** **** ******* *** *** have ** ** *** *** *** hands **** **** ** ******."
- "* *** ** *** ****** **** mainly ** **** ** ********* **** having ** ****** **** **********"
- "******* ****** **** ******* ********* * web ******. ****** *** *** ****** very ******."
- "**** ** ***** **** **** ** the **** ** *******."
- "**** ** **** **** **** *** allow ****** ** ********* ** *********** accounts."
- "**** **** **** ********** ** ******. Because ** ** ****** **** ***** methods"
- "**** ** *** ********. **** ** use."
- "**** *** **** ********** **** ** restrictions"
**** ** ********** **** ****** **** VPN ******* ** ******** **** ********** for ****** ******. **** ***/** **** forwarding ******* ***'* ******* ** *** entire ****** ********, ******* **** ****** can ******* ** ******* *** ****** ***'* device (*.*., ****** ** ********).
*** - ***** ******/****** *******
*** *** *** ***** ****** ******, but ******* **** **** ******* (**% increased ** **%), **** *********** ****** the **** ****** *** *** *** is **** ** *****:
- "*** ******* **'* *** ******* ** set ** *** ** ****** **** the ****** **** ** *** ****** it **."
- "*** ***** ** ***, **** ** hikconnect. **** ** ***** *** *** often ********* *********, ******* ***, ***"
- "****** **'* **** *** *** ** 'cloud' ******* ****** ******** ** *** relevant ************. **** **** **** ********** has * ********* ******** ******."
- "* ******* *** ** * *** solution ** **** *** ******** *** connect **** * ****** ********."
- "***** ****** *** ** ***** (** Witness). ** **** ********** ** *** required. ***** **** *** ******* ** use, *** **** ****** **** **** forwarding."
- "** *** *** *** *** *******, but ***** *** **** ******* ** the *** **** *****. ***** *** is ****** ******"
- "*** - ** *** ** **** dealer *** ********* ***** *** **** really ****"
- "*** ** **** ** **** ** set ** **** *** *** *** QR ****."
- "***-******* ******* ** ** **** *** free"
- "***** ****** ******. **'* ****** *** decently ****"
- "****** *** ** **** ** *** main **** *** *** ***** ******"
- "*** **** ****** *** **** ** install *** *****, ** ****** ************* needed"
- "***, **** *****"
- "*** ******"
- "*** - **** ****** ******** ** manufacturer"
- "***. ******* ***** *** ******."
*******
*** ***, **** *********, ****** *****-******* remote ****** **** ******** ** ****. Using **** *** **** ********** ** more **** ********* *** **** ***** risky **** ***** ********** **** **** capabilities *** ****** ********** *** *******. As **** ** ******, *** / cloud ** ******** ** *** **** the ***** ** ****.
*******, ***** *** ***** ** ******* vendors ****** ** ***'* ********, **** using *** / *****, ** ****** a *********** ******* ** ***** **** continue ** ****** *** ******* ******* of ***** ***** *** ****.
*** ****, ***'****' ** *** ****, ***** ***** Surveillance ** *** ******.
Comments (12)
Undisclosed Manufacturer #1
Does this mean that nearly 50% of the people on this website, are not impacted by hacks, exploits, or other vulnerabilities since the VPN would have to be compromised in order for a security breach to occur?
Create New Topic
Sean Nelson
10/25/19 06:22pm
In my opinion, this site is way biased towards VPN due to heavy recommendations from previous articles. I would also have to guess that most integrators surveyed are large VMS users. I do have a hard time believing this refects the industry as a whole that the majority of installers are using VPN. I could be wrong though.
If you want my real opinion, its a shame that its almost 2020 and we are still using DDNS/Port Forwarding and VPN for remote management.
We should never have to use DDNS/Port Forwarding on any device that can be remotely managed. If there are manufacturers still developing products in this industry that require port forwarding for remote management, then they need to get with the program and develop a reliable and secure P2P platform. Its nearly 2020, cmon!
I can see why people use VPN, what I dont like though is the fact that we have to use it. Again, a good P2P platform should be reliable as well as trustworthy. No installer should have to go through the process of setting up a VPN in 2019 and beyond, nor should the end user have to experience working with one. Manufacturers should make this a much easier process for both installer and end user alike.
Create New Topic
Undisclosed Integrator #3
What method does Sureview use to connect to the NVRs so they can be viewed in Immix or whatever it is called? Do you have to open up a firewall rule to the NVR to allow Sureview from a monitoring company like Pro-Vigil or I-View to work or do they work through a VPN?
Create New Topic
Jon French
good job, answered many questions
Create New Topic