VLAN For Video Surveillance Usage Statistics

Published Aug 21, 2017 13:10 PM

VLANs (see our tutorial) are an option for networks using video surveillance, but how often are they actually used?

125+ integrators told us how and when they use VLANs for surveillance products.

Integrators who use VLANs as a matter of course were quite vocal about the importance of doing so. As one integrator said:

I continue to be amazed at how "security" integrators simply install plug and play network switches and ignore the security of the network. They install alarm & access control systems with supervisory circuits in order to detect efforts to defeat it, yet at the same time feel that IP based security endpoints shouldn't? makes no sense to refuse to become qualified on a critical component of the systems they sell.

Integrators who do not regularly use VLANs either do not see the value in it, or worry that their end users may not have the ability or manpower to set up and maintain a VLAN. As one integrator told us:

We do not get into managing networks as a matter of support, unless it is our own.

Segregating ************ ********* ********** ********** *** ***************

*********** **** ********* *** ***** ** so ******* ** ***** ** ****** to ************ ********. 

  • "*** *** ****. ***** ******* ******** its *** ****, ***! ** **** to ********* **** **** ** ***** traffic. **'* ********* ** **** * segregated ******** *******. ****** ** ******. Less ******. ** **** *** ****. Can **** **** **** ******** ** well. *** *** **** *** *** depending ** ******** ********."
  • "***** **** *** ******** ***** *** segmented ******* ******** *** ***** ************ that *** ******."
  • "****** *** ** *** ******* *** on *****. ** *** **** ****** to ********* *** ******* *** **** other ********."
  • "** **** ***** ** ***** *************** easier *** ** **** **** ****** pointing ** ** ********."
  • "******. ******* * ****** *** ******** and *** ******* *** ****** *******. Cameras *** *** **** ***** ******** without ******** *****. ** ** *** permit ****** ****** ** ******* **** unauthenticated *****."
  • "** ****** ***** *** ******* ** our ******* ********. **'** ****** ********** our *** ******* ** ********* **** to ***** * **** *** ** to ***. **** **** *** **** layer ** ******** *** ***** *** IT **** **** ******** ******* ** the ******* ** ****'** *** * bandwidth *******. * ********** **** ** stay ** *** **** **** *** IT **** ******** ** * ***. Sometimes **'* ***********."
  • "** *** ***** ** ******** ****** than ***** **********. * **** ***** limit ************ ****** ** *** ******* and ***** ****** * "*********** *****" for *** ******* **** **** ******** with * ********'* *******. ** ********** our ********** ** *** ****** *** provides ******* *** ** ****** ** the ********'* **** ** **** **** don't ************* **** ** *** ****** by ****** ******* ** *** *******."
  • "***** *** ** ******* *** ********** by ** *********** ******* ************* ** the ******** ********* ***** ** ** the **** *** ** **** ***** change ******** **** ****** ** ***** are ****."
  • "** ** **** ****** ** ** network ***** ***** ** ** **** are *** ** *** **** ****, then ** **** ** ** *** something ** ** *** ** *** devices."

Some ***** *** ******** ******

**** *********** **** *** * **** when * ******** ******** **. 

  • "** *** ********* ******* **** ** departments ** ****** *************. ** ***** this ** ** **** ** ******. I ***** *** **** ***** **** not, **** ** ******* *** ***** on ** * ****."
  • "******** **** ** * ******** **** is **** ** ** *** *********. don't **** ****** * ********** ** issue ** ****** ***."
  • "********* ** *** ********* ** **********'* practices, ** *** ***** **** *********."
  • "****.** ******** *** ** ** *** who ** * **** *** ******** it."
  • "*** *****. ********* *** **** ********* to ********** *** *** ********."
  • "** ***'* *** ***** ****** **** the ******** ******."
  • "*** ******* **** ** ** ******. Most ** *** ******** *** ***-******** we *** *** ******** ** *** client ** ***** *******, *** ** don't *** *** ****** ** ****. We **** ** ********* ** ***** specification, *** **** ***** ***'* **** any ******* **** *** *** ********* were ****."
  • "******. ** ** ***** ** ****** try, *** ********** **'* *** ********'* call ** *** **** *** ***** network. ** ****** **** ** ******* the ******** ** ** *** **'* important ** ******* *** ******* *** other ******** ******* ** * ******** VLAN **** *** ******** ********** *******. Most ********* ********** *** **** ***'* an *****."
  • "***** *****, *** **** ** ******* dictated ** *** ******** **** ******* reside ** ***** *******."

