i-PRO Puts Cybersecurity in the Utility Camera and Radar Specification Process

A utility-security message, not a new product announcement

On September 8, 2026, i-PRO published a utility-focused cybersecurity briefing arguing that physical-security technologies must be evaluated as connected computing assets. The company’s discussion covers cameras, radar sensors and other networked devices used around substations, transmission assets and remote critical-infrastructure sites.

The central point is straightforward: detection performance alone is not a sufficient basis for specifying a connected security endpoint. The manufacturer says the assessment should also cover protections in hardware and software, the communications architecture and the vendor’s ability to maintain the device as threats and vulnerabilities change.

The post does not announce a new i-PRO product, a vulnerability, or a newly issued certification. Instead, it is a specification and operating-practice message aimed at utility security teams and their integrators.

Connected security endpoints belong in the cyber risk picture

A camera or radar unit that is assigned an address, managed remotely, exchanges video or telemetry, or receives firmware is part of the organization’s attack surface. That does not make every endpoint an OT controller, but it does mean the endpoint needs to be discovered, governed and protected as a networked asset.

This framing is consistent with NIST’s operational-technology guidance. NIST includes physical access-control and physical-environment monitoring systems among the technologies that may require OT security considerations, while recognizing that availability, reliability and safety needs shape the security design.

For project teams, the practical consequence is to involve the organization’s cybersecurity and network stakeholders before selecting cameras, sensors, video recorders or management platforms. This helps identify whether the security system will be isolated, use a dedicated segment, connect through a demilitarized zone, or require tightly controlled access to other environments.

Specify security controls as verifiable requirements

i-PRO identifies encrypted communications, digitally signed firmware, secure boot and secure storage for credentials as relevant safeguards. These should be converted from broad marketing terms into acceptance criteria during design and procurement.

Installers and owners can ask vendors to document supported cipher and protocol settings, the firmware-signing and secure-boot chain, account and certificate management, disabled-by-default services, audit logging and hardening instructions. They should also establish who is permitted to administer each device, how remote support will be enabled, and how credentials will be changed when an installer or service provider changes.

Requirements must match the site risk assessment. For example, a remote substation with constrained communications and limited physical access may place particular value on secure local recovery procedures, a documented update method and clear device inventory information. A device’s feature list is not a substitute for an architecture that limits unnecessary connections and privileges.

Network design is part of physical-security design

NIST recommends segmentation or zoning as part of a defense-in-depth OT architecture, organizing devices by location or function and restricting communications through gateways and firewalls. CISA likewise advises critical-infrastructure organizations to place OT assets into logical zones, define approved conduits between them and control and monitor the resulting traffic.

For a surveillance or radar project, that suggests documenting data flows early: device-to-recorder traffic, management access, time synchronization, directory or certificate services, video-client connections, cloud connections and vendor support pathways. Each flow should have an owner and a justified destination. Unneeded ports, protocols and services should be removed or disabled where operationally feasible.

Segmentation is not an argument for an unmaintained isolated network. Security endpoints still need controlled processes for firmware updates, vulnerability review, backups and incident response. The goal is to reduce exposure and lateral-movement opportunities without impairing the security system’s required availability.

Treat lifecycle support and FIPS claims carefully

i-PRO also emphasizes continuing firmware maintenance and alignment with evolving cybersecurity frameworks. Buyers should ask for a support lifecycle statement, a vulnerability-disclosure channel, advisory history, expected update cadence, end-of-support dates and the process for applying updates at sites where outages must be planned. These items are especially important for equipment intended to remain in service for many years.

The briefing references NIST guidance and FIPS 140-3 Level 3 compliance. Procurement teams should distinguish a cryptographic-module validation from a blanket claim that a camera, radar sensor or surveillance system is certified. FIPS 140-3 defines security requirements for cryptographic modules, and validation depends on the specific module and, in some cases, its documented installation and operating configuration.

The most useful outcome from i-PRO’s message is a broader bid-review discipline: evaluate the endpoint, its management plane, its permitted communications and its maintenance commitment together. That approach better reflects the role connected physical-security equipment can play in a utility’s overall resilience.