A hospital corridor clock, warehouse display or school classroom clock may look like simple equipment, but its security profile depends entirely on how it receives time. Are clocks cybersecure? A battery-powered quartz clock has no network connection to attack. A synchronised WiFi, PoE or network time system, however, is part of the wider digital estate and should be specified accordingly.
For facilities and estates teams, the practical question is not whether every clock needs a cyber security assessment of the same depth. It is whether the clock system can be trusted to show the correct time, whether it introduces an avoidable route into the network, and whether it can be supported safely throughout its working life.
Are clocks cybersecure by design?
No connected product is automatically cybersecure simply because it is supplied for commercial use. Security is a combination of product design, installation method, network configuration and ongoing management. The appropriate level of control also varies by application.
A conventional analogue battery clock is not a cyber asset. It has no IP address, does not connect to a wireless network and cannot be accessed remotely. Its main risks are operational: a flat battery, accidental adjustment, damage or gradual time drift. For isolated locations or straightforward applications, that simplicity can be a genuine advantage.
A synchronised clock system addresses different operational needs. In a healthcare setting, for example, consistent time across wards, treatment rooms and public areas supports coordinated activity. In education, transport and logistics, a common time reference helps manage lessons, departures, shift changes and production schedules. To achieve this, clocks may receive time via a dedicated wireless signal, a network time protocol source, WiFi or Ethernet with Power over Ethernet.
The more connected the system, the more carefully security needs to be considered. That does not make networked clocks unsuitable. It means they should be treated as managed operational devices rather than as ordinary wall fittings.
The connection method changes the risk
Battery and dedicated wireless clocks
Battery clocks operating independently present the lowest cyber exposure because there is no digital connection. They may be appropriate where synchronisation is not essential, or where a small number of clocks can be maintained locally.
Dedicated wireless synchronised systems can offer a useful middle ground. A central transmitter sends time to compatible clocks over a purpose-designed radio signal rather than joining every clock to the organisation’s IT network. This reduces the number of network endpoints, although the installation should still consider radio coverage, signal resilience, transmitter security and the consequences of incorrect time being transmitted.
Wireless does not automatically mean WiFi. This distinction matters during specification. A proprietary radio synchronisation system and a WiFi clock system have very different infrastructure, administration and cyber security requirements.
WiFi clocks
WiFi clocks connect through the organisation’s wireless network, often obtaining time from an approved time source. They can be efficient where suitable coverage already exists and where cabling would be disruptive or costly. They also create an endpoint on the wireless estate.
A WiFi clock should use current, organisation-approved wireless security settings and be placed on an appropriate network segment. It should not rely on a shared guest network, outdated encryption or default credentials. The IT team should be able to identify the devices, control which services they can reach and remove access when equipment is replaced.
For large sites, wireless capacity is also a practical consideration. A clock may use little data, but hundreds of devices still need addressing, onboarding and monitoring. The right solution is the one that fits both the operational requirement and the network team’s support model.
PoE and wired network clocks
PoE clocks receive power and data through a single Ethernet cable. This can simplify installation, avoid routine battery changes and provide dependable connectivity in buildings where cabling is practical. It also makes the clock a physical network endpoint.
Wired connectivity is not inherently safer than WiFi, but it can be easier to control in some estates. Switch ports can be assigned to a dedicated VLAN, disabled when not in use and monitored by the network team. A properly designed PoE installation also considers switch capacity, backup power arrangements and cable routes, particularly where time displays are needed during an incident or power disruption.
Security starts with the time source
A clock is only as trustworthy as the time it receives. If an unauthorised or unreliable source can alter that time, every connected display may become wrong together. For an office this may be inconvenient. In clinical, transport, manufacturing or examination environments, it can be materially disruptive.
The central time source should be approved and controlled. Depending on the system, this may be a local master clock, a GPS or GNSS receiver, or a managed network time source. The design should define which source is authoritative, what happens if it becomes unavailable, and how the system detects a loss of synchronisation.
Where Network Time Protocol is used, clocks should be directed only to approved internal or external sources. Unnecessary access to the wider internet should not be assumed. Restricting devices to the services they genuinely require reduces exposure and gives IT teams clearer control of traffic.
Accuracy and security are linked here. A system that is well protected but has no resilience against loss of signal can still fail operationally. Equally, a highly accurate external source is not enough if devices can be redirected to an untrusted one.
What good clock-system security looks like
For commercial buyers, cyber security should be part of the specification rather than a last-minute IT query. The supplier, electrical contractor, network team and facilities lead all have a role. The supplier should explain how the system communicates; IT should determine how it is admitted to the network; and the operational owner should define the consequence of lost or incorrect time.
A sensible design normally includes network segmentation, restricted communications and controlled administration. Clocks do not usually need broad access to business systems, email, file shares or internet services. Place connected clocks in a suitable device network or VLAN and permit only the traffic required for time synchronisation and management.
Default usernames and passwords should be changed before handover where applicable, with credentials held under the organisation’s normal access-control process. Management interfaces should be disabled if they are not required, or limited to authorised administrators. If a device supports encrypted administration, current firmware and event logging, these features should be assessed against the site’s policies rather than left unconfigured.
Physical security matters too. A network clock installed in a public reception, school corridor or warehouse must not provide easy access to an exposed live Ethernet port. Cabling, switch ports and local controllers should be protected in the same way as other building technology.
Questions to ask before specifying connected clocks
Before selecting WiFi or PoE clocks, ask the supplier and internal IT team how the devices obtain time, how they are commissioned, and whether they require an ongoing management platform. Establish whether fixed IP addresses, DHCP reservations or another approach will be used, and who owns that configuration after installation.
It is also sensible to ask about firmware support. Connected equipment can remain installed for many years, so buyers need clarity on available updates, how updates are applied, whether they cause interruption, and what happens when a model reaches end of support. A low purchase price is less attractive if the device cannot remain acceptable within future security policy.
For critical areas, ask how the system behaves during loss of network connection, power failure or a time-source fault. Some clocks can continue displaying time from an internal reference and resynchronise later. The required behaviour depends on the site. A clock in a staff room and a clock supporting timed clinical activity should not necessarily be specified to the same resilience standard.
Finally, document the clock estate. Record device location, model, connection method, network segment, time source and responsible team. This makes routine support easier and prevents connected clocks becoming forgotten devices on the network.
Selecting proportionate protection
The aim is not to force every commercial clock into a complex IT project. It is to match the technology to the environment. A small community hall may be well served by reliable battery clocks. A multi-building school may benefit from a dedicated wireless synchronised system that avoids placing every clock on WiFi. A hospital, transport hub or large distribution site may require networked clocks integrated with controlled infrastructure and a resilient time source.
The most effective installations begin with operational requirements: where time must be visible, how accurate it needs to be, how many displays are involved, what infrastructure exists, and what level of cyber control the organisation requires. From there, the appropriate clock technology becomes clearer.
Treat connected clocks as part of the building’s operational technology estate, and they can deliver consistent, visible time without becoming an overlooked weakness.