Some ********* ****** ******* *****

**** *********** *** ******** ** *** a ****, ******* **** ** *** offer ******* ********** ******** *** *** not ********* **** ***** ********* *** handle * **** ** ***** ***. This ** ********** **** *** ******* systems, ***** ********* ** *** ******* **** VLANs ** *** ****. 

  • "******* ******* (pay ** **** ***** ** ***** network - *** ***** *** ***** to ****** ******* **** ***."
  • "** ********** ********* *** *** ** VLAN's ******* - ** ** *** generally ****** ******* ********* ******* *** resources ** ** ***** *** ****'*."
  • "**** ** *** **** ********** *** smaller ************* * ***'* *** *****."
  • "** ********** ******* ** ** ******** enterprise ***** ******* **** ******* *** always ** * ****** ****** ****** and ****. *** *********** *********** ******* but ******** *** **'* *** ***** user *******. ** ** ** **** adding **** * "***********" ******** **** we ***'* *** ****."
  • "** ****** ********* ***** *** **** gotten ****** **** ** *********** *** has *** ************ (**********) ** ****** it. ** ** ** *** ***** the ******** *** ********* **** ** push **** *** * ******** ******* with *** ********."
  • "******. ** ***'* **** **** **** clients *** ******* ** ****** ***."
  • "** ***** ******* ** *** ***** level ** *** ******** *** ***/** they ****** ***** ** ***********."
  • "** ****** ******* *** ********* ** do * **** ** ******** ** separate *** *******. ********* ****** *** customer *****'* **** *** ********* ** how ** ***** * ****.
  • "****** *****, ***** ** ***'* **** the ******* **** ***** ** ***. There's *** ******** ***** **** *** the ** ****** ** **** ***** of *** ************ *** **'* ******* the ********* ******** *** ** *** own."

Many *********** *** ********* ******** ***** ********

**** *********** ********* ********** ********** ******** *** ************ equipment, *** *** ***** **** **** a ******** ************ ******* ** *** possible. 

  • "** *** ** *** *** *** switches *** ********* ******* ******** ********."
  • "****** *****. ** ******* ***** ** separate *** *** ****."
  • "*** **** ** *** ************* (~**%) we ********* ***** *** * ********** separate *******, ******** **** *********** **** down ** *** **** ****** ** years. ** *** ******** *** ********* to *** ************ ******* *** ** VLAN's *** ********."
  • "** *** ******** ******* ** ********, than ***** ** ******* ** **** for *****."
  • "******** ********, ** ********* *** *** of * ********** ************* ******* (******** bridged *** ***) **** ***** ******* data/business/internet *******."
  • "** ****** ** ******** * ********* physical *******."
  • "** **** ** *** ********** ********** networks *** ** *******. ********** ******."
  • "***** *** ******* *** ** ***** own ******* *******, ** **** **** an *****."
  • "******, ** ****** ********** *** *** parallel ******* **** ********* ******** ***... and ****** *** ******** ****** *** network ******* * ********* ******* **** on *** ****** ** **."
  • "** ********* ** ********** ******** *** for **** ** ********** *** ********* security."

**** ***** ** ******** ****** ** see **** ********** ** ***** ************ networks *** ** ********* ** ********* ones.

Comments