Camera-management servers need the same security care as business IT
5 November 2026
Review camera server security after Huntress incident analysis, with checks for supported software, service accounts, vendor access and recovery.
Huntress has published incident analysis describing attackers compromising camera-management software, deploying malware, maintaining access and communicating with attacker-controlled infrastructure. For Australian businesses running CCTV management servers, the practical lesson is straightforward: camera server security belongs in the IT security programme, not only the physical security maintenance contract.
The Huntress incident analysis is the source for the reported attack chain and indicators of compromise. The checks below are broader defensive recommendations, not claims about the specific entry point or software involved in that incident.
Put camera server security under a named owner
A camera-management server can hold recordings, camera credentials, remote support tools and connections to other business systems. Depending on its configuration, compromising it may create opportunities beyond interrupting video surveillance.
The ownership gap matters. A security installer may maintain cameras while an IT provider assumes the recording server sits outside its scope. Meanwhile, nobody checks whether endpoint protection is working or whether an old support account remains active.
Assign a business owner and a technical owner. Record who is responsible for:
- Operating system and camera-management application updates.
- Service accounts, administrator permissions and vendor access.
- Endpoint monitoring and investigation of alerts.
- Configuration backups, recording retention and recovery testing.
- Approving downtime that affects surveillance coverage.
Ask both providers to confirm the boundary in writing. A server should not disappear from the asset register because it was purchased as part of a CCTV installation.
Confirm software support before scheduling updates
Start with an inventory of the management application, underlying operating system, recording components, installed plug-ins and remote support software. Record versions and support status, rather than relying on a statement that the system is “maintained”.
Ask the supplier for the supported upgrade path and compatibility requirements. An application update may depend on a newer operating system, database component or camera firmware. Confirm licence entitlements and obtain installation media before making changes.
For each server, check:
- Is the operating system still receiving applicable security updates?
- Does the vendor support the installed application version?
- Are security advisories reaching someone who can act on them?
- Is there a tested backup and documented rollback procedure?
- Can updates be scheduled without leaving critical areas unmonitored?
Unsupported software needs a replacement plan with an owner and a deadline. Restricting connectivity can reduce exposure while replacement is organised, but does not make unsupported software safe indefinitely. Patching also does not remove persistence from an already compromised server.
Restrict service accounts to the work they perform
Camera services often need to start automatically, write recordings and communicate with devices. Those requirements do not automatically justify domain administrator access or unrestricted access to business file shares.
List the identities used by recording services, application services, scheduled tasks and storage connections. Establish what each identity actually needs before reducing permissions with the supplier's involvement.
Use dedicated accounts rather than a staff member's login. Avoid reusing credentials across unrelated servers. Where supported, use managed service accounts or an appropriate credential-management process. Restrict interactive sign-in for service identities when the application permits it.
Check recording storage permissions carefully. An account writing video to one storage location should not also have write access to finance or operational documents. Document any vendor-required elevated permissions and review whether a supported alternative exists.
Treat credential rotation as a planned change. Updating a password without updating dependent services can stop recording. After a change, verify live views, recording, playback and retention behaviour.
Make vendor access deliberate and traceable
Remote maintenance is useful, but a permanently available support path increases the number of ways into a camera server. Camera server security should include every access method, including remote desktop, VPN connections, vendor portals and remote management tools.
Ask the installer to demonstrate how support staff connect. Identify which accounts they use, where authentication occurs and what logs your business can obtain.
Prefer named identities, multi-factor authentication at the access gateway, restricted destinations and time-limited access where supported. Remove accounts belonging to former technicians and disable access that no longer has a business purpose.
Avoid directly exposing management interfaces or remote desktop services to the internet. Use a controlled access path and document any unavoidable exceptions. Do not leave an unmanaged remote tool installed merely because it was useful during commissioning.
For a wider review of support software, use our remote access and RMM checklist. The objective is accountable access, not making legitimate maintenance impractical.
Separate cameras, servers and everyday business systems
A camera network should not provide unrestricted access to staff devices, business servers or backup administration interfaces. Equally, a compromised workstation should not automatically be able to administer the CCTV environment.
Map the required traffic between cameras, recording servers, viewing workstations, storage, update services and support gateways. Then restrict communication to those documented needs.
A separate VLAN is only part of the job. Firewall rules or equivalent controls must enforce which systems can communicate. Review outbound access too: a recording server may need specific vendor services, but not unrestricted internet connectivity.
Test changes against live viewing, recording, playback, time synchronisation and approved remote support. Our network segmentation checklist explains how to turn network separation into enforceable boundaries.
Monitor the server, not just camera availability
An alert that a camera has stopped recording is not the same as detecting malware on the management server. Camera server security needs visibility into the host's activity as well as surveillance system health.
Deploy supported endpoint detection and response tooling where the platform allows it. Confirm that the server reports to the monitoring console and that someone is responsible for investigating alerts.
Useful investigation signals include unexpected processes launched by camera software, new services or scheduled tasks, unfamiliar remote access tools, unusual administrator sign-ins and connections to unexpected external destinations. These require context: legitimate updates can also create services or change network activity.
Check antivirus and endpoint protection exclusions. Performance concerns should lead to narrow, documented exceptions, not blanket exclusion of application folders or drives. Our Defender exclusions audit provides a practical starting point.
Use the indicators published by Huntress to guide investigation where relevant, but do not treat a clean indicator search as proof that the server is uncompromised.
Plan recovery around both evidence and surveillance
Recovery arrangements should cover application configuration, camera enrolment, licences, credentials, storage mappings and installation media. Decide separately which recordings need protection and how long they must be retained.
Protect backups from the server's everyday accounts. Test whether a replacement server can restore configuration and resume recording. A backup job marked successful does not establish that licences, credentials and camera connections will work after restoration.
If compromise is suspected, coordinate containment with the people responsible for site security. Isolating a server may interrupt live monitoring or recording, so arrange temporary coverage where needed. Preserve relevant logs and evidence with incident-response guidance before wiping systems.
Where system integrity cannot be established, plan a rebuild from trusted media rather than assuming malware removal is sufficient. Review connected systems and exposed credentials before restoring access.
Review your CCTV environment as part of cyber security
Start with one camera-management server: confirm its owner, support status, permissions, remote access paths, monitoring coverage and recovery process. Assign unresolved gaps to someone with authority to close them.
Tech Engine Australia provides cyber security, managed IT and CCTV services. To review your cyber security across camera-management servers and connected business systems, call 1300 088 324, email sales@techengine.au or visit aiaas.au.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint