Remote Access (DDNS vs P2P vs VPN) Usage Statistics 2019

By IPVM Team, Published Oct 25, 2019, 09:03am EDT (Info+)

Remote access can make systems more usable but also more vulnerable. How are integrators delivring remote access in 2019? How many are using dangerous port forwarding?

We asked integrators:

What do you typically setup for customers for remote access to their video surveillance systems (e.g. DDNS, P2P, VPN, etc.)? Why?

This is the successor to Remote Access (DDNS vs P2P vs VPN) Usage Stats 2017 report.

See also IPVM's Remote Network Access for Video Surveillance Guide, which outlines the 5 primary methods for access and identifies pros and cons for each.

In this report, we examine statistics based on responses from 150+ integrators and examine the trends they reveal.

*** ********

*** ******** *** ******* *** ******, 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)

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?

Agree
Disagree
Informative
Unhelpful
Funny

Roughly, yes, however, while a VPN does decrease the risk, it does not ensure there are no vulnerabilities.

Agree: 1
Disagree
Informative
Unhelpful
Funny

No. It means that there are people on this site who sell to residential customers and VPNs have not yet penetrated the market space due to complexity. Not all installations are created equal.

Agree: 4
Disagree
Informative
Unhelpful: 1
Funny

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.

Agree: 5
Disagree
Informative
Unhelpful
Funny

this site is way biased towards VPN due to heavy recommendations from previous articles

Lol...

hard time believing this refects the industry as a whole

Well, I have a hard time believing a third of 'integrators' use port forwarding / DDNS in 2019... There's obviously diversity across the industry. People buying white label Hikvision or RaySharp are going to skew more towards not knowing how to spell VPN, let alone configure one.

I can see why people use VPN, what I dont like though is the fact that we have to use it.

I agree with that. What are you using for P2P, HikConnect or?

Agree: 1
Disagree
Informative
Unhelpful
Funny

People buying white label Hikvision or RaySharp are going to skew more towards not knowing how to spell VPN, let alone configure one.

It shouldn't be considered a badge of honor that you have to setup a PVN (intentional misspelling) because a convoluted VMS may not have a good P2P option, especially when the cheap Chinese DVR's do. The mere fact that a VPN would even be considered difficult to configure is a good reason why we shouldnt be doing it in 2019.

Agree
Disagree
Informative
Unhelpful
Funny

Lots of high-security environments do not allow nor want P2P because of the security risks of letting 3rd parties inside their networks... like cheap Chinese DVRs.

Serious question - what do you use for remote access to your white labelled / Nelly's products?

Agree: 1
Disagree
Informative
Unhelpful
Funny

If the high security environment wants remote management of their surveillance system, then the manufacturer of the products they use should make an easy and reliable and secure platform for them to view remotely. Its 2019.

Questions to ponder

If u r using a vpn and your manufacturer has a p2p cloud like solution, is that essentially saying that u dont trust your products cybersecurity? If so, why r u installing such product?

If a manufacturer makes a product that is so called cyber secure but wont consider making an easy p2p like solution, does that mean they are not fully confident in their cybersecurity skills? Its 2019, make a solution that doesnt involve making your customer do a vpn.

Agree
Disagree: 1
Informative
Unhelpful: 3
Funny

Absolutely. It's enough of a headache getting some of our customers to allow ANY remote access to the system, and nowadays its almost always 2fa with RSA tokens to get into a VPN.

Anything "cloud" or direct connect P2P are the quickest ways to kill any conversation with their IT teams.

Agree
Disagree
Informative: 1
Unhelpful
Funny

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?

Agree
Disagree
Informative
Unhelpful
Funny

The monitoring company would need to establish a connection between the Immix Server and the edge device. How that connection is established depends on the customer/integrator/monitoring company. Typically a VPN is preferred for security, but I know smaller/simpler sites tend to get away with port-forwarding on the modem/router.

Agree
Disagree
Informative
Unhelpful
Funny

good job, answered many questions

Agree
Disagree
Informative
Unhelpful
Funny
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports