Основы Product Security для автомобилей и зарядных станций: термины, архитектура, фреймворки

Product Security for automotive and EV charging infrastructure encompasses several key concepts, including terminology, architecture, frameworks, and typical risks. Modern automobiles and charging stations are no longer just simple machines but complex software-hardware products, with embedded systems, cloud services, mobile applications, and telecommunication playing crucial roles.

The security model differs from traditional web applications, with potential consequences ranging from system failures to compromise of OTA updates, remote command abuse, and loss of availability for charging infrastructure.

Product Security (ProdSec) in this context goes beyond simply finding bugs. It involves managing trust, architecture, software lifecycle, cloud and embedded components, and operational security. The growing interconnectedness of electronic components, cloud and embedded components, telecommunication, mobile applications, cloud backends, OTA updates, analytics, monitoring, vendors, and field operations emphasizes the need for a separate discussion on ProdSec in automobiles and EV charging infrastructure.

Automobiles today are not just single components but an entire ecosystem. They include in-car software and Electronic Control Units (ECUs), internal buses and networks, telematics and remote communication, mobile applications and web portals, cloud backends, OTA updates, analytics and monitoring, suppliers, and field operations.

This interconnectedness makes the question of vulnerability more nuanced. Instead of asking "is there a vulnerability?", a more productive question is "can this weakness impact the trust architecture, product lifecycle, or operational security?"

An EV Charging Equipment (EVSE) is not merely a charging station. It involves a connected infrastructure, including chargers, device settings, communication protocols with the backend, operator portal, mobile app, billing and tariffs, session management, OTA updates, and monitoring. From a ProdSec perspective, security is required not only for web parts or APIs but for the entire operational framework, including devices, station identities, remote commands, updates, and recovery processes.

The architecture of modern automobiles and EV ecosystems can be divided into four major layers: the user layer (driver, passengers, mobile app); the vehicle layer (ECUs, infotainment, telematics, ADAS, battery, and internal functions); networking and connections (CAN/LIN/FlexRay, Automotive Ethernet, 4G/5G, Wi-Fi/Bluetooth, GNSS); and the cloud and services (OTA, analytics, remote commands, APIs, data storage).

This model helps illustrate that risks and control measures are distributed across multiple levels, not just hardware or backend.

Key terms in ProdSec for automobiles and EVSE include Electronic Control Unit (ECU), Telematics Control Unit (TCU), Advanced Driver Assistance Systems (ADAS), Over-the-Air (OTA), Infotainment, OCPP (a key protocol for charging station-backend interaction), Firmware, CAN/LIN/FlexRay/Automotive Ethernet, Software Bill of Materials (SBOM), Threat Analysis and Risk Assessment (TARA).

In ProdSec, the focus is on securing the product as a system. Typically, attention is concentrated on specific themes, including: boundaries of trust (trust boundaries) - where the system accepts external data and where the trusted zone ends; identity and authentication - how devices prove their identity and how EV charging stations authenticate.