In an increasingly interconnected world, government facilities — from municipal buildings and schools to libraries and critical infrastructure sites — face mounting threats that blur the distinction between the physical and cyber domains. Traditional security measures such as alarm systems and CCTV are now deeply integrated with operational technology (OT) and Internet of Things (IoT) networks, exposing them to sophisticated cyber risks. This article explores how adopting a Secure-by-Design (SbD) approach can strengthen these systems, drawing on guidelines from organisations such as the Australian Cyber Security Centre (ACSC) and the Australian Signals Directorate (ASD). By embedding security from the outset, public sector entities can mitigate vulnerabilities, ensure resilience and comply with evolving standards.
The convergence of physical security and IT networks has transformed the installation of alarms from a straightforward hardware task into a complex and risky process. Whereas it used to be about wiring sensors and cameras, it now involves integrating IP-based devices that communicate over shared networks, which could potentially open the door to remote exploitation. For example, a compromised CCTV camera could be used by attackers to infiltrate broader institutional systems, leading to data breaches or operational disruptions. This shift means that alarm installation must be approached with cybersecurity in mind, incorporating principles such as encryption and access controls from the design phase onwards in order to prevent such cascading failures.
Why physical security equals cybersecurity for government objects
Integrating alarm and CCTV systems with institutional networks is a critical convergence point where physical safeguards can be exploited by cyber threats. This ‘physical = cyber’ paradigm is particularly pertinent in the public sector, where facilities frequently constitute critical infrastructure. According to cybersecurity experts, the transition from analogue to IP-based systems nearly three decades ago accelerated this convergence, enabling centralised monitoring but also introducing vulnerabilities such as unauthorised access to video feeds or manipulation of alarm triggers.
The risks to critical infrastructure are amplified when these systems are connected to OT/IoT environments. For instance, a compromised network video recorder (NVR) could render surveillance ineffective during a physical intrusion or even enable adversaries to steal sensitive data. Incidents in the public sector highlight this danger. Reuters has reported on cases where state-sponsored actors have targeted utility grids and government buildings by exploiting IoT devices as weak links. In one notable incident, cybercriminals compromised CCTV networks in a European municipality and used them to launch DDoS attacks on national infrastructure. Similarly, reports from the US highlight how physical security lapses, such as unpatched alarm panels, have enabled ransomware infiltration in schools and libraries, resulting in operational disruption and substantial recovery costs.
Convergence also increases the importance of critical sectors. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) emphasises that organisations with integrated cybersecurity and physical security measures in place are more resilient and better equipped to prevent, mitigate and respond to threats. In Australia, the Australian Cyber Security Centre (ACSC) warns of supply chain risks in OT systems, where compromised vendors could embed backdoors in CCTV firmware. These examples demonstrate the need for government entities to treat physical security as an extension of cyber defence, mandating comprehensive risk assessments that consider both domains.
Applying the principles of secure-by-design to alarm systems
Secure-by-Design (SbD) requires security to be incorporated from the outset and treated as a core constraint alongside usability and cost. In the context of alarm and CCTV systems, this involves designing architectures that anticipate attacks, minimise attack surfaces and enable rapid recovery. Key principles include:
- segmentation, which isolates OT zones from IT networks to contain breaches
- minimisation of exposure, whereby only essential interfaces are exposed
- updateability, achieved through over-the-air firmware patches
- robust logging for audit trails
- vendor verification, to ensure supply chain integrity
Drawing from ACSC/ASD recommendations, it is clear that segmentation is crucial for alarm systems. By creating air-gapped or virtually segmented zones, organisations can prevent attackers who compromise a single sensor from moving laterally through the system. Minimisation involves disabling unnecessary ports on CCTV cameras to reduce potential entry points. The ability to update ensures that devices such as alarm panels can receive security patches without downtime, which counteracts zero-day exploits that are common in the Internet of Things (IoT).
Logging and monitoring are emphasised in the ASD Principles of Operational Technology Cyber Security, which advocate comprehensive event logging to detect anomalies such as unauthorised access attempts. Vendor verification aligns with CISA’s guidance on selecting secure technologies, involving audits of suppliers’ security by design (SbD) practices to prevent vulnerabilities from being embedded. For government sectors, these principles are not optional: they form the basis of frameworks such as NIST SP 800-160, which promote layered defences and least privilege access.
In practice, applying security by design (SbD) to alarm systems means starting with threat modelling during the design process. For CCTV systems, this could involve implementing default-deny policies, whereby cameras only communicate with verified video management systems (VMS). The Australian Cyber Security Centre’s (ACSC) IoT Secure-by-Design guidance for manufacturers reinforces this approach, outlining thirteen principles, including the absence of default passwords and the implementation of secure boot mechanisms. By adhering to these principles, public entities can build systems that are resilient to evolving threats, such as ransomware targeting OT.
Architecture: From sensor to PSIM/VMS
A secure architecture for alarms and CCTV systems spans from edge devices, such as sensors and cameras, to centralised platforms like Physical Security Information Management (PSIM) or Video Management Systems (VMS). Network zones should be prioritised in topologies, with OT isolated from IT via firewalls or VLANs to prevent cross-contamination. All data in transit, from sensor alerts to video streams, must use encryption protocols such as TLS 1.3.
The remote access of contractors poses significant risks, making Zero Trust models necessary. Zero Trust Architecture (ZTA) assumes no implicit trust and verifies every request, regardless of its origin. In this setup, a contractor accessing an alarm panel would undergo multi-factor authentication (MFA), micro-segmentation and continuous monitoring. ZTA applies granular policies to subsystems: for example, a CCTV camera might only access the VMS, not the broader network.
Secure data aggregation is involved in the flow from sensors to PSIM/VMS. Sensors use encrypted channels to report to edge gateways, which then forward the data to zoned servers. PSIM integrates alarms, CCTV and access controls; however, with SbD, it also incorporates AI-powered anomaly detection to identify unusual patterns. ASD/ACSC endorse such topologies in their OT cybersecurity principles, emphasising defence in depth. Implementation may involve the use of hybrid clouds for VMS, alongside on-premises NVRs for sensitive sites, to ensure compliance with data sovereignty laws in government contexts.
Standards and processes for government institutions
Government institutions must ensure that their alarm and CCTV deployments adhere to rigorous standards. The ACSC/ASD Information Security Manual (ISM) provides a framework that mandates access policies enforcing role-based controls and regular audits. IoT inventory is foundational. CISA’s OT asset guidance recommends mapping all devices, including cameras and panels, in order to identify vulnerabilities.
The log requirements stipulate centralised collection with a retention period of at least 12 months to enable forensic analysis. NIST SP 800-61 outlines the incident response process, emphasising the preparation, detection and recovery phases. Testing involves regular penetration tests and tabletop exercises designed to simulate breaches.
Processes include ongoing monitoring via Security Operations Centres (SOCs) and the integration of SIEM (Security Information and Event Management) for real-time alerts. In the public sector, compliance with frameworks such as NIST SP 800-213 for federal IoT ensures a minimum level of security. These standards promote a culture of proactive security and reduce downtime in critical facilities.
Case studies of quick wins in municipalities, libraries, and schools
Although specific case studies are scarce, practical ‘quick wins’ demonstrate rapid improvements. For example, implementing MFA for cloud-based alarm panels in a U.S. municipality took four weeks and thwarted brute-force attacks. In a library, isolating NVRs via network segmentation prevented the spread of malware, which was achieved in six weeks with minimal disruption.
Schools have updated the firmware on their CCTV cameras en masse, addressing known vulnerabilities within a month. Incident response plans have been swiftly developed, often using ACSC templates, and include escalation protocols for cyber-physical events. These cost-effective and low-effort measures yield high returns, boosting resilience without the need for overhauls.
For example, an Australian school district isolated IoT devices and enforced firmware updates to reduce exposure to exploits. Municipalities have integrated basic SIEM logging to enable the quick detection of anomalies. These examples demonstrate that targeted actions can secure systems within 4–6 weeks, thereby aligning with the SbD approach for achieving an immediate impact.
Checklist for procurement and acceptance
A robust checklist is required to ensure SbD compliance when procuring alarm and CCTV systems. Key questions for vendors: Do the devices support automatic updates? What encryption standards do they use? Can you provide evidence of third-party security audits?
The RFP should include mandatory Secure by Design (SbD) features such as Zero Trust compatibility and Internet of Things (IoT) inventory tools. KPIs for exploitation should include uptime of at least 99%, patch deployment within 72 hours and zero unaddressed critical vulnerabilities. It is essential that cyber warranties are in place, with vendors guaranteeing remediation for breaches due to design flaws.
Integration with SOC/SIEM is essential. Specify the APIs required for log forwarding and alert correlation. The acceptance criteria are successful penetration testing, a verified vendor supply chain and compliance with ACSC/ASD standards. This checklist protects investments by ensuring that systems are secure from day one.
In conclusion, adopting a Secure-by-Design approach can transform alarm and CCTV systems from vulnerabilities into strengths in the OT/IoT era. By adhering to these principles, architectures and processes, government sectors can safeguard critical assets against converging threats and foster a safer public ecosystem.
Public Spectrum is the first knowledge-sharing platform in Australia to embrace the entire public sector. This website is a platform where you can connect, collaborate, empower, inspire, and upskill with public sector professionals.
- Editors Publicspectrum
- Editors Publicspectrum

