Subscriber Discussion

What Are The Best Way To Secure IP Cameras And NVR Over The Network?

UI
Undisclosed Integrator #1
Feb 10, 2019

I’m wondering about the best way to secure the IP cameras and NVR over network.

on other hand, the Arecont Vision & Exacq Vision have a back door or not?

(1)
JH
John Honovich
Feb 10, 2019
IPVM

Don't port forward. Use VPNs. At a high level, that is the two most fundamental recommendations.

See: Cybersecurity for IP Video Surveillance Guide and VPNs for Video Surveillance Guide.

Arecont and Exacq do not have a track record of significant vulnerabilities.

(1)
(1)
(1)
U
Undisclosed #2
Feb 10, 2019
IPVMU Certified

on other hand, the Arecont Vision & Exacq Vision have a back door or not?

Arecont and Exacq are more than three letters.

(5)
MM
Michael Miller
Feb 10, 2019

Change all the default passwords and use a VPN.

(1)
UM
Undisclosed Manufacturer #3
Feb 11, 2019

Turn off any unused protocols.

UM
Undisclosed Manufacturer #4
Feb 12, 2019

Here is what our IT person uses when training security integrators on camera cyber issues...hope it helps

 

  

(2)
(1)
JH
John Honovich
Feb 12, 2019
IPVM

While HTTPS has some security benefits, it is going to increase complexity of setup and many installers are going to have problems. I am guessing (fairly confidently) that 98%+ of video surveillance systems do not use HTTPS to connect cameras and recorders / VMSes. I added this to the list of future surveys. Anyone with thoughts, I'd be curious to hear.

(1)
(1)
(1)
UM
Undisclosed Manufacturer #3
Feb 12, 2019

It is good, in theory.  However, the full solution needs to support it.  Many VMS and NVRs don't support it.  In addition, it adds more load to the NVR/VMS CPU, and can lower performance.

When going to the device webpage, it usually will give a certificate error, confusing most installers or end-users.

Furthermore, the camera - NVR/VMS connection is usually on a more protected network segment and is not the one to worry about securing.  Rather the one that goes out to the internet/WAN from the client to the VMS.

I have worked with cameras that support HTTPS to the NVR and from the NVR to the client software.

You also don't want to provide a false sense of security. Most cameras or VMS or NVRs that perform encryption encrypt the web page and API, but not the video itself.  The few systems that are capable of this will again use more CPU, etc.  I think that very few do this, except for some cloud systems.  Find out what is actually encrypted.

(1)
U
Undisclosed #5
Feb 12, 2019

Onssi has Https for the camera connection.The video stream is encrypted by default so no technician configurations are needed for that. Even on a private camera network the recorders if not using HTTPS camera connections will show the user name and password in plain text within wireshark on a local lan when perusing the client host traffic to the recorder. Yes you should use Https between camera and recorder.

As far as all the Hikvision trunk-slammers here, go figure. Changing your camera password to &#$H**QN*F*Nhhseh83hJ@*...awer832 is not going to yield any protection in Http, Wireshark confirms this.

Also as I have squelched in another post, find out if you have been pwned!

https://www.youtube.com/watch?v=N5pt4xgxC5E

BTW, I do not like Onssi. Recorder zones are a bad design when considering camera storage distribution. Perhaps Qognify can dilute the system further so I have a out to migrate a few customers off of Onssi /Seetec / Frustrated.

(1)
(1)
(1)
JH
John Honovich
Feb 12, 2019
IPVM

Onssi has Https for the camera connection

Many VMSes offer https but the problem is each IP camera needs to be set up to use it, ergo rarely is this used whether it is OnSSI, Milestone, etc.

(1)
(1)
U
Undisclosed #5
Feb 12, 2019

So with all the video testing IPVM performs the thought of using SSL connections is passed because it is a 1:1 setup per camera? Is this due to some of the technicians not having the right skill set?

Again, Onssi being an example look at the conversations between on all of Onssi communication ports. If the camera connection is passed as HTTP port 80 rather than SSL port 443 then the password is readable in Wireshark or Steel Central as CLEAR TEXT. 

Perhaps the local gas station or beauty salon CCTV customers do not perform pen tests, but for those customers that realize insider threat need to understand this is happening. Each VMS has different methods for authentication and stream management so the case may be different from one platform to the other.

In Wireshark look at the conversations between the Device Manager, Base Station and Ocularis Client, run the pen test from the corporate network. The cameras even if they reside on a private dead net 192.168.x.x network still send the password between the applications that reside on the corporate network.

Integrators need to get their skill sets up when deploying these systems, start by downloading Parrot OS, go over to youtube and start learning about simple tools that test your configurations. Jump in.

(1)
U
Undisclosed #2
Feb 12, 2019
IPVMU Certified

The cameras even if they reside on a private dead net 192.168.x.x network still send the password between the applications that reside on the corporate network.

