IAM at the End of the Power Cord, Part 3
· 5 min read · Updated
Lire en français
This third part of our series on IAM at the end of the power cord moves from analysis to action, with what we would do if we led an IAM program and your vocabulary translated row by row.
This article follows part one and part two of the series.
What to do if you lead an identity and access management (IAM) program
Inventory critical assets lacking access policies. Not servers or applications, but machines, cabinets, test benches and equipment where unauthorized use carries physical, safety or regulatory impact, and for which you cannot produce an access list or an audit log. In many industrial organizations this list easily rivals the number of governed applications, and it was simply never compiled because it fell outside everyone's scope, too physical for IT and too digital for facility maintenance.
Define denial semantics equipment by equipment with the safety teams. In our experience this is the hardest and most structuring deliverable, because it says, machine by machine, what a denial produces (a stop, a logged continuation or a reduced mode), it dictates the whole architecture, and it cannot be done by the security team alone.
Require an enforcement point capable of offline decision-making. This criterion quickly filters out unsuitable options, because any solution relying on a continuous link to a central service will fail during the first outage, which is precisely the moment when risk is highest.
And one thing not to do: do not connect equipment to the network solely in order to govern it, because physical access control does not require the machine to be smart, it requires the power outlet to be.
Your vocabulary translated
| IAM concept | On a sensitive machine | What breaks |
|---|---|---|
| Subject identity | The person intervening: operator, in-house maintainer, tier-2 subcontractor, OEM field engineer | Usually not in the operator's directory. Federation with no shared IdP, and often no IdP at all on the supplier side. |
| Resource identity | The machine, the cabinet, the test bench | No cryptographic identifier. IEEE 802.1AR-2018 (IDevID/LDevID) is the right normative answer, but it assumes an identity minted at the factory, whereas the installed base has a nameplate. |
| Authentication | Proof that the right person is physically present, here, now | No keyboard, no screen, no browser, so the factor must be carried by the person and validated by a reader external to the machine. |
| Authorization | Role and valid qualification and scheduled work order and zone | De facto ABAC, with one OT specificity, since purpose is a first-class attribute: being qualified is not enough, because you need a legitimate reason to be here now. NERC CIP-004-7 R4.1 puts electronic access and unescorted physical access under a single authorization process. |
| PEP | The actuator that cuts or releases power | Must be physically separate from the machine, or the machine judges its own case. |
| PDP | The policy engine | Must be local. NIST SP 800-207 describes the PEP as "responsible for enabling, monitoring, and eventually terminating connections between a subject and an enterprise resource", which assumes the connection exists, whereas here it does not. |
| Session | The period the machine is energized | Barely exists, because an energized machine stays energized, so it needs continuous re-evaluation, the physical counterpart of CAEP / Shared Signals. |
| Provisioning / JML | Joiner, mover, leaver, but mostly credential expiry | The real OT leaver is a lapsed qualification, not an HR departure. NFPA 70E-2024 §110.4(A)(3) requires requalification at intervals not exceeding three years, and Australia's CIRMP rules require re-vetting of critical workers at least every five years. Note also the distinction NFPA 70E draws in §110.4(A)(1)(b), "a person shall be qualified for certain equipment and tasks to be performed", which is least privilege written into an electrical safety standard. |
| Access review | Recertifying "may energize machine X" | NERC CIP-004-7 R4.2 already mandates verification of unescorted physical access authorizations once each calendar quarter, and outside that regime it is close to nonexistent. |
| Logging | Timestamped, attributed proof of use | NERC CIP-006-6 R1.8: log each individual, with information identifying them and the date and time of entry, and R1.9: retain 90 calendar days. Elsewhere, the only log is the machine's hour counter, which is unattributed, unsigned and reset at maintenance. |
| PAM | The OEM engineer's privileged access | PAM covers the remote session, while the same engineer, with the same laptop and the same reprogramming capability, standing in front of the cabinet, is covered by nothing. |
| Revocation | Removing the right to use | NERC CIP-004-7 R5.1: unescorted physical access removed within 24 hours of a termination action, against 30 calendar days for named logical accounts under R5.3. And here, revoking means cutting power, with physical consequences. |
Read that table honestly and you will notice that you already know how to handle ten rows out of twelve, at least conceptually, so what is missing is not IAM doctrine but an enforcement point that acts in the physical world and a decision point that survives OT conditions.
Expanding IAM to the end of the power cord, not the stack
IAM spent fifteen years expanding its reach, from employees to customers, customers to partners, humans to workloads, workloads to autonomous agents, and at every step the same objection resurfaced, "that's not really identity", and at every step it was proven wrong.
The next frontier belongs to assets that have no IP address and never will. They form a large part of the production core of European critical infrastructure, they are subject to the same regulatory pressures as everything else, and they are currently managed with physical keyrings and paper logbooks.
The good news is that your mental model holds up, identity, authentication, policy, enforcement, proof, review, and you simply need to accept that the enforcement point is no longer a software component on a network path but a hardware device on an electrical circuit, and that decisions must be made locally, even when connectivity completely drops.
This reasoning gave birth to Trust-Buster, with a local policy engine that establishes the identity and legitimacy of an intervention from its physical and radio-frequency environment, actuators that enforce decisions on the equipment's power supply, and an audit-ready proof log, all of it in nominal operation whether connected or offline.
IAM at the end of the power cord, in short, is the same discipline you practice, with a circuit breaker at the end of the chain.
