If you buy networked chargers in 2027, ask for OCPP 2.0.1, and ask your software provider how it secures the link between each charger and its servers. Three things changed this autumn. From 28 September, California requires OCPP 2.0.1 certification on newly installed DC fast chargers built with public or ratepayer money. The Open Charge Alliance opened testing for OCPP 2.1 on 12 October. And two US government security advisories this year described charging back ends that let an attacker pose as a charger.

Here is what each change means for condo boards, property managers, small network owners and installers, and the five questions to put to any provider.

OCPP in one paragraph

OCPP (Open Charge Point Protocol) is the language a charger uses to talk to the software that runs it: start and stop, prices, status, faults, firmware. Because it is an open standard, an OCPP charger from one maker can work with software from another company, and you can change software later without replacing the charger.

Why the OCPP version matters for funding

OCPP 1.6 dates from 2015 and OCPP 2.0.1 from 2020; 2.0.1 builds security and ISO 15118, the standard behind Plug & Charge, into the protocol. We compare the two versions in detail in OCPP 1.6 vs 2.0.1: the differences that matter.

A 1.6 charger does not stop working when a newer version appears. But funding rules are moving to 2.0.1:

  • Federal. Public chargers built with federal highway funds such as NEVI must conform to OCPP 2.0.1 (23 CFR 680.108).
  • New York. In the utilities’ Make-Ready program, Level 2 chargers committed on or after 1 June 2025 had to use OCPP 2.0.1 or later hardware. The program stopped taking new applications in April 2026.
  • California. See below.

What California’s rule actually says

The California Energy Commission’s summary page says that publicly funded DC fast chargers installed on or after 28 September 2026 “must report using the OCPP 2.0.1 protocol.” The standards exclude single-family homes and buildings with fewer than four units.

Under the regulation (Title 20, §3125), the OCPP 2.0.1 duties apply to networked chargers installed on or after 28 September 2026 that were built with public or ratepayer money. AC Level 2 chargers, fleet chargers and private residential chargers are exempt. In practice this means publicly or ratepayer-funded DC fast chargers. They need OCPP 2.0.1 certification for “Core and Advanced Security”, and so does their network provider’s software. In the OCA’s certification documents, Advanced Security means support for TLS with client authentication: the charger proves its identity with a certificate, not just a password.

Level 2 sites funded by a CEC grant are different. A CEC advisory notice from 9 June 2026 says upcoming CEC-funded projects will require OCPP 2.0.1 (or later) certification for most networked charger models, while certification of the network software will no longer be required in grant agreements unless stated. So in California, the version on the charger matters even when you are not building fast chargers. This is not legal advice; read the notice and the regulation for your own project.

OCPP 2.1: testing is open, certification has no date

The OCA released OCPP 2.1 in January 2025. It adds bidirectional charging (V2X), deeper control of distributed energy resources and support for ISO 15118-20. The OCA says application logic built for 2.0.1 “will continue to work in OCPP 2.1”, while 1.6 “is not compatible with OCPP 2.1.”

On 12 October 2026 the OCA made OCPP 2.1 testing available in its test tool, so makers can now test ISO 15118-20 support, bidirectional power transfer and improved smart charging. The announcement gives no start date for 2.1 certification, and the OCA’s certification page lists certificates for 1.6 and 2.0.1 only.

What it means for you: 2.0.1 is the version to buy for now, and a charger that runs 2.0.1 is the shorter step to 2.1. Kinethra supports OCPP 1.6 and 2.0.1, and Connect Business works with OCPP 1.6 and 2.0.1 chargers from any manufacturer. OCPP 2.1 support at Kinethra is in development.

Why security is now a buyer’s question

On 1 October 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) published an advisory on a charging-software back end. Its most serious finding, rated 9.4 out of 10: OCPP “WebSocket endpoints lack proper authentication mechanisms, enabling attackers to impersonate charging stations,” where an attacker who knew a charger’s ID could pose as that charger. CISA also listed no limit on login attempts, one session ID usable from several places, and charger identifiers visible on public maps. CISA said it had no reports of public exploitation. The vendor said it supports OCPP 1.6 Security Profile 2 (a password sent over TLS encryption) and encourages operators to enable it.

