How to secure AMI gateways and smart meters that attackers can physically reach, open and probe.
An AMI rollout turns a utility's metering estate into a fleet of small, networked computers mounted in cabinets, on walls and on poles. Unlike servers in a data center, each one can be reached, opened and probed by anyone willing to take the risk. AMI network security therefore starts from an uncomfortable assumption: the attacker may have the hardware in hand.
What Changes at Grid Scale
- Physical access: devices sit in the field, not behind a locked data-center door.
- Long service lives: meters stay installed for a decade or more, so keys and firmware must be replaceable remotely.
- Blast radius: a credential extracted from one device must never open the rest of the fleet.
Each of these pushes the design the same way. Security has to be a property of every individual device, enforced locally, rather than a perimeter the utility hopes will hold.
Hardening the Gateway
We start every deployment from the same baseline: a read-only root filesystem, a signature on every firmware image and a unique identity for each node. A read-only root means a tampered gateway returns to a known state when it reboots. Signed images mean the device refuses any code the operator did not release. Per-device identity means revoking one node leaves every other node untouched.
# mount the root filesystem read-only; writable state lives in a signed overlay
mount -o remount,ro /
# verify the firmware signature before applying an update
cosign verify-blob --key /etc/keys/fleet.pub --signature fw.sig firmware.binAssume every field device will eventually be in an attacker's hands, and design so that fact changes nothing for the rest of the grid.
Containing the Network Path
Encrypted peer-to-peer tunnels between nodes and the hub complete the design. Traffic from a compromised meter stays inside its own tunnel, cannot be used to reach neighboring devices and can be cut off by revoking a single certificate. That containment is what separates a maintenance ticket from a public incident.
Tagged Under

KoderTroop Systems Squad
Technical Authors
Articles are written by KoderTroop specialists and architects who design and deliver embedded systems, cloud platforms, edge computing and applied AI for our clients.