A Chat About CyberSecurity with Dr. Steven A Wright

The Dodge Charger is a performance-focused sedan (and in some years, a muscle-car style vehicle) known for strong acceleration and a sporty driving feel. In an EV-focused podcast context, it’s being mentioned because vehicle connectivity and software can create cybersecurity concerns—like the idea that someone could hack a “charger” (or a connected vehicle system) and exploit vulnerabilities. That makes it relevant to discussions about protecting modern cars from unauthorized access.

A public charging network is a service that provides EV charging access at locations like parking lots and streets. It’s run by a charging operator that manages authentication and billing for drivers using the chargers.

A charging system operator is the organization that runs a charging network and administers access to chargers. They typically control user authentication, authorization, and billing workflows across chargers and apps.

Personally identifiable information (PII) is data that can identify a specific person, such as account details tied to EV charging. EV charging systems may collect it for identifying users, tracking charging activity, and processing payments.

EV chargers are the hardware units that deliver electricity to an EV and communicate with the network for authorization and payment. Because they include both power electronics and networked software, they can be vulnerable to attacks.

A private EV charger is a charging unit intended for a specific location or owner (for example, at home or a private facility). The transcript notes that physical security is often stronger for private chargers, which can affect the threat model.

Standardized protocols are agreed-upon communication rules that charging equipment and software use to talk to each other. Standardization can improve interoperability, but it also means security issues in widely used protocols can affect many networks.

Tesla is an electric-vehicle brand known for tightly integrating software with the car. In cybersecurity discussions, that “software-first” design can matter because attackers may target connected systems and update pathways rather than only physical components.

Malware is malicious software designed to harm, spy on, or take control of a device. In a connected vehicle context, malware can be used to disrupt systems or attempt to gain access through entry points like updates, connectivity, or compromised subsystems.

Over-the-air (OTA) software updates are remote updates sent to a vehicle over a wireless connection. Because they change code inside the car, they can become an attack surface if an attacker can interfere with the update process or trick the vehicle into installing malicious software.

Infotainment systems are the car’s in-cabin entertainment and information tech, typically including the touchscreen, media playback, navigation, and connectivity features. If an infotainment system is compromised, it can sometimes be used as a stepping stone to reach other vehicle computers over internal networks.

Near-field communications (NFC) are short-range wireless links used for things like tapping a card or phone to a reader. In vehicles, NFC can be a contactless entry point, and if its security is weak, it may be exploited to gain unauthorized access.

RFID (radio-frequency identification) interfaces use radio signals to identify objects or credentials, often at close range. In vehicles, RFID can be part of keyless entry or other access systems, and weak RFID security can enable unauthorized identification or access attempts.

A charging station is the EV charging hardware (often a wallbox or public charger) that provides electrical power to the vehicle. In cybersecurity discussions, it’s a key “device” because it can communicate with back-end services and may have its own software and network connections.

“Back end systems with the payments” refers to the remote servers and software that manage charging sessions, authentication, billing, and payment processing for EV charging. These systems are part of the overall EV charging ecosystem, so attacks can target accounts, authorization flows, or payment-related services.

“Destabilize the grid” means disrupting the electrical power network so voltage, frequency, or power flow becomes unstable. EV charging can interact with the grid through power electronics and control systems, so an attack could theoretically cause harmful power behavior.

“Unsafe power delivery” refers to providing electrical power to an EV in a way that’s outside safe operating limits (for example, incorrect voltage/current or improper control timing). In cybersecurity terms, attackers might try to manipulate charging control so the vehicle receives harmful power.

“Degrade the batteries” means reducing battery health over time, typically by stressing the cells beyond what they’re designed to handle. In EV cybersecurity discussions, the idea is that malicious charging behavior could accelerate wear or damage battery components.

A “vulnerability” is a weakness in software or systems that can be exploited to cause harm—such as unauthorized access, incorrect behavior, or denial of service. The speaker frames it as something discovered in a lab and then evaluated for severity and whether systems have been patched.

A “supply chain of software” is the chain of dependencies used to build EV-related systems—like libraries and components written by other developers. If upstream software has security issues, those weaknesses can flow into the final product unless updates and checks are done.

“Open source software” is code whose source is publicly available and can be used or modified by others. In EV cybersecurity, open-source dependencies are common, so teams must monitor them for newly reported vulnerabilities and apply updates.

“Upstream software” means the earlier, third-party components and libraries that your system depends on. If vulnerabilities are found upstream, they can affect downstream EV systems unless patches and dependency updates are applied.

The Linux kernel is the core software that manages hardware resources like CPU, memory, and device drivers. In EV and vehicle cybersecurity, vulnerabilities in widely used components like the Linux kernel can affect many devices that run Linux-based systems.

Drones are unmanned aerial vehicles controlled via onboard software and often via wireless links. In a cybersecurity context, drone systems have different threat models than cars because failures can have immediate physical consequences in the air.

E-bikes are bicycles with electric motors, typically controlled by an onboard electronic system. Cybersecurity can apply to their motor controllers, connectivity features, and any companion apps that manage settings or firmware.

E-trikes are electric three-wheeled vehicles (tricycles) with motorized assistance or full electric drive. Like e-bikes, their electronic control systems can be part of the cybersecurity surface area.

Robotaxis are autonomous ride-hailing vehicles that operate with self-driving software rather than a human driver. Cybersecurity matters because attacks could affect vehicle control, passenger safety, or the service’s ability to operate safely.

Jetson-1 appears to refer to NVIDIA’s Jetson platform line, which provides embedded computing for robotics and autonomous systems. These devices often run Linux-based software stacks, making them relevant to the cybersecurity “upstream fix” discussion.

In this context, airborne refers to electric vehicles operating in the air (like drones or personal flyers). The key point is that safety and consequences differ from ground vehicles, affecting how cybersecurity risk is evaluated.

The Tesla Model Y is an all-electric compact SUV built by Tesla, widely discussed for its software-driven features and app-based controls. It comes up in the podcast around accessories and apps—specifically how owners use connected services and whether there are security or access concerns tied to those apps. That makes it a relevant example for how EVs rely on software and connectivity in day-to-day use.