---

Vector Informatik has expanded its CANoe Test Package EV with security tests for charging communication, reflecting a broader shift in EV validation towards cybersecurity as well as functional compliance. The update is aimed at helping carmakers, Tier 1s, and infrastructure developers identify weaknesses earlier in the development cycle.

For eeNews Europe readers, the move is relevant because charging communication is becoming a more complex part of EV system design, especially as Plug & Charge, ISO 15118 and encrypted communication become more widely deployed. It also points to a growing need for test tools that fit into automated development and validation workflows rather than stand-alone manual checks.

Security moves further into EV test workflows

Vector’s extension focuses on automated security validation for charging communication, an area that is becoming more critical as electric vehicles and charging stations exchange more data and rely on standardised communication stacks. In practice, this means developers need to check not only interoperability and protocol compliance, but also whether implementations can withstand malformed messages, protocol misuse or transport-layer issues.

The company says manual security testing can be slow, difficult to reproduce and poorly suited to CI/CD environments. That creates a challenge for teams trying to integrate cybersecurity checks into regular software and system validation. It can also add overhead when documenting results and maintaining custom test setups over time.

By adding dedicated security functions to the CANoe Test Package EV, Vector is positioning charging communication testing as part of a more continuous and structured development process, rather than a late-stage specialist task.

Coverage includes ISO 15118 and TLS testing

The CANoe Test Package EV – Security includes vehicle-to-grid communication fuzzing with system-under-test monitoring, along with TLS fuzzing, TLS protocol tests and interfaces for custom security tests. Supported standards include ISO 15118-2, ISO 15118-20, TLS 1.2 and TLS 1.3.

That combination potentially makes the package relevant for developers working on EVs, charging controllers and backend-linked charging functions, particularly where secure certificate-based communication is involved. Plug & Charge is one obvious area, since it depends on robust and trusted communication between vehicle and charger.

Vector says the package is designed for integration into existing development and integration workflows, with automated execution and systematic documentation intended to reduce manual effort. For engineering teams, the value may lie less in replacing specialist security analysis and more in making routine charging communication security tests easier to repeat and scale across development programmes.

---

---