UN R155 R156 Controversies

Stefan Coetzeecreated 2026-05-12updated 2026-06-081 min readcross-cutting
Vault note, not reviewed against the source. Written in the knowledge vault on 2026-05-12 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

UN R155 / R156 Controversies

Type-approval focus vs lifecycle reality

Regulations focused on type-approval moment:

  • Continuous cybersecurity post-approval less directly addressed.
  • Software-defined vehicle continuous evolution mismatches type-based approval.
  • Vehicle owners experience post-approval cybersecurity events.

Smaller manufacturer burden

CSMS / SUMS overhead significant:

  • Smaller manufacturers (niche, specialty) face disproportionate compliance cost.
  • Some smaller OEMs / converters concerned.

Assessment variance across authorities

Type approval authorities vary in CSMS / SUMS assessment depth:

  • Some thorough, others lighter.
  • Mutual recognition transfers variance.
  • Industry concerns over forum-shopping.

AI / autonomous-driving outpacing regulation

R155 published 2020:

  • AI-feature specifics not deeply addressed.
  • Adversarial ML threats not fully covered.
  • Updates lag autonomous-driving progress.

OTA complexity vs simple type approval model

OTA updates complicate type approval:

  • RxSWIN change triggers re-approval workflow.
  • Frequent updates ⇒ frequent approvals.
  • OEM operational impact.

Counterpoint

  • Mandatory teeth produced industry uplift.
  • ISO 21434 / ISO 24089 implementation path clear.
  • Mutual recognition useful.
  • OEM-supplier coordination forced.

See also