October is Cybersecurity Awareness Month. Most organisations will spend it on phishing training and password reminders. Both matter. But there is a category of device on most corporate networks that rarely gets mentioned: the security systems themselves.
IP cameras, video recorders, access control controllers and servers, intercoms and visitor management systems are all networked computers. They run firmware, they need patching, and many are reachable remotely for maintenance. They also tend to fall between two teams. IT assumes the security contractor looks after them. The security team assumes they are covered by IT’s processes.
We made the wider argument earlier this year in why your physical security system is your next cybersecurity battleground. This is the practical version: five checks worth running this month.
1. Are the devices on an asset register?
You cannot patch what you do not have listed. Every camera, controller, recorder and server should be on a register with its model, firmware version and location. In many estates the only complete list sits with the integrator, if anywhere.
2. Are they in your vulnerability scanning and penetration testing scope?
If your last pen test excluded the security network, you don’t know what an attacker would find there. Agree the scope with your integrator first: some older devices behave badly under aggressive scanning, and nobody wants a door controller to reboot mid-test.
3. When was firmware last updated?
Manufacturers publish security fixes regularly. A device several versions behind is carrying vulnerabilities that are already documented publicly. Agree an update cycle with whoever maintains the system, and write it into the maintenance contract.
4. Who has remote access?
Remote access is how systems get maintained efficiently, and how they get compromised. List every route in: vendor support tools, integrator VPNs, cloud management portals, and the people who hold each credential. Remove anything that isn’t needed, and make sure what remains uses individual accounts and multi-factor authentication where the platform supports it.
5. Is the security network actually separate?
Many designs put security devices on their own VLAN. Fewer have tested whether that separation holds. Check that a compromised camera could not reach the corporate network, and that the corporate network cannot reach the cameras beyond what the video management system needs.
Don't forget the servers
One date is worth adding to your list: Microsoft ends extended support for Windows Server 2016 on 12 January 2027. Access control and video management servers installed in the late 2010s often run on it, and they are often missing from IT’s upgrade plans.
Two teams, one conversation
None of these checks needs new technology. They need IT and security to agree who owns what, and an integrator willing to answer the questions. If yours can’t tell you the firmware version of every device on your estate, that’s the first thing to fix.
If you’d like a second opinion on where your security estate stands, speak to our team.