In February, CISA had described the same four types of weakness at another provider.

We name no one here; the advisories are public. The point is that a condo board rarely asks how its chargers log in, and the answer decides who can control them.

The OCA’s guidance is also moving. Its Security Operations Guide, version 2 (22 September 2026) splits requirements between software providers and charge point operators, adds a section on defense in depth, and adds a policy on post-quantum cryptography. For 1.6 chargers, the OCA’s security whitepaper covers secure firmware updates and security event logging.

5 security questions for your software provider

  1. Which OCPP security profile does each of my chargers use today? Ask for it per charger. In the OCA’s definitions, Profile 1 is a password without encryption, Profile 2 is a password over TLS, Profile 3 is a certificate over TLS. If any charger logs in without TLS encryption, ask for a plan and a date to move it.
  2. Does every charger have its own password or certificate, and how is it changed? A charger ID used as the only credential is the weakness CISA described; a shared or default password is a close cousin.
  3. What stops someone posing as one of my chargers? Ask about limits on login attempts, alerts on duplicate sessions, and who sees those alerts.
  4. How are firmware updates checked and logged? Ask whether updates are signed, who can start them, and whether security events are recorded.
  5. What OCA certification do you hold, for which version and profiles? Ask for the certificate and check it on the OCA website. If you will run publicly or ratepayer-funded DC fast chargers in California, ask whether the software holds OCPP 2.0.1 Core and Advanced Security certification and whether the provider is a CEC-enrolled charging network provider.

Ask any provider these five questions. Every charger on Kinethra has its own unique OCPP authentication key, and chargers talk to the platform over a secure WebSocket channel (WSS). The app, admin and API use TLS/HTTPS. We answer security questions on request.

What to do now

  • Buying chargers in 2027: ask for OCPP 2.0.1 on the exact model, and whether the maker plans 2.1.
  • Applying for funding: read the program’s OCPP and certification lines before you choose hardware and software.
  • Running 1.6 chargers: keep them, but ask your provider which security profile they use and whether firmware supports a stronger one.
  • Any network: put the five questions above in writing, and keep the answers with your contract.

Choosing chargers or software for 2027?

The OCPP version and the security setup are decided at purchase, and they are hard to change after installation. If you are planning chargers for a building or a network, book a business demo and we will go through your chargers, your funding rules and these questions with you.

Sources

  1. California Energy Commission, EV charger standards (opens in a new tab) ()
  2. California Energy Commission, Title 20 regulatory text (opens in a new tab) ()
  3. California Energy Commission, 9 Jun 2026 (opens in a new tab) ()
  4. eCFR, 23 CFR 680.108 (opens in a new tab) ()
  5. Joint Utilities of New York, Make-Ready overview (opens in a new tab) ()
  6. Open Charge Alliance, OCPP overview (opens in a new tab) ()
  7. Open Charge Alliance, 23 Jan 2025 (opens in a new tab) ()
  8. Open Charge Alliance, 2.1 testing, 12 Oct 2026 (opens in a new tab) ()
  9. Open Charge Alliance, OCPP certification program (opens in a new tab) ()
  10. Open Charge Alliance, 2.0.1 CSMS certificate, 19 Nov 2025 (opens in a new tab) ()
  11. Open Charge Alliance, Security Operations Guide v2, 22 Sep 2026 (opens in a new tab) ()
  12. Open Charge Alliance, 1.6 Security Whitepaper, 5 Feb 2026 (opens in a new tab) ()
  13. CISA, ICSA-26-274-02, 1 Oct 2026 (opens in a new tab) ()
  14. CISA, ICSA-26-057-07, 26 Feb 2026 (opens in a new tab) ()

About the author