How ADAS Is Reshaping Vehicle Safety Compliance

October 15, 2026
Authored by Burhan Barisik

Advanced driver assistance systems (ADAS) are becoming an important part of modern vehicle architecture. Functions such as advanced emergency braking, adaptive cruise control, lane-keeping assistance, driver monitoring and assisted lane changing are now available across a growing range of vehicle categories and market segments.

These technologies support drivers and contribute to safer mobility, but they also change how vehicle safety compliance must be demonstrated. An ADAS function may depend on sensors, software, electronic control units, braking, steering and human-machine interfaces (HMIs) operating together. Vehicle safety compliance is therefore expanding from the assessment of individual systems toward the evaluation of integrated vehicle functions.

In the European Union (EU), Regulation (EU) 2019/2144, commonly referred to as the General Safety Regulation, introduced a range of advanced safety technologies as standard vehicle equipment. Depending on the vehicle category and implementation date, these include intelligent speed assistance, driver drowsiness and attention warning, advanced driver distraction warning, reversing detection, event data recorders, emergency lane-keeping systems and advanced emergency braking capable of detecting vehicles and vulnerable road users.

Traditional vehicle safety regulations generally address defined systems or areas such as braking, steering, lighting, tires, occupant protection and crashworthiness. ADAS introduces additional complexity because one function may rely on several regulated vehicle systems simultaneously.

For example, an advanced emergency braking system may use cameras or radar to identify a potential collision, software to classify the object and calculate the risk, and the braking system to initiate an intervention. The safety of the function depends on the effective integration of sensing, data processing, vehicle control and driver communication. A compliant sensor or braking component does not, by itself, demonstrate that the complete ADAS function will perform safely in the vehicle.

Adding an ADAS function does not automatically mean that one separate regulation becomes applicable. Regulatory applicability depends on what the system does, how it influences vehicle control, the conditions under which it operates and the responsibility that remains with the driver.

A warning-only function may have a different regulatory impact from a function that applies the brakes or changes the vehicle’s lateral position. A system that continuously controls longitudinal and lateral motion may also be subject to different requirements from an emergency function that intervenes briefly in a critical situation. 

Commercial names such as “driving assistant,” “highway assistant” or “pilot” may describe different technical capabilities. Regulatory classification should therefore be based on a detailed technical description covering the intended use cases, activation conditions, operational boundaries, control capabilities, driver-monitoring strategy, override provisions, failure behavior and dependencies on other vehicle systems.

Regulatory requirements may also differ across target markets. While UNECE regulations provide an important framework for vehicle type approval in many countries, other markets may apply national safety standards, self-certification systems, or additional testing and reporting requirements. Manufacturers should therefore assess both the technical functionality of the ADAS feature and the regulatory framework of every market in which the vehicle or system is intended to be offered. 

Functions that automatically reduce speed or initiate emergency braking may interact with general braking requirements and dedicated advanced emergency braking regulations.

UN Regulation No. 152 addresses the approval of M1 and N1 vehicles with regard to advanced emergency braking systems. Its scope includes systems intended to avoid or mitigate rear-end collisions with passenger cars and impacts with pedestrians and bicycles. It also contains performance specifications, test procedures, conformity-of-production provisions and requirements concerning modifications to an approved vehicle type.

Lane-keeping, lane-centering and assisted lane-change functions may create regulatory considerations relating to steering control, operating boundaries, driver override and driver engagement.

UN Regulation No. 171 addresses driver control assistance systems (DCAS). UNECE defines DCAS as systems that assist the driver in controlling longitudinal and lateral vehicle motion on a sustained basis without taking over the entire driving task. The driver remains responsible for vehicle control and must continue monitoring the environment and system performance.

The development of UN Regulation No. 171 illustrates the expanding scope of ADAS regulation. The 02 series of amendments considered in 2026 expands the provisions relating to DCAS performance, driver engagement, operational monitoring and software management. This reflects the need to consider operational limits and driver interaction in addition to steering and braking performance.

An ADAS function may perform as designed while still creating a safety risk if the driver misunderstands its capabilities or operating limits. Human-machine interaction is therefore an important element of ADAS safety compliance.

Depending on the function, the vehicle may need to monitor driver availability, communicate system status, issue escalating warnings, allow driver override and explain when the system is unavailable. Information presented to the driver should also distinguish driver assistance from automated driving.

UN Regulation No. 171 requires warning strategies when insufficient driver engagement is detected. It also addresses communication of system limitations and the driver’s continuing responsibility, helping reduce the risk of overreliance on sustained assistance functions.

ADAS functions are increasingly software dependent. Their behavior may be affected by software versions, calibration data, cybersecurity controls and updates introduced after production.

UN Regulations Nos. 155 and 156 are not ADAS performance regulations. However, they support the continued integrity of software-dependent vehicle functions by addressing cybersecurity risks and controlled software updates. UN Regulation No. 156 establishes requirements relating to software updates and the software update management system.

Demonstrating ADAS performance requires evidence that the complete function performs as intended across defined operating conditions. Testing may need to consider variations in speed, loading, target position, road layout, environmental conditions and driver behavior.

Physical track and road testing remain important, but reproducing every combination of traffic, environmental and system conditions may not be practical. Modeling and simulation can support scenario exploration and performance assessment when models, inputs, assumptions and results are appropriately verified, validated and traceable. Rather than replacing physical tests, these methods can extend test coverage and provide evidence for conditions that are difficult or unsafe to reproduce.

Growing ADAS integration requires closer coordination between regulatory, engineering, safety, software and testing teams. Manufacturers should conduct function-based applicability assessments, define operational boundaries and driver responsibilities, coordinate braking, steering, HMI and software requirements, establish vehicle-level compliance evaluation strategies, and maintain hardware and software configuration traceability. 

Suppliers may need to provide performance evidence and supporting documentation, system limitations, installation conditions, calibration requirements, failure-mode information, software-version traceability, and change-impact assessments. Clear allocation of responsibilities is particularly important when a function depends on hardware or software supplied by multiple organizations.

Increasing ADAS integration does not simply add more safety features to vehicles. It changes how vehicle safety must be assessed, documented and demonstrated. Although each additional function does not necessarily introduce a separate regulation, it may expand the applicable requirements and create new interactions between sensing, braking, steering, driver monitoring, software management and cybersecurity.

Regulatory applicability should therefore be assessed when the function, sensor architecture, operating conditions and driver-interaction concept are defined. Early planning can help identify compliance gaps, establish suitable compliance evidence and reduce the risk of costly changes later in vehicle development.

UL Solutions can help automotive manufacturers and suppliers understand the regulatory requirements that may apply to ADAS-equipped vehicles, systems and components across target markets. Our global regulatory expertise can support function-based applicability assessments, regulatory change monitoring and compliance planning throughout product development. 

Through UL Solutions Global Compliance Management — Regulatory Intelligence (GCM-RI), manufacturers and suppliers can identify and compare regulatory requirements relevant to their automotive products, systems and target markets. GCM-RI also helps organizations monitor relevant regulatory developments, stay informed about new or changing requirements and assess their potential impact on products and market access strategies. 

Identifying applicable requirements and regulatory changes early can help organizations better coordinate compliance activities, technical documentation, product development and global market access activities.