TL;DR: EV charging infrastructure needs availability, interoperability, and digital trust, with PKI and ISO 15118-2 certificates enabling authenticated Plug & Charge connections between vehicles and chargers, according to DigiCert. For identity teams, the lesson is that device trust and lifecycle control matter as much in physical infrastructure as they do in NHI programmes.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on DigiCert's blog post: EV charging depends on availability, interoperability, and digital trust, with PKI and ISO 15118-2 certificates used to authenticate vehicles and chargers automatically.
Why it matters: It matters because identity teams can treat EV charging as a real-world example of device trust, certificate lifecycle control, and federated interoperability across physical infrastructure.
Context
EV charging security is not only a transportation problem. It is a device identity problem, because the charger, vehicle, payment path, and software stack all need to trust one another before energy flows or a session completes. When that trust model is weak, interoperability becomes a usability issue and a security issue at the same time.
DigiCert frames the EV ecosystem around three dependencies: enough charging availability, standardised interoperability, and digital trust. For identity practitioners, the important shift is that certificates and roots of trust are not abstract backend controls here. They are the mechanism that lets unfamiliar devices and organisations safely transact across a shared infrastructure.
Key questions
Q: How should organisations govern device identity in shared charging infrastructure?
A: Treat every charger and vehicle certificate as part of a governed identity lifecycle. The key is to define who issues credentials, how trust is validated across partners, and how revocation works when equipment changes hands or reaches end of life. Shared infrastructure fails when identity ownership is assumed instead of documented and enforced.
Q: Why does interoperability create identity governance risk in EV ecosystems?
A: Because interoperability multiplies the number of organisations that must trust the same authentication model. If certificate formats, issuance practices, or trust anchors diverge, the result is fragmented control and inconsistent device assurance. Governance has to scale with the ecosystem, not with any one vendor or operator.
Q: What breaks when IoT certificates are not lifecycle-managed?
A: When IoT certificates are not lifecycle-managed, devices can keep trusted access long after business ownership, vendor relationships, or security intent has changed. That creates hidden trust debt, weak revocation posture, and a gap between technical validity and governance validity, which is where many device identity failures start.
Q: What is the difference between plug compatibility and trusted charging interoperability?
A: Plug compatibility is physical or electrical matching. Trusted charging interoperability adds identity proof, certificate validation, and mutual trust between organisations before a charging session is allowed to proceed. One solves connection mechanics, while the other solves whether the connection should be trusted at all.
Technical breakdown
How PKI establishes trusted charger-to-vehicle sessions
Public key infrastructure creates a verifiable trust relationship by using certificates, roots of trust, and certificate validation rather than shared passwords or static device allow-lists. In EV charging, that matters because the vehicle and charger need to authenticate each other automatically at connection time, before the charging session proceeds. ISO 15118-2 supports this model by defining how contract certificates are used to prove legitimacy. The security value is not only authentication, but also the ability to anchor trust in issuers, revoke credentials, and manage lifecycle changes across a distributed charging estate.
Practical implication: treat charger identity certificates as governed credentials with issuance, validation, revocation, and renewal processes.
Why interoperability depends on identity standardisation
Interoperability in EV charging is not just about plug shape or connector compatibility. It also depends on whether different automakers, charger operators, and payment systems can recognise and trust the same identity and certificate model. Without standardisation, drivers face extra app downloads, profile creation, payment setup, and inconsistent charging behaviour. That creates friction for users and fragmentation for security teams. A common trust framework reduces the number of bespoke trust relationships each participant must maintain, which is critical when infrastructure scales across brands, geographies, and operating models.
Practical implication: align charger and vehicle identity requirements to shared standards rather than building one-off trust exceptions.
Why a root of trust matters for Plug & Charge operations
A root of trust is the anchor that makes downstream certificates meaningful. In Plug & Charge scenarios, the root validates the trust chain that allows an EV and charging infrastructure to complete a secure, automatic session without manual login. If the root is weak, isolated, or inconsistently governed, the rest of the certificate hierarchy inherits that fragility. This is why unaffiliated root models matter in multi-party ecosystems: they reduce dependence on a single vendor’s trust boundary and help separate testing, issuance, and deployment across participants.
Practical implication: map every production charging trust chain back to the issuing root and verify who governs it.
Breaches seen in the wild
- GitHub code signing certificate theft 2022: A machine account's compromised token cloned GitHub's Desktop and Atom repos, exposing encrypted signing certificates later revoked.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 150+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
EV charging is becoming a device identity problem before it is a user convenience problem. The article shows that charging only scales when chargers, vehicles, and payment systems can trust each other across organisational boundaries. That shifts the control question from physical access alone to certificate governance, device authentication, and lifecycle management. For practitioners, the lesson is to model EV charging as a federated identity ecosystem, not a standalone IoT deployment.
PKI is the practical trust layer, but its value depends on governance discipline. Certificates only work when issuance, validation, revocation, and renewal are consistently managed across manufacturers and operators. Without that discipline, a secure-looking connection can still conceal stale trust, fragmented trust anchors, or unverifiable device provenance. The implication is that identity governance for connected infrastructure must extend to machines and charging endpoints, not stop at human users.
Interoperability changes the attack surface by expanding the number of parties that must share trust. As more automakers and charging networks converge on common standards, the number of cross-organisation trust relationships grows. That does not weaken security by itself, but it makes certificate lifecycle control and root governance more consequential. Practitioners should expect standards-based scale to increase the operational burden of identity assurance, not reduce it.
Federated device trust is now a market pattern, not an edge case. EV charging shows how physical infrastructure increasingly relies on identity mechanics normally associated with NHI and workload trust. The same governance logic applies wherever autonomous devices transact with shared services: establish verifiable identity, constrain trust boundaries, and manage credentials across their full lifecycle. The practitioner takeaway is that device trust models are becoming core identity architecture, not a niche integration concern.
What this signals
Device trust is moving into the same governance class as workforce and workload identity. EV charging shows that identity teams will increasingly be asked to govern certificates, issuer boundaries, and revocation logic for infrastructure that looks operational but behaves like a trust network. The programme implication is that machine identity controls must extend into physical environments where authentication happens between organisations, not just inside them.
Certificate lifecycle discipline is the real control plane for Plug & Charge ecosystems. Once connected infrastructure depends on automatic authentication, the quality of the trust model depends on who can issue, revoke, and replace credentials without breaking service. Identity programmes that already manage NHI and workload credentials have a useful template here: inventory the trust chain, define ownership, and make revocation observable.
For practitioners
- Map charging assets to a trust inventory Document every charger, vehicle interface, issuer, and certificate chain involved in the charging flow so you can see where trust is anchored and where it is delegated.
- Govern certificate lifecycle end to end Define issuance, renewal, revocation, and retirement processes for charger and vehicle certificates, including who can approve exceptions and what triggers recovery.
- Standardise trust boundaries across partners Require common identity and certificate expectations for automakers, charger operators, and platform providers so interoperability does not rely on ad hoc trust exceptions.
- Test failure modes in the root of trust Validate how the environment behaves when a root is replaced, a certificate is revoked, or a trust chain cannot be verified, because these are operational rather than theoretical failures.
Key takeaways
- EV charging trust depends on more than connectors and app workflows. It depends on certificate-based device identity that can be issued, validated, and revoked across multiple organisations.
- The practical risk is not abstract. As interoperability expands, the number of parties that must share trust increases, which makes lifecycle governance and root-of-trust control more important.
- Identity teams should treat connected charging infrastructure as a federated trust environment and apply the same rigor they use for machine identities and other non-human credentials.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5 and CSA Cloud Controls Matrix set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-04 — Insecure Authentication | Mutual certificate trust for chargers and vehicles is an authentication problem for non-human devices. |
| NHI-07 — Long-Lived Secrets | EV charging certificates and trust roots require lifecycle control to prevent stale credentials from persisting. | |
| Recommendation — Apply NHI-04 by enforcing certificate-backed authentication for chargers, vehicles, and issuer flows. Reduce long-lived trust by tightening certificate expiry, renewal, and revocation governance. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Certificate issuance, renewal, and revocation are central to this device trust model. |
| Recommendation — Use IA-5 to govern certificate lifecycle handling for charging infrastructure and partner trust. | ||
| MITRE ATT&CK | TA0006 — Credential Access | The article centers on protecting credentials and trust material used by connected devices. |
| Recommendation — Map exposed charging credentials to TA0006 and watch for unauthorized certificate or key use. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | The charging ecosystem depends on identity governance across multiple cloud-connected participants. |
| Recommendation — Apply IAM governance to federated charger and vehicle trust relationships. | ||
Key terms
- Public Key Infrastructure: Public Key Infrastructure is the trust system that issues, manages, and revokes digital certificates used to prove identity. In practice it binds keys to entities and policies, making authentication, encryption, and non-repudiation possible across users, devices, and services.
- Root Of Trust: A root of trust is the authoritative starting point that other identities and certificates rely on for validation. In distributed ecosystems, it determines which parties can establish trust, which can be revoked, and how consistent authentication remains across vendors and environments.
- Plug & Charge: Plug & Charge is an EV charging model where authentication and session setup happen automatically when a vehicle connects to a charger. It depends on standards-based identity and certificate validation, which means convenience only remains safe when the underlying trust chain is managed well.
- Device Identity: Device identity is the cryptographic proof that a specific machine is the thing being accessed, independent of its IP address or current network. In fleet governance, it allows policy, audit, and revocation to follow the device across locations and transports.
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on June 24, 2026.
Updated on October 8, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org