Updating firmware on cameras and Network Video Recorder (NVR) to ensure the latest security patches and features are in place.
It's always best to keep cameras and NVR up to date. Unfortunately there are bugs reported from time to time in firmware updates. There will be many systems out there that get installed and just left, never updated and that's where risk lies.
Establishing a robust, randomly generated password for the admin user to prevent unauthorized access.
Again easy to do. It's a shame that the 'admin' username cannot be changed to further enhance security and thats something that has been communicated to Hikvision by use-ip staff previously I believe (as one of Hikvision's own security hardening white papers details it but doesn't implement it in it's own systems). If port forwarding or UPnP are not in use, and the NVR/DVR/Camera http interface are not accessible from the internet, the password on the NVR/DVR is preventing access to the local interface or from the LAN.
Avoiding port forwarding by utilizing Hik-Connect for remote access, enhancing security by minimizing direct exposure to the internet.
For viewing remotely, port forwarding is no longer necessary/advised. An issue arises if remote configuration is needed...
Hikvision have come up with Hik Partner Pro allowing installers to access systems without port forwarding required and with the ability of the end user to control access (allowing/revoking of permissions from within their Hik-Connect app). It's a nice concept but currently is lacking in number of areas. Slow access, many menu items inaccessible using the platform, firmware updates limited to security patches rather than being able to remotely load a general release firmware file. Hikvision have decided to charge installers per site for this service. That might be fine for installers dealing with commercial installations where ongoing maintenance plans are in place. However for smaller installers dealing primarily with residential systems it doesn't work. The inability to be able to access all programming features that are available by browser and the cost will likely push installers back to using port forwarding.
Isolating the NVR within a dedicated and segregated VLAN, limiting potential network vulnerabilities.
Beyond the scope of most home users; some users will create an IoT VLAN for all devices that need to 'call home' to internet services (TV's, smart home devices etc)
Activating stream encryption to protect video data integrity and confidentiality.
Adds security but also adds some latency and sometimes can cause glitches in the images when viewed in the app.
Enabling HTTPS browsing on the NVR, securing web interface communications.
Certainly worthwhile if there needs to be port forwarded access to the device web interface to prevent username and passwords being transmitted unencrypted.
@Sunchaser I think you've probably implemented more with regard to securing the system than most users (or even installers) would bother with, certainly for a domestic system.
As has been mentioned before, there's a balance between network security and convenience. Many are concerned about access to the CCTV system but are more than happy to have Amazon, Google and other devices connected to their network; listening in around the home and recording every journey they've made/location they've visited with their smartphone.