Are you sure about the clear text password thing?

Most cameras and VMSes use digest authentication, which is a hash of the password.  Add in a nonce and you’re good to go.

I’m not saying you can’t force the camera and VMS to use clear text (or base64) passwords, but it shouldn’t be the default.

(1)
U
Undisclosed #2
Feb 12, 2019
IPVMU Certified

I am guessing (fairly confidently) that 98%+ of video surveillance systems do not use HTTPS to connect cameras and recorders / VMSes. 

fwiw, when the recorder is in the cloud (Nest/Arlo etc), imho, the traffic is usually encrypted.

JH
John Honovich
Feb 12, 2019
IPVM

Yes, that's why I said 98% rather than 99%. Outside of directly cloud connected cameras (which are a distinct minority considering the tens of millions of conventional IP cameras), it is very rarely done.

UE
Undisclosed End User #6
Feb 12, 2019

How secure do you really want to make things?  Let me share with you some of the recommendations that are used in large deployments where I dabble a bit, they can get pretty complex but in my world Regulatory Compliance is the name the game.

Network Segmentation is key to security period.

First its highly recommended that you deploy a flat network so it is easier to manage the devices connected to it.  When you have a closed secondary network for IP Camera traffic its typically on a unmanaged switch.  Then direct access to the devices is challenging to say the least unless you are physically at the switch.  You may often rely on the VMS software to push camera updates if they even have that capability, if not then its do truck rolls to update camera firmware etc which is very costly with 8K+ recorders and 150K+ cameras.  Average cost per site is about $300 which is pretty pricy to push a required firmware update (abut $2.5mil per update). 

Second, create a separate VLAN for the IP Cameras and the recording devices, be sure to designate a create a small MAC ACL and or JumpBox for IP Camera Administration so the device can be managed remotely within its VLAN by only by authorized connections.   Limit the amount of folks that can have direct access to the devices, really no need to access the camera web page unless you are doing configuration or troubleshooting IMO.

Third is use 801.x EAP-TLS Certificate Based Authentication.  Yes its a bit of work but it locks things down pretty tight.  As a failback you can use MAB (MAC Authentication Bypass) to keep it secure assume the switches you are using support these features.

Once you get things talking to each other then you move on to how to manage it w/o loosing control, you must have a robust Policy to manage the following using the either NIST or ICS-CERT Cyber Security Guidelines (links below).  Compliance and Reporting is the name of the game in my world.

- Password Management

- Patch Management

- Configuration/Drift Management

You should have a solid Baseline Configuration that is deployed with all devices and the ability to measure drift from it to correct, this will help ensure if followed properly that all of the devise are deployed ready to go out of the gate.  That being said most VMS platforms which I consider to be the ecosystems of a surveillance system are very weak at the three examples above. 

Unfortunately the VMS manufactures don't thinks its their responsibility to provide these functions and often push it back on the camera manufacturer, think of yourself like a very large enterprise like I assist with and all of the devices to manage, you need one tool in the toolbox to manage it all not five or six tools (one form each camera supplier).  From what I can see the VMS platforms still don't get it and there appears to only be one solution now that can help bridge the gap, shameless plug for Viakoo suggest you check them out.

You want to learn a bit more about cyber security standards check these links out, there is a ton of stuff I did not call out that is employed to enhance security I chose not to dive into.

https://ics-cert.us-cert.gov/Standards-and-References

https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.04162018.pdf

 

 

 

 

(1)
(2)
Avatar
Ariel Levy
Feb 12, 2019

Use Hardware Firewall to secure your network. Netgate / pfSense are fantastic open source solutiouns!

(1)
MD
Matthew Del Salto
Feb 12, 2019
Hudson Security

Don't connect your cameras to an internet uplink have them on an offline poe switch connected to a proper vms server.

Avatar
Jon Dillabaugh
Feb 13, 2019
Pro Focus LLC

Easy and inexpensive ways to secure your cameras;

1) Keep the cameras on a network segment that does not have internet and/or corporate network access

2) Give VMS servers two NICs minimum; one NIC in corporate, internet facing LAN, and the second NIC in camera (sequestered) LAN.

This can be done with either separate switches, or with properly implemented VLANs using managed switches. We generally like to use managed switches with VLANs as it saves money on hardware. If done correctly, it is as safe as separate switches.

3) Keep firmwares up to date.

4) Use complex passwords.

5) Create non-admin accounts for VMS server access. Create a new user with only the minimum rights needed to pull camera streams. This can limit VMS users having the ability to change zoom or focus.

(1)
UM
Undisclosed Manufacturer #7
Feb 14, 2019

This is a very similar approach to how we do things at work.

 

I would also recommend logging any outside traffic, so that if something does go awry you are able to see when, where and how; to prevent future issues.

New discussion

Ask questions and get answers to your physical security questions from IPVM team members and fellow subscribers.

Newest discussions