i-PRO Frames Cybersecurity as a Core Utility Physical-Security Requirement

A vendor briefing, with a broader infrastructure implication

i-PRO published a blog post on September 8, 2026 arguing that cybersecurity deserves the same early consideration as physical protection when utilities deploy cameras, radar and other connected security equipment. The briefing focuses on substations, transmission assets and remote locations where surveillance technology may improve situational awareness but also becomes part of the organization’s connected attack surface.

The point is especially relevant to installations where security devices share communications infrastructure with business systems, site operations or third-party maintenance connections. A network camera is not simply a perimeter-security endpoint once it is addressable, remotely administered, integrated with a video platform or connected through a field network. Its access controls, firmware state, certificates, logs and communication paths become design considerations.

Remote sites need an architecture review, not a device-only review

For an integrator, specifying a rugged camera, long-range wireless link or radar system is only part of the utility-site design. The accompanying questions are architectural: Which network zone will host the device? What systems may initiate connections to it? Is video routed through a controlled intermediary? How are installers and service personnel granted, logged and removed from remote access?

CISA’s operational-technology guidance advises critical-infrastructure organizations to secure essential remote access, use strong authentication and apply least privilege. It also calls for IT and OT segmentation and a demilitarized zone where control information must pass between enterprise and operational environments. These practices are not camera-brand requirements; they are deployment disciplines that can reduce the consequences if an endpoint or credential is compromised.

What to place on the security-device checklist

i-PRO identifies encrypted communications, signed firmware, secure boot and protected credential storage as controls utilities should seek in modern connected security devices. Those categories make a useful starting point for a submittal or basis-of-design checklist, provided that the project team verifies the actual capabilities of the selected model and software release.

A practical review should document supported authentication methods; certificate handling; encrypted management, video and API interfaces; account roles; password and credential-change procedures; audit logging; firmware signing and verification behavior; and the process for disabling unused services. Teams should also identify dependencies such as video management software, mobile applications, cloud connectors, network switches and cellular or wireless gateways. The security posture of the overall system will be limited by the weakest exposed integration path.

Do not turn broad standards references into product claims

The i-PRO post encourages utilities to prioritize technologies aligned with NIST guidance and mentions FIPS 140-3 Level 3 compliance. Procurement teams should ask suppliers to identify precisely what is covered by any claimed certification or validation: the product model, firmware version, cryptographic module, operating mode and validation status. A general reference to a framework or cryptographic standard does not, by itself, establish that every device in a proposed surveillance system has a particular certification.

This distinction matters in utility projects because compliance scope varies. NERC’s CIP-011-3, for example, addresses protection of Bulk Electric System Cyber System Information. It should not be read as an automatic declaration that every surveillance deployment is in scope. Utility owners and their compliance, OT and security teams need to determine applicability based on the systems, information and architecture involved.

Lifecycle support is part of the equipment decision

i-PRO also stresses continuous maintenance as vulnerabilities and attack methods change. That is an important procurement issue: a security device may remain installed for years after initial commissioning, often in difficult-to-reach locations. The bid evaluation should therefore cover support duration, firmware availability, security-advisory publication, vulnerability-reporting channels, update methods, rollback procedures and the operational impact of maintenance windows.

A useful acceptance plan can require an accurate asset inventory at handoff, including model and serial information, network addresses, firmware versions, enabled services, administrative ownership and documentation of approved communication flows. Those records support patch planning and help incident responders determine whether an affected device is present and reachable.

The specification opportunity for utilities and integrators

The immediate news is i-PRO’s September 8 briefing, rather than a new mandatory rule or a disclosed incident. Still, it reflects a practical change in how utility physical-security projects should be framed. Detection performance, environmental ratings and coverage design remain essential, but cyber controls should be addressed at the same design milestone—not after equipment is online.

For remote utility assets, the strongest outcome is a joint physical-security and OT/IT review before purchase orders are released. That review can define segmentation boundaries, approved remote-service workflows, ownership of credentials and certificates, logging destinations, update responsibilities and the evidence required for final acceptance. Doing so gives installers clear commissioning requirements and gives operators a more manageable security system over its service life.