Back

Physical access control is changing. In utilities and critical infrastructure, access decisions are no longer based only on whether someone has a valid badge or credential. Increasingly, they depend on information coming from other business systems, such as identity management platforms, contractor databases, maintenance software, work orders, training records, and operational schedules.

As a matter of fact, a technician should not automatically be allowed to enter a substation, pumping station, or remote technical site simply because they are registered in the access control system. Access may also depend on whether they have been assigned a specific task, hold the necessary certifications, are responsible for that asset, and are expected to be onsite at that time.

By combining this information, organisations can make access decisions that are more accurate, more secure, and better aligned with operational needs.

Every integration creates trust

When a physical access system relies on information from other applications, it is effectively trusting those systems. The access control system relies on the accuracy of the identity information it receives: it relies on employee and contractor status being current, on work orders being valid and up to date, and on qualifications, certifications, and permissions being correctly maintained.

Ultimately, this trusted information can result in a real action: unlocking a door, gate, cabinet, or technical enclosure. For this reason, integration should never be viewed as simply connecting two applications. Behind every interface are data flows, user permissions, administrative processes, synchronisation rules, and system responsibilities that need to be clearly defined.

Organisations should ask practical questions:

  • Which system is the authoritative source of information?
  • What happens if data is inconsistent between systems?
  • How quickly can permissions be revoked?
  • What happens if one platform becomes unavailable?

For utilities managing large numbers of geographically distributed assets, these questions are critical to both security and operational continuity.

Integration does not mean connecting everything

One common misconception is that a highly integrated architecture requires every physical access point to be permanently connected to the network. In reality, integration and connectivity are two different concepts.

At the management level, integration delivers significant benefits. Access rights can be linked to identities, job roles, maintenance activities, contractor assignments, or work orders. Permissions can become temporary, task-specific, and automatically aligned with operational requirements.

However, at the field level, connectivity should only be introduced when it provides a clear operational or security advantage. Utilities often manage remote substations, water facilities, telecom sites, and outdoor technical cabinets located in environments where connectivity and power availability can be limited. Permanently connecting every access point increases infrastructure complexity and creates additional devices that must be maintained, secured, monitored, and updated.

A more balanced approach is to separate centralised access management from the physical locking technology deployed in the field. This is the principle behind the ISEO LSA and F9000 architecture. LSA acts as the intelligent management platform, integrating with corporate and operational systems. F9000 allows access authorisations to be securely distributed to remote access points without requiring every lock to be continuously connected to a network or power source. As a result, organisations can benefit from integration while avoiding unnecessary expansion of their digital attack surface.

The goal is controlled dependency

Modern utilities cannot operate without interconnected systems. The objective is therefore not isolation, but control. Organisations need to understand the dependencies created by integration and ensure those dependencies are intentional, manageable, and auditable. This means applying well-established cybersecurity principles such as:

  • Least privilege access
  • Clear ownership of data and permissions
  • Restricted administrative access
  • Full traceability of activities
  • Rapid revocation of rights
  • Resilience when communications or external systems fail

Equally important is understanding the operational impact of these principles. A system that is highly secure but prevents technicians from accessing a critical site during a communications outage is not truly resilient. Conversely, a system designed purely for operational convenience may create excessive permissions and reduce accountability. The challenge is finding the right balance between security, availability, and operational efficiency.

When integration becomes part of the security architecture

As physical access becomes increasingly connected to IT systems and operational processes, selecting an access control solution is no longer just a product decision. It requires a partner that understands physical security, digital identity, system integration, cybersecurity, and the operational realities of critical infrastructure.

Organisations must determine not only what should be connected, but also what does not need to be connected and what must continue functioning even when networks or external systems are unavailable.

Because once physical access becomes part of the broader digital ecosystem, integration itself becomes part of the security architecture. And in critical infrastructure, good integration should always reduce uncertainty, not introduce it.