India has introduced cybersecurity testing requirements for battery management systems (BMS) used in L-category electric vehicles, bringing wireless BMS security within the testing framework prescribed under AIS-156.
Amendment No. 5 to AIS-156-2020 adds a new Clause 6.12 covering security testing of BMS units fitted with Bluetooth Classic, Bluetooth Low Energy or other wireless interfaces. The requirements are aimed at ensuring that an unauthorised mobile application or device cannot connect to the BMS or execute safety-critical functions.
While AIS-156 already prescribed testing of BMS safety functions, the latest amendment specifically brings cybersecurity testing of wireless BMS interfaces into the framework. The new requirements test whether unauthorised devices or applications can discover, connect to or command the BMS, including safety-critical functions.
The scope covers access to live BMS data such as voltage, current, temperature and state of charge, as well as commands including opening or closing contactors or relays, enabling or disabling charging and discharging, controlling cell balancing and resetting faults.
It also covers attempts to modify configuration parameters or protection thresholds and perform firmware read, write or update operations through a wireless connection.
The amendment comes after cybersecurity concerns emerged around Bluetooth-enabled BMS units used in some e-rickshaws. In July, CERT-In said it had received reports of unauthorised individuals using publicly available BMS mobile applications to abruptly power off moving e-rickshaws. According to the government, some BMS units used in low-cost e-rickshaws had default or no credentials, allowing unauthorised users to connect, modify settings or cut battery discharge.
The government subsequently acted against applications identified as being capable of such misuse. The Ministry of Heavy Industries also issued an advisory on Bluetooth BMS vulnerabilities to SIAM, ACMA and vehicle testing agencies.
Under the AIS-156 amendment, the prescribed testing setup includes Android and iOS smartphones to replicate attempts by unauthorised third-party applications. Test agencies can also use Bluetooth protocol analysers or sniffers and generic BLE GATT browsers or Bluetooth Classic terminal applications to attempt discovery, connection and command injection.
Testing can be carried out using a vehicle or bench rig with the battery pack powered and, where applicable, under a simulated vehicle-running condition. Data loggers and CAN or UART analysers can be used to record BMS responses, including contactor states and fault flags.
The amendment also requires REESS manufacturers to declare details of the wireless interface, including the chipset, Bluetooth profiles, services or characteristics exposed, intended pairing method and all commands and functions accessible through the interface.
Importantly, the battery system must first be tested in its default configuration as delivered to the customer, without manufacturer-assisted security hardening specifically for the test. The battery pack is also required to be conditioned to a state of charge between 40 and 60 percent unless otherwise specified.
ALSO WATCH: Cybersecurity Dialogue Ep1: Can Your Car be Hacked?
Cybersecurity Dialogues Ep 2: Is an SDV Complete Without Chip-Level Cybersecurity?