| Draft Report of the 57th Session of the IWG on DETA |
| Reference Number: WP.29-200-24 |
|
Report of the 57th session of the IWG on Data Exchange for Transport Authorities held on 13 November 2026. The session recorded more than 153,000 approvals uploaded by 23 approval authorities, an increase of 20,000 since the previous session. The IWG discussed the new DETA software version introducing two-factor authentication, internal mail functionality, and enhanced administrator configuration options, with migration expected in Q1 2027. Germany is considering using DETA for a scenario database for automated driving. The IWG reviewed potential use of DETA for sharing technical information regarding proposed GRPE UN Regulation on brake emission of non-original parts. Draft amendments to guidelines for UNR155 were approved, with similar updates planned for UNR171 and UNR157. The next session is scheduled for 26 February 2027 in Brussels. |
| Submitted by: DETA |
| Meeting Sessions: 200th WP.29 session (16-20 Nov) |
| Document date: 17 Nov 26 |
| Relevant to: WP.29 Discussion Topic | Database for the Exchange of Type Approval Documentation, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), and UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS) |
| Click here to view the full document file |
| Report to 200th WP.29 session from the 57th IWG on DETA meeting (Data Exchange for Transport Authorities) |
| Reference Number: WP.29-200-23 |
|
Report on the secure internet database DETA for exchanging approval documentation between Contracting Parties of the 1958 Agreement. 41 Contracting Parties have notified DETA Focal Points; approximately 153,300 approvals and 8,700 manufacturers are uploaded. 20 manufacturers and 4 Technical Services have access to DETA. Migration to new software version with features including two factor authentication, mailing functions, adaptation of guidelines for UN R155/171/157, and additional languages is expected in Q1/27. DETA serves as an open, neutral, trustworthy platform for authorities to exchange compliance documents beyond the 1958 Agreement. |
| Submitted by: DETA |
| Meeting Sessions: 200th WP.29 session (16-20 Nov) |
| Document date: 17 Nov 26 |
| Relevant to: WP.29 Discussion Topic | Database for the Exchange of Type Approval Documentation, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), and UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS) |
| Click here to view the full document file |
| Data Exchange for Type Approvals: Agenda for the 58th (February 2027) session |
| Reference Number: DETA-58-02 |
|
Report of the 57th session of the IWG on DETA held on 13 November 2026. The session covered the state of play with 153,000 approvals uploaded by 23 approval authorities, a new DETA software version introducing two-factor authentication and internal mail functionality with migration expected Q1/2027, widening the scope to include a scenario database for automated driving and potential use for sharing technical information on brake emission of non-original parts, amendments to guidelines for UNR155 reflecting changes to the new software version, and plans for a joint IWVTA/DETA workshop on 24 June 2027. |
| Meeting Sessions: 58th DETA session (26 Feb 2027) |
| Document date: 14 Nov 26 |
| Relevant to: WP.29 Discussion Topic | Database for the Exchange of Type Approval Documentation, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), and UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS) |
| Click here to view the full document file |
| Guidelines for the use of DETA with regard to the exchange of information on Cyber Security |
| Reference Number: DETA-57-03-Rev.1 |
|
Guidance document for approval authorities on using DETA to implement UN Regulation No. 155. Notifying authorities shall upload cyber security information as PDF files no later than 14 days before granting a first-time approval, complete mandatory fields including approval number and date, and send a notification message to other authorities via DETA. Other approval authorities may submit comments within 14 days of notification by email and DETA message. Notifying authorities shall upload received comments to DETA without undue delay. These procedures apply before first-time approvals and each time assessment methods or criteria are updated. |
| Submitted by: DETA |
| Meeting Sessions: 57th DETA session (13 Nov) |
| Document date: 13 Nov 26 |
| Relevant to: WP.29 Discussion Topic | Database for the Exchange of Type Approval Documentation and UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Automated/Connected Vehicles: Report of the 26th (September 2026) session |
| Reference Number: GRVA/26 |
|
GRVA’s twenty-sixth session reviewed the Informal Working Group on Automated Driving Systems’ progress and adopted revised Terms of Reference for Phase II, establishing the Workshops on ADS implementation with Terms of Reference and Rules of Procedure. GRVA adopted amendments to UN R157 addressing Safety Management System provisions and clarifying requirements for ALKS activation across multiple territories, with supplements to the original version and 01 series of amendments. GRVA adopted amendments to UN R155 and UN R156 concerning software identification and software updates provisions, approved Supplement 4 to UN R155 clarifying its scope, and adopted amendments addressing Approval Authority arrangements for Certificates of Conformity. GRVA adopted amendments to UN R171 aligning continued compliance provisions with UN R157, adopted amendments to UN R79 regarding steering equipment and remote-control parking, adopted amendments to UN R13 and UN R13-H concerning trailer braking systems, and adopted amendments to UN R90 addressing replacement braking parts. GRVA established the Task Force on Exchange of Scenario-Relevant Information with Terms of Reference and Rules of Procedure, discussed automated vehicle categorization and automated parking systems, and reviewed ongoing work on Artificial Intelligence in vehicles, cyber security, data protection, advanced driver assistance systems, and motorcycle braking. |
| Submitted by: GRVA |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 04 Nov 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 90 | Replacement Brake Linings, Discs, and Drums, UN Regulation No. 140 | Electronic Stability Control Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), GTR No. 26 | Automated Driving Systems, and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| AI Management System: Bridging the Gap Between AI and Current Open Norms |
| Reference Number: AI-12-23 |
|
Presentation proposing an AI Management System (AIMS) as a complementary organizational layer to existing safety, cybersecurity, and software update management systems. AIMS would regulate AI through organizational processes rather than technical requirements, covering data lifecycle, model development, verification and validation, change control, and operational monitoring. The system is technology-neutral, lifecycle-based, and aligned with industry standards including ISO 26262, ISO 21448, and ISO/IEC 42001, avoiding the need for product-specific AI test procedures and re-approval of model updates. |
| Submitted by: Netherlands |
| Meeting Sessions: 12th AI session (26-27 Oct) |
| Document date: 22 Oct 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, WP.29 Discussion Topic | Artificial Intelligence, and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| IWG EV/HFCV Retrofit Systems : Status Report |
| Reference Number: GRPE-95-57 |
|
Status report on the EV/HFCV Retrofit Systems IWG activities. The group held six meetings since the last GRPE session and is currently focused on the EV part, with HFCV-specific issues deferred to a future series of amendments. Key discussion items include scope definition with agreement to exclude vehicles holding approvals according to UN R155 and UN R156, definition of Electric Powertrain Retrofit System, vehicle family notion, and type of EPRS. Experts from different GRs participate in discussions on electrical safety, EMC, braking, cybersecurity, and power determination. Benchmarking of existing national requirements for EV retrofit activities is ongoing. Regulation drafting continues on scope and type definition, with demonstrations of retrofitted vehicles expected at the 200th WP.29 session in November 2026. |
| Submitted by: EV/HFCV |
| Meeting Sessions: 95th GRPE session (14-16 Oct) |
| Document date: 14 Oct 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| Outline of 1st DETA/IWVTA Workshop in 2026 |
| Reference Number: IWVTA-52-06 |
|
Document outlining the 1st DETA/IWVTA Workshop held on 17 June 2026 in Flensburg, Germany. The workshop covered presentations on what DETA and IWVTA are, industry and government expectations, and issuance and acceptance of IWVTA certificates in the EU. Survey responses from 15 participants, including from Southeast Asian countries, indicated needs for more explanation on DETA access rights, onboarding processes for new Contracting Parties, and clearer guidance on how IWVTA can be modified to suit individual markets. Suggestions included developing supporting materials and guidelines on IWVTA application procedures and organizing a second workshop in Japan or Asia. |
| Meeting Sessions: 52nd IWVTA session (12 Nov) |
| Document date: 13 Oct 26 |
| Relevant to: UN Regulation No. 90 | Replacement Brake Linings, Discs, and Drums, UN Regulation No. 0 | International Whole Vehicle Type Approval System (IWVTA), WP.29 Discussion Topic | Database for the Exchange of Type Approval Documentation, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, and UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS) |
| Click here to view the full document file |
| EV/HFCV Retrofit Systems: Minutes of the 12th (September 2026) session |
| Reference Number: EV/HFCV-12-04 |
|
Minutes of the twelfth meeting of the IWG on EV/HFCV Retrofit Systems held 28 September 2026. The group adopted the provisional agenda and reviewed the work program, aiming to provide GRPE with a first draft of a future UN Regulation by 14–16 October 2026. The group focused on revising definitions in the draft UN Regulation, particularly EPRS definition, EPRS type, vehicle family, and installer provisions. Key unresolved issues include which components must remain identical within an approved type, alternative ways of grouping vehicles within a family, whether installer requirements should be included in the UN Regulation, and the scope regarding vehicles subject to UN Regulations Nos. 155 and 156. |
| Meeting Sessions: 12th EV/HFCV session (28 Sep) |
| Document date: 07 Oct 26 |
| Relevant to: UN Regulation No. 10 | Electromagnetic Compatibility, UN Regulation No. 100 | Construction and Safety of Electric Powertrains, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, and WP.29 Regulatory Project | Electric and Hydrogen Fuel-Cell Vehicle Retrofit Systems |
| Click here to view the full document file |
| UN R39: Proposal for a Supplement 3 to the 02 series of amendments |
| Reference Number: GRSG-132-14-Rev.1 |
|
Proposal to amend para. 5.12. to require the manufacturer’s management system encompassing cyber security to comply with the relevant requirements of UN R155 with regard to total distance indicated and total distance values, and to require threat and associated vulnerabilities to be analysed according to the management system with regard to total distance indicated and total distance values, with proportionate mitigations implemented including or equivalent to mitigation 7 referred to in Annex 5, Part B, Table B5, threat 20.4. of UN R155. The proposal aligns odometer anti-tampering and security management requirements with UN R155 and clarifies that mitigating measures must be implemented regardless of risk value assessment. |
| Submitted by: Netherlands |
| Meeting Sessions: 132nd GRSG session (28 Sep-2 Oct) |
| Document date: 30 Sep 26 |
| Relevant to: UN Regulation No. 39 | Speedometer Equipment and UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Electric Powertrain Retrofit Systems (EPRS): Final review of the draft UN Regulation |
| Reference Number: EV/HFCV-12-02 |
|
Proposal for a new UN Regulation establishing uniform provisions for type approval of Electric Powertrain Retrofit Systems (EPRS) designed for conversion of vehicles of categories M and N to full electric propulsion. The regulation does not apply to vehicles holding approval under UN R155 or UN R156. It sets out requirements for EPRS manufacturers, installers, markings, approval procedures, general and specific technical requirements for retrofit systems, installer authorization and training, documentation to be provided by manufacturers, conformity of production, modification and extension of approvals, and penalties for non-conformity. |
| Meeting Sessions: 12th EV/HFCV session (28 Sep) |
| Document date: 28 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, and WP.29 Regulatory Project | Electric and Hydrogen Fuel-Cell Vehicle Retrofit Systems |
| Click here to view the full document file |
| EV/HFCV Retrofit Systems: Minutes of the 11th (September 2026) session |
| Reference Number: EV/HFCV-11-04 |
|
Minutes of the eleventh meeting of the IWG on EV/HFCV Retrofit Systems held on 9 September 2026. The group adopted the provisional agenda and reviewed the draft UN Regulation on EV/HFCV retrofit systems. Key discussions addressed the regulatory concept for approval of the Electric Powertrain Retrofit System combined with installation requirements and vehicle testing, vehicle scope including possible exclusion of older vehicles and those subject to UN Regulations Nos. 155 and 156, and confirmation that HFCV provisions would remain as placeholders for later development. The updated working document will be circulated before submission to GRPE in October 2026. |
| Submitted by: EV/HFCV |
| Meeting Sessions: 11th EV/HFCV session (9 Sep) |
| Document date: 24 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, and WP.29 Regulatory Project | Electric and Hydrogen Fuel-Cell Vehicle Retrofit Systems |
| Click here to view the full document file |
| UN R155: Proposal to amend GRVA/2026/29 |
| Reference Number: GRVA-26-36-Rev.1 |
|
Proposal to amend paragraph AI to introduce a link between existing text in Part A and new text in Part C regarding vehicle transformations, and insert new Part C providing guidance for the application of UN Regulation No. 155 to transformed vehicles. The proposal adds section 6 clarifying that the requirement for the Certificate of Compliance and type approval to be issued by the same Approval Authority applies only within the scope of the type approval granted to the manufacturer concerned, and does not restrict another manufacturer from obtaining a separate type approval and associated Certificate of Compliance from the responsible Approval Authority. |
| Submitted by: UK |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 18 Sep 26 |
| Document status: Approved by GR |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| RE3: Proposal of provisions for PTI scan tools |
| Reference Number: PTI-44-02-Rev.1 |
|
Proposal to insert new clauses to section 8 of the Consolidated Resolution on the Construction of Vehicles (R.E.3) to add provisions 8.40.1. through 8.40.9. establishing requirements for:
|
| Submitted by: Japan and Russia |
| Meeting Sessions: 44th PTI session (17 Sep) |
| Document date: 18 Sep 26 |
| Relevant to: United Nations Agreement | RE3 Construction of Vehicles, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and WP.29 Discussion Topic | Electronic Technical Inspections |
| Click here to view the full document file |
| UN R155 and R156: Proposal to amend GRVA/2026/30 |
| Reference Number: GRVA-26-35 |
|
Proposal to amend para. 5.1.3., insert new paras. 5.1.5. and 5.1.5.1. requiring the Approval Authority to refuse type approval unless the Certificate of Compliance for the Cyber Security Management System is issued by the same Approval Authority granting vehicle type approval, while permitting referencing of certificates from other Approval Authorities under specific conditions with documented agreements and clarified responsibilities, and insert new paras. 5.4. and 5.4.1. with equivalent requirements for the Software Update Management System Certificate of Compliance. |
| Submitted by: UK, France, Luxembourg, Germany, and Netherlands |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 17 Sep 26 |
| Document status: Approved by GR |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| Draft priorities for GRVA in 2027 |
| Reference Number: GRVA-26-34 |
|
Document outlining GRVA’s priority activities for 2027 based on ECE/TRANS/WP.29/2026/1. GRVA will continue establishing and maintaining the United Nations regulatory framework for Automated Driving Systems, including UN R185 and GTR 26, with work on cyber security, over-the-air software updates, and the Data Storage System for Automated Driving. GRVA will focus on ADS implementation, provisions for Exchange of Scenario-Relevant Information, and elaboration of requirements for Advanced Driver Assistance Systems and Automated Emergency Braking Systems building on UN R79, 171, 131, and 152. |
| Meeting Sessions: 26th GRVA session (14-18 Sep) and 22nd ADS session (6-9 Oct) |
| Document date: 17 Sep 26 |
| Relevant to: UN Regulation No. 79 | Steering Equipment, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), GTR No. 26 | Automated Driving Systems, and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| Proposal for amendments to the 1958 Agreement regarding the voluntary acceptance of Certificates of Compliance |
| Reference Number: GRVA-26-21 |
|
Proposal to amend Article 2, paragraph 2 to clarify that where a Certificate of Compliance required under a UN Regulation and issued by an Approval Authority of another Contracting Party is accepted by a Contracting Party, the Approval Authority granting the corresponding type approval shall remain responsible for all aspects of that type approval. The amendment addresses management systems and their Certificates of Compliance used in UN Regulations such as UN R155 and UN R156. |
| Submitted by: CLCCR, CLEPA, and OICA |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Relevant to: United Nations Agreement | 1958 Agreement, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155/R156: Approval Authority for the COC of a CSMS/SUMS and type approval (vehicle type) |
| Reference Number: GRVA-26-20 |
|
Document explains concerns about the approach in GRVA/2026/30 to require a single Approval Authority to issue certificates of compliance for Cyber Security Management Systems and Automated Driving Systems Management Systems and vehicle type approval. The proposed changes would lead to double or triple approvals of management systems, creating administrative burden and unresolved legal consequences regarding challenged certificates of compliance and their effects on other issued certificates for the same management system. The submission proposes clarifying existing wording, documenting implications of challenged certificates, and adding a new paragraph 5.1.5. to UN R155 permitting mutual agreement between Approval Authorities regarding certificate usage. |
| Submitted by: CLCCR, CLEPA, and OICA |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Relevant to: UN Regulation No. 133 | Light Vehicle Recyclability, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| Informal Working Group on Cyber Security and Software Updates: Proposal for Terms of Reference |
| Reference Number: GRVA-26-19 |
|
Proposal to renew the terms for the Informal Working Group on Cyber Security and Software Updates under GRVA. The IWG shall maintain official documents on cyber security and software updates, develop amendments to UN R155 and UN R156 including provisions on software identification, support application across Global Technical Regulations, and provide opportunities for participants to share implementation experience. The IWG will be chaired by the United Kingdom, United States, and Japan, with OICA providing technical secretariat, and will operate until November 2029. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| Cyber Security and Software Updates informal group status report to GRVA |
| Reference Number: GRVA-26-18 |
|
Status report on activities of the IWG on CS/OTA since the 25th GRVA session. The IWG reviewed proposals for amendment of UN R155 and its interpretation document for multi-stage vehicles, proposals for approval-authority arrangements and Certificates of Compliance for UN R155 and R156, proposals integrating software identification and update text across several UNRs outlined in RE.3, component and STU approval concepts, and remote operation and automated driving systems. The IWG proposes updating regulatory text and interpretation documents for UN R155, revisions to software identification and update text across several regulations, and revised Terms of Reference for a mandate till November 2029. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Relevant to: UN Regulation No. 89 | Speed Limitation Devices, WP.29 Regulatory Project | Automated Driving Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Proposal to amend the Interpretation Document |
| Reference Number: GRVA-26-12 |
|
Proposal to amend paragraph AI to introduce a link between existing text in Part A and new Part C regarding vehicle transformations, insert new Part C providing guidance for the application of UN Regulation No. 155 to transformed vehicles including documentary evidence requirements, and add section 6 clarifying that the requirement for Certificate of Compliance and type approval to be issued by the same Approval Authority applies only within the scope of a specific type approval and its approval holder. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Document status: Formal GR review |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Software updates: Proposal to amend GRVA/2026/27 |
| Reference Number: GRVA-26-11 |
|
Proposal to insert definitions for Software Identification Number, insert requirements for manufacturers to provide necessary information allowing the Technical Service to uniquely identify hardware and software configurations, insert provisions allowing vehicle manufacturers to apply for new approvals to differentiate software versions for registered versus new vehicles, amend production discontinuation provisions to clarify that cessation is not deemed definitive if the manufacturer intends to obtain subsequent extensions for software updates of vehicles already registered in the market, renumber and insert new items in approval communication annexes regarding software identification and software updates including RxSWIN, and insert provisions allowing vehicle manufacturers to obtain new approvals for software version differentiation across multiple UN Regulations (13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178). |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 14 Sep 26 |
| Document status: Formal GR review |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 140 | Electronic Stability Control Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 139 | Brake Assist Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| CS/OTA Task Force: Minutes of the 39th (September 2026) session |
| Reference Number: TFCS-39-13 |
|
The UN IWG on Cyber Security and OTA issues held its 39th session on 3 September 2026. The provisional agenda (TFCS-38-01/Rev.3) and minutes from the 38th session (TFCS-38-13) were adopted. Regarding R155 amendments: multistage vehicle proposals (GRVA/2026/28, GRVA/2026/29, TFCS-39-08) will be submitted as informal documents with a merged paragraph; component approval proposals (TFCS-39-04) had STU references removed and discussion continues; remote operation for ADS proposals were not discussed but participants are invited to consider a general refresh of Annex 5. RXWIN application proposals (TFCS-39-05, TFCS-39-06, TFCS-39-07, TFCS-39-08, TFCS-39-09, TFCS-39-10, TFCS-39-11, TFCS-39-12) were presented; items 1, 4, and 6 were agreed, item 5 was agreed in principle, and items 2 and 3 regarding R155 and R157 applicability require revised wording. Netherlands expressed concerns about vehicle discontinuation and multiple type approvals. Administrative provisions regarding Type Approval Authority for CSMS/SUMS (GRVA/2026/30, TFCS-39-02, TFCS-39-07) were discussed without consensus. Out-of-scope vehicle approvals (TFCS-38-03) discussion was deferred to a separate workshop. Two informal documents will be provided to GRVA. |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 04 Sep 26 |
| Relevant to: United Nations Agreement | RE3 Construction of Vehicles, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Comments on GRVA/2026/28 concerning multistage vehicles |
| Reference Number: TFCS-39-08-Rev.1 |
|
Proposal to insert new paras. 27 and 28 in Part C Guidance for the application of UN Regulation No. 155 to transformed vehicles. Para. 27 states the requirement that the Certificate of Compliance and type approval are issued by the same Approval Authority applies only within the scope of the type approval granted to the manufacturer concerned. Para. 28 states where a vehicle manufacturer modifies a vehicle with existing type approval and applies for new type approval covering the modification, they need not use the same type approval authority as was used by the original vehicle manufacturer. |
| Submitted by: OICA, CLCCR, and CLEPA |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 03 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Position on GRVA/2026/30 |
| Reference Number: TFCS-39-07 |
|
OICA, CLEPA, and CLCCR oppose the requirement in GRVA/2026/30 for a single Approval Authority to issue the Certificate of Compliance for CSMS/SUMS and vehicle type approval. They contend the approach would create multiple approvals of the same Management System, imposing administrative burden and creating unresolved legal consequences if a CoC is challenged. The organizations propose adding a new paragraph 5.1.5. instead of paragraph 5.1.3. e) to permit mutual agreement between Approval Authorities, allowing usage of a CoC issued by another Approval Authority, with such agreement documented in type approval documentation. |
| Submitted by: OICA, CLCCR, and CLEPA |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 02 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R13 / UN R13-H / UN R79 / UN R89 / UN R131 / UN R130 / UN R178 / UN R155 / UN R156 / UN R152 / UN R157 / UN R171 / UN R175: Proposal to amend GRVA/2026/27 |
| Reference Number: TFCS-39-06 |
|
Proposal to amend GRVA/2026/27, which proposes amendments to UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R139, UN R140, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178:
|
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 02 Sep 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, United Nations Agreement | RE3 Construction of Vehicles, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 140 | Electronic Stability Control Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| CS/OTA Task Force: Agenda for the 39th (September 2026) session |
| Reference Number: TFCS-39-01-Rev.2 |
|
The agenda includes adoption of the provisional agenda and minutes from the thirty-eighth session; proposals for amendments to R155 concerning multistage vehicles, separate technical units and component approval, and remote operation for automated driving systems; review of cyber and software requirements in the ADS Regulation; application of RXSWIN to R156; administrative provisions in R155 and R156 regarding Type Approval Authority for CSMS/SUMS and issuing approvals for out-of-scope vehicle types; and preparation of GRVA 26. |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 02 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Concept for approval of components |
| Reference Number: TFCS-39-04 |
|
This document presents a concept for approvals of electrical/electronic sub-assemblies (ESAs) as components according to UN R155, and the installation of such approved components on vehicles already holding UN R155 approval. The proposal removes the possibility of separate technical unit (STU) approvals as a first step, limiting coverage to components connected only to power and/or reading data through approved existing interfaces. The document restructures UN R155 into three parts: Part I covers vehicle type approvals; Part II covers ESA component approvals with cybersecurity requirements; Part III covers vehicle type approvals regarding installation of approved ESAs. Requirements include cybersecurity management systems, risk assessments, threat mitigations, and reporting provisions for development, production, and post-production phases. |
| Submitted by: UK |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 28 Aug 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Proposal to amend the Interpretation Document |
| Reference Number: TFCS-39-02 |
|
Proposal to amend Paragraph B to insert new requirement 5.1.3 establishing that the Approval Authority or Technical Service shall refuse to grant type approval regarding cyber security where the vehicle manufacturer has not fulfilled requirements in paragraph 7.3., notably that the Certificate of Compliance for the Cyber Security Management System has not been issued by the same Approval Authority granting the type approval, add explanatory text clarifying that this ensures Article 2(2) of the 1958 Agreement compliance while permitting cooperation between Approval Authorities and acceptance of prior documentation, amend Paragraph K to remove existing guidance text in paragraphs 6.1 and 7.1 regarding Certificate of Compliance issuance and inter-Authority arrangements, and insert statement that no guidance is included regarding paragraph 6 requirements. These changes support proposal GRVA/2026/30. |
| Submitted by: UK |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 28 Aug 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Proposal for amendments to UN Regulations Nos. 13, 13-H, 79, 89, 130, 131, 152, 155, 156, 157, 171, 175, and 178 |
| Reference Number: GRVA/2026/27 |
|
Proposal to insert provisions on Software Identification Numbers and software updates across UN R13, R13-H, R79, R89, R130, R131, R152, R155, R156, R157, R171, R175, and R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7 paragraph 2, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance with test reports, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered vehicles from new vehicles where type approval regulations are updated or hardware changes occur in series production with test duplication avoided where possible, clarifying that production is not considered definitively discontinued if manufacturers obtain subsequent extensions for software updates of registered vehicles, renumbering and inserting new items in approval communication annexes for R13SWIN, R13-HSWIN, R79SWIN, R89SWIN, R130SWIN, R131SWIN, R152SWIN, R155SWIN, R157SWIN, R171SWIN, R175SWIN, and R178SWIN information including whether held on vehicle and relevant parameter identification lists, and amending R157 and R171 to align software update requirements with R156 technical specifications and transitional provisions. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 06 Jul 26 |
| Document status: Formal GR review |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| UN R155: Proposal for a Supplement |
| Reference Number: GRVA/2026/29 |
|
Proposal to insert new Part C providing guidance for the application of UN R155 to transformed vehicles. Part C addresses identification of cyber-relevant transformations, impact on original vehicle architecture, connection risks, and impact on cyber security management systems. It specifies that transformations require new approval unless the manufacturer provides clear evidence that the original approval remains valid, and outlines critical factors and examples of cyber-relevant actions. It details documentary evidence expected from manufacturers regarding functional descriptions, connections with original vehicle types, added components and functions, and arguments demonstrating negligible intrinsic risk. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 06 Jul 26 |
| Document status: Formal GR review |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Proposal for a Supplement |
| Reference Number: GRVA/2026/28 |
|
Proposal to amend para. 5.3.2. to require notification of assessment methods and criteria including paras. 8.2. and 8.3., insert new paras. 8.2. and 8.3. establishing criteria for equipment installation without further assessment, and amend Annex 1 to require disclosure of equipment excluded from assessment pursuant to paras. 8.2. and 8.3. The amendments clarify that equipment with negligible intrinsic cyber security risk installed according to manufacturer specifications and not introducing cyber security risk, and standard non-automotive equipment connected solely for power supply with no increased cyber security risk, shall not invalidate approval of the original vehicle type under UN Regulation No. 155. |
| Submitted by: TFCS |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 03 Jul 26 |
| Document status: Formal GR review |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Proposal to amend UN R155 and UN R156 |
| Reference Number: GRVA/2026/30 |
|
Proposal to amend UN R155 by inserting new para. 5.1.3.(e) establishing that the Certificate of Compliance for the Cyber Security Management System shall not be issued by a different Approval Authority than the one granting type approval, and amend UN R156 by inserting new para. 5.4. establishing that Approval Authorities shall not grant type approval if the Certificate of Compliance for the Software Update Management System has not been issued by the same Approval Authority granting type approval. Justification includes ensuring holistic cybersecurity assessment, clarifying reporting obligations under para. 7.2.2.2.(g), addressing unharmonized mutual recognition of management system certificates, maintaining consistency between regulations, and upholding the fundamental principle that approval authorities retain responsibility for all aspects of type approval. |
| Submitted by: France, Germany, Luxembourg, Netherlands, and UK |
| Meeting Sessions: 26th GRVA session (14-18 Sep) |
| Document date: 03 Jul 26 |
| Document status: GR approved as amended |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| CS/OTA Task Force: Minutes of the 38th (June 2026) session |
| Reference Number: TFCS-38-13 |
|
The UN IWG on Cyber Security and OTA held its 38th session 29 June–1 July 2026 in London with remote participation. The group adopted the provisional agenda and minutes from the 37th session. Three items from the IWG were presented at the May GRVA meeting: multistage vehicle documents to become working documents for September; RXWIN documents with elements in square brackets to be resolved; and SUMs document returned for further discussion. For R155, the group agreed to forward multistage amendment proposals as working documents to September GRVA. The UK proposal on STU and component approval for R155 was discussed extensively; the UK will draft a proposal for components only. The UK proposal on remote operation for ADS requires further development. The group will review ADS GTR cyber and software provisions. RXWIN proposal documents were adapted; R155 was removed and R89 and R156 sections amended; reviewers may address concerns by 31 July 2026. Germany’s proposal requiring the same Type-Approval Authority for CSMS and vehicle type approval was discussed; a dedicated meeting will be scheduled. The UK proposal on approvals for out-of-scope vehicle types was introduced. Draft Terms of Reference were revised and will be forwarded to GRVA for September approval. The next meeting is scheduled for 3 September 2026, 12:00–15:00 CET. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 03 Jul 26 |
| Relevant to: United Nations Agreement | RE3 Construction of Vehicles, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, GTR No. 26 | Automated Driving Systems, and UN Regulation No. 185 | Approval of vehicles with regard to their Automated Driving Systems |
| Click here to view the full document file |
| Cyber security: Vehicle modification use cases |
| Reference Number: TFCS-38-11 |
|
The document presents vehicle modification use cases categorized into four cases and additional scenarios. Case 1 covers components with negligible risk or cyber-relevant non-automotive devices. Case 2 addresses cyber-relevant automotive devices approved to specific regulatory requirements, requiring installation approval and vehicle type re-approval. Case 3a addresses cyber-relevant devices not approved to specific requirements, requiring component or STU approval. Case 3b covers devices controlling vehicle functions, also requiring component or STU approval. Case 4 encompasses invasive modifications or complex interactions not covered by other cases. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 01 Jul 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Cyber security: Modifications to GRVA-25-30 |
| Reference Number: TFCS-38-12 |
|
Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| CS/OTA: Draft updated terms of reference |
| Reference Number: TFCS-38-02-Rev.1 |
|
The Informal Working Group on Cyber Security and Software Updates will continue to consider how cyber security and software updates have a bearing on automotive safety and security, and whether any changes are necessary to the Regulations and guidance it has produced under WP.29. In particular, the IWG shall maintain official documents regarding UN R155, UN R156, and Recommendations on uniform provisions concerning cyber security and software updates; develop amendments to relevant documents; develop a proposal to amend UN Regulations under the responsibility of GRVA to record details of an RXSWIN where applicable which have been mandated by the 01 series of UN Regulation No. 156; develop proposals to amend UN Regulation No. 155 and its interpretation document to support application in national/regional frameworks for aspects such as multi-stage manufacturing; consider and develop deliverables regarding software updates after registration potentially creating a proposal for modification to the type approval numbering or a classification of update categories; support and review the application of cyber security and software update provisions across GRs notably for the Global Technical Regulation on Automated Driving Systems; and provide opportunities to participants to share knowledge, experience and ideas from implementation of national regulation/standards regarding CS/OTA as well as UN R155 and R156. The IWG will continue its activities until November 2029. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Proposal to amend GRVA-25-32 |
| Reference Number: TFCS-38-10 |
|
Amend para. AI to replace the heading “Examples of documents/evidence that could be provided” with “Explanation of the requirement” and insert text stating that Part C of this document provides further guidance on the application of the Regulation to vehicles which have been modified by carrying out a transformation of the vehicle. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| Component/STU type approval under UN R155 |
| Reference Number: TFCS-38-09 |
|
CLEPA welcomes questions raised by Japanese experts under doc TFCS-37-06 and identifies points requiring further clarification regarding component and STU type approval scope, technical integration, STU definition, implementation, risk assessment, impact and benefit, and post-market monitoring. CLEPA proposes that components or STUs required for initial vehicle type approval under Part I should not be subject to separate approval under Part II, noting that vehicle cybersecurity depends on vehicle-level system interactions and E/E architecture, the OEM has full visibility of system architecture, and Part I approval ensures integrated assessment. |
| Submitted by: CLEPA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Proposal to address approvals by one or more authorities |
| Reference Number: TFCS-38-08 |
|
Proposal to add para. 3.2.3.1. requiring manufacturers to provide additional information on the Cyber Security Management System at request of the Approval Authority when the Certificate of Compliance for CSMS is issued by a different Approval Authority, add para. 5.1.5. allowing the Approval Authority to refuse type approval if insufficient information on the CSMS and its implementation was provided, and add para. 7.4.1.1. requiring all granting Approval Authorities to be included in reporting when different Approval Authorities are used for the Certificate of Compliance for CSMS and type approval of the vehicle type. |
| Submitted by: OICA and CLEPA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| CS/OTA Task Force: Agenda for the 38th (June 2026) session |
| Reference Number: TFCS-38-01-Rev.3 |
|
The agenda includes review of proposals for amendments to R155 concerning multistage vehicles, separate technical units and component approval, approval-authority requirements for CSMS CoC and vehicle type approval, and remote operation for ADS; review of cyber and software requirements in the ADS Regulation based on WP.29/2022/60 as amended by WP.29/2023/87; discussion of RXWIN application amendments; and consideration of terms of reference renewal ahead of mandate expiration in November 2026. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 29 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Review of points for approval of separate technical units |
| Reference Number: TFCS-38-06 |
|
A comprehensive cyber security risk assessment without gaps between Parts I, II, and III is required for component or separate technical unit approval. Risk assessment is difficult for manufacturers alone; contracts are required to share vulnerability information. Identification of realistic installation use cases, information sharing between approval authorities, and clarification of responsibilities are necessary. Components with no communication to the vehicle or only mechanical and power connection do not require new approval. Components sending data to the vehicle or controlling it require Part II approval and joint risk analysis by the original equipment manufacturer and installer. |
| Submitted by: NTSEL |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 26 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Response to questions concerning separate technical unit approvals |
| Reference Number: TFCS-38-05 |
|
Answers to questions on separate technical unit approvals under UN R155 clarify that a base vehicle must already hold an R155 type approval before an ESA can be added at Part III; approval authorities for different parts may differ with mutual recognition applying; the end of support period for an ESA manufacturer must be communicated to the vehicle manufacturer, with implications to be discussed by the IWG; installation of ESAs must follow vehicle manufacturer instructions without necessarily requiring separate agreement; STU data sharing agreements are required; and after ESA installation, a whole vehicle cyber security risk assessment is not necessary, though Part III must consider risks where ESA and base vehicle interactions occur. A working document is planned for submission to GRVA in January 2027. The IWG will explore whether Part II components may include equipment from certificated base vehicles under UN R155 multi-stage categorization and discuss incorporating STU into original approvals. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Questions concerning separate technical units |
| Reference Number: TFCS-38-04 |
|
Questions address whether minimum vehicle architecture approval should be required before Part III can be used for additional devices; whether approved ESAs can be incorporated in original vehicle approval or as an extension to Part I approval; whether different terminology should replace CSMS for Part III approvals; whether second Part III approvals are permissible for vehicles already approved to Parts I and III; and what implications arise from end-of-support by ESA manufacturers. |
| Submitted by: UK |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155 and R156: Approvals for ‘out-of-scope’ vehicles |
| Reference Number: TFCS-38-03 |
|
Vehicles of categories M1, N, O, R, S and T may fall out of scope of UN R155 or UN R156 if they lack ECUs or do not permit software updates. Approval authorities currently make individual determinations regarding whether vehicles are in or out of scope, and justification for out-of-scope decisions must be recorded to ensure vehicles remain out of scope during the lifetime of whole vehicle approval. UN Regulation No. 10 provides precedent by allowing approvals for vehicles where certain equipment is not relevant. A similar provision could be incorporated into UN R155 and UN R156 by amending the scope and adding provisions to section 5 allowing manufacturers to obtain approvals for vehicles that do not permit software updates, with requirements of paragraph 7 not applying. |
| Submitted by: VCA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| Request for guidance on vehicle compliance after the end of production |
| Reference Number: GRVA-25-48 |
|
The document requests guidance on the legal basis for provisions within UN Regulations extending beyond the End-of-Production date and which authority such provisions address. Examples include UN R171 requirements for manufacturers to demonstrate safety management systems to the Type Approval Authority every three years and report annually on Driven Coded Auxiliary System operation until production is discontinued, and UN R155 requirements for Cyber Security Management Systems to apply to the post-production phase when vehicles remain operational but are no longer produced. The document poses an additional question regarding vehicle safety when manufacturers cease operations and cannot fulfill post-deployment safety provisions. |
| Submitted by: Germany |
| Meeting Sessions: 25th GRVA session (18-22 May) |
| Document date: 21 May 26 |
| Relevant to: United Nations Agreement | 1958 Agreement, WP.29 Regulatory Project | Automated Driving Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS) |
| Click here to view the full document file |
| CS/OTA Task Force: Minutes of the 37th (April 2026) session |
| Reference Number: TFCS-37-12 |
|
The CS/OTA Task Force held its thirty-seventh session on 21-22 April 2026 by video conference. The group adopted the provisional agenda and minutes from the thirty-sixth session. Discussions addressed proposals for amendments to UN R155 concerning multi-stage vehicle approvals and separate technical units, for which a subworking group was established. Proposals were also considered on type approval authority responsibility for cyber security management systems and remote operation of automated driving systems. The group reviewed cyber and software requirements in the ADS GTR and WP.29/2022/60 as amended by WP.29/2023/87, and discussed application of RXSWIN to UN Regulations, selecting option 2 for presentation to GRVA with R155, R156, and R89 square bracketed. The IWG mandate renewal was discussed, with potential new items including component and STU approval and software numbering proposals. |
| Meeting Sessions: 37th TFCS session (21-22 Apr) |
| Document date: 21 May 26 |
| Relevant to: UN Regulation No. 89 | Speed Limitation Devices, WP.29 Regulatory Project | Automated Driving Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
No matching documents.