AIS-156 Adds Cybersecurity Testing for Wireless BMS

India Adds Wireless BMS Cybersecurity Testing

India has introduced wireless BMS security testing requirements for battery management systems used in L-category electric vehicles, bringing cybersecurity assessment of wireless BMS interfaces into the AIS-156 framework. Amendment No. 5 to AIS-156-2020 adds Clause 6.12, specifically addressing BMS units equipped with Bluetooth Classic, Bluetooth Low Energy or other wireless interfaces. The requirements are intended to ensure that an unauthorized mobile application or device cannot connect to the BMS or execute safety-critical functions. The change expands the existing safety-focused BMS testing framework by directly addressing cybersecurity risks associated with wireless connectivity in electric vehicle battery systems.

New AIS-156 Clause Covers Wireless BMS Interfaces

AIS-156 already prescribed testing of BMS safety functions, but the latest amendment specifically introduces cybersecurity testing for wireless BMS interfaces. The new requirements assess whether unauthorized devices or applications can discover, connect to or command a BMS, including functions that could affect vehicle or battery safety. The testing therefore extends beyond conventional verification of BMS protection behavior and examines whether wireless communication channels can be misused. Bluetooth Classic, Bluetooth Low Energy and other wireless interfaces fall within the scope when they provide access to BMS functions or information.

BMS Data and Safety-Critical Commands Face Testing

The testing scope includes access to live BMS information such as voltage, current, temperature and state of charge. It also covers commands capable of affecting battery operation, including opening or closing contactors or relays, enabling or disabling charging and discharging, controlling cell balancing and resetting faults. These functions are significant because unauthorized access could potentially alter how the battery system operates or responds to protection conditions. The amendment consequently requires testing to determine whether an unauthorized wireless application or device can reach these functions through the BMS communication interface.

Configuration and Firmware Operations Are Included

The requirements also address attempts to modify BMS configuration parameters or protection thresholds through a wireless connection. Testing extends to firmware read, write or update operations, creating a broader assessment of what an unauthorized wireless connection could access within the battery management system. This approach means the security evaluation is not limited to observing normal BMS data or issuing operating commands. It also examines whether wireless access could expose configuration or software-management functions that influence the system's operating behavior, protection settings or firmware state.

Bluetooth BMS Vulnerabilities Prompted Government Action

The amendment follows cybersecurity concerns involving Bluetooth-enabled BMS units used in some e-rickshaws. In July, CERT-In said it had received reports of unauthorized 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 unauthorized users to connect, modify settings or cut battery discharge. The government subsequently acted against applications identified as capable of such misuse, while the Ministry of Heavy Industries issued an advisory on Bluetooth BMS vulnerabilities to SIAM, ACMA and vehicle testing agencies.

Testing Uses Smartphones and Bluetooth Analysis Tools

Under the amendment, the prescribed testing setup includes Android and iOS smartphones to replicate attempts by unauthorized third-party applications. Test agencies can also use Bluetooth protocol analyzers or sniffers, along with generic BLE GATT browsers or Bluetooth Classic terminal applications, to attempt device discovery, connection and command injection. The setup is designed to reproduce practical wireless access scenarios rather than relying solely on theoretical cybersecurity assessments. These tools allow testing agencies to examine how a BMS responds when an external device attempts to establish communication and send commands through its supported wireless interfaces.

Vehicle and Bench-Rig Testing Can Record BMS Responses

Testing can be conducted using a vehicle or a bench rig with the battery pack powered and, where applicable, under a simulated vehicle-running condition. Data loggers and CAN or UART analyzers can be used to record BMS responses during testing, including contactor states and fault flags. This arrangement allows the test agency to observe both the attempted wireless interaction and the resulting BMS behavior. Recording these responses is particularly relevant when testing commands associated with charging, discharging, contactor operation, fault handling or other functions that can affect battery system operation.

REESS Manufacturers Must Declare Wireless Interface Details

The amendment requires REESS manufacturers to declare information about the wireless interface used by the battery system. The declared details include the chipset, Bluetooth profiles, exposed services or characteristics, intended pairing method and all commands and functions accessible through the interface. This information gives testing agencies a defined view of the wireless architecture that needs to be evaluated. It also establishes a documented basis for checking whether the accessible services and functions can be discovered, connected to or controlled by unauthorized applications or devices during the prescribed cybersecurity assessment.

Default Configuration Must Be Tested First

An important requirement is that the battery system must first be tested in its default configuration as delivered to the customer. Manufacturers cannot provide security hardening specifically for the test before this initial assessment. This condition is intended to evaluate the security exposure of the system in the configuration that customers actually receive rather than measuring a specially prepared test configuration. The battery pack must also be conditioned to a state of charge between 40 and 60 percent unless otherwise specified. Together, these requirements establish controlled baseline conditions for the cybersecurity testing process.

Industry Impact & Outlook

The amendment increases the cybersecurity responsibilities associated with wireless BMS deployment in India's L-category electric vehicle market, particularly for manufacturers and suppliers using Bluetooth-connected battery systems. For the industry, the practical impact is a shift toward documenting wireless interfaces, testing unauthorized access paths and demonstrating that safety-critical BMS functions cannot be improperly controlled through wireless connections. The requirements are especially relevant to e-rickshaw applications following the reported misuse concerns, while testing agencies will need appropriate smartphones, Bluetooth analysis tools and vehicle or bench-rig setups. Future compliance activity is therefore likely to place greater emphasis on secure default configurations and controlled wireless access.

Frequently Asked Questions

What does the AIS-156 amendment require for wireless BMS security testing?
The AIS-156 amendment requires testing of wireless BMS interfaces to determine whether unauthorized devices can discover, connect to, or control safety-critical battery functions. It applies to BMS units using Bluetooth Classic, Bluetooth Low Energy or other wireless interfaces in covered L-category electric vehicles. Testing can examine access to live battery data, operating commands, configuration parameters, protection thresholds and firmware functions. The prescribed setup can include Android and iOS smartphones, Bluetooth analysis tools, vehicle or bench rigs, and data logging equipment to record BMS responses during attempted wireless access.