
Ten security questions for your charging back-end supplier
What to ask before you sign or renew, why each question matters, and what a good answer sounds like.
NIS2 lists operators of recharging points, subject to size rules. You’re expected to know your chargers, act without stopping sessions, and show what happened.

NIS2 duties stay with the operator in scope. The Open Charge Alliance’s guide also says the charge point operator shall set up security monitoring.
The clock runs from when you become aware of a significant incident. Someone has to decide, and record why.
CISA issued at least 15 advisories on charging back-ends in 2026. The six from 26 February all list missing authentication on charger connections.
Each item carries its status today. The first GridSEAL release is targeted for about Q2 2027.
What’s connected, on which OCPP version and security profile, with a source beside each field.
Roadmap, first releaseDetections on back-end events, such as an unsigned firmware job. Each alert names the rule that fired.
Research pilot, rules engine laterA check for active sessions comes first, and a named person approves. Actions go through your own back-end.
Isolation lab-tested, approval laterA sealed record with a signature, which your auditor can verify without an account on our system.
Roadmap, first releaseIn a study of 325 DC chargers, 12% supported TLS on this link.
ISO 15118-20 applies to new or renovated points from 1 January 2027.
It’s a networked computer on a public site, and its firmware is an update path.
The Cyber Resilience Act binds charger makers.
CISA issued at least 15 advisories on these platforms from January to October 2026.
NIS2 binds operators, including their supplier risk.
Vehicle-to-grid adds commands that move real power, so each one needs limits.
GridSEAL Grid is on our roadmap.

What to ask before you sign or renew, why each question matters, and what a good answer sounds like.

What counts as significant, what’s due and when, and what a charge point operator should set up before an incident.

How a charger proves who it is to your back-end, what each profile protects, and what no profile covers.
One to two weeks: an outside-in scan plus one read-only export. You get a written report, and nothing is installed.