Do you give us the ISO/SAE 21434 text?

By default, ISO/SAE 21434 and the diagnostic standards are surfaced as requirement and clause mappings with Ansvar cross-references, not the reproduced standard. But the ISO/SAE 21434 text itself — licensed and cited verbatim inside your workflows — is available as the SIS-licensed standards add-on, one of the five standards live today; see /standards. UN R155 and R156 are the regulations, addressable provision by provision.

Does this produce a type-approval verdict?

No. The TARA and CSMS/SUMS gap analyses are decision-support — cited evidence you take into the type-approval process, not the approval itself.

Sector · Automotive

Automotive

Make your TARA — and your CSMS evidence — hold up to UN R155 type approval.

Ansvar is a gateway for the AI assistant your team already uses — Claude, Microsoft Copilot, any MCP client. Connect it, and every answer below comes back cited to the provision or marked unresolved.

See full coverage

R155 · R156provision-level

11automotive scopes, type-approval to circularity

TARAISO 21434 clause map + threat analysis

Vehicle law and vehicle cybersecurity in one lane. UN R155 and R156 are addressable provision by provision, and the EU type-approval estate sits beside them: the type-approval and vehicle-safety acts, emissions and environment, L-category vehicles, agricultural and forestry tractors, in-service and road use, circularity and materials, in-vehicle data access, repair and maintenance information, and the UN ECE regulations as published in the Official Journal. ISO/SAE 21434 and the diagnostic standards are clause maps with Ansvar cross-references rather than the standard text; 21434 is one of the standards you can licence in through the SIS module when you want it cited verbatim. Run the TARA, the CSMS gap, or an ECU effective-risk pass and cite every finding.

what we cover

The law and standards we ground on

Regulation

UN R155 (cybersecurity) · UN R156 (software update)

addressable provision-level

Regulation

EU vehicle type-approval & safety

the type-approval framework and the vehicle-safety acts, article-level from EUR-Lex

Regulation

EU automotive emissions & environment

article-level from EUR-Lex

Regulation

EU L-category and agricultural / forestry tractor type-approval

the two type-approval regimes outside the M/N vehicle classes

Regulation

EU automotive in-service & road use · circularity & materials

roadworthiness and in-use duties, and the end-of-life, recyclability and materials rules

Regulation

UN ECE vehicle regulations

the UN regulations as published in the EU Official Journal, alongside R155 and R156

Regulation

In-vehicle data access for connected vehicles

the EU rules on access to vehicle-generated data

Regulation

Repair & maintenance information access — RMI / SERMI

Reg (EU) 2018/858

Standard

Control mapping: ISO/SAE 21434

requirement mapping + cross-references — the ISO/SAE 21434 text itself is available as the SIS-licensed add-on (/standards)

Standard

Control mapping: automotive engineering & diagnostics stack

33 standards and 703 clause entries — UDS (ISO 14229), DoIP, SOVD, AUTOSAR diagnostics, ISO 15765-2, LIN (ISO 17987), ISO 22737 low-speed automated driving and ISO 27145 WWH-OBD — clause mapping, not the standard text

Law

Chinese national law

national laws of the NPC and its Standing Committee, legislative decisions and State Council administrative regulations from flk.npc.gov.cn, in Chinese original with Ansvar-authored English metadata. Local regulations, judicial interpretations and departmental rules are not yet served. GB/GB-T standard body text is excluded; this listing does not establish Chinese market approval or equivalence with ISO standards.

Regulation

Horizontal: Cyber Resilience Act · GDPR (connected-vehicle data)

what you can do

Workflows that turn it into evidence

assembledPremium

Vehicle threat model & TARA

ISO/SAE 21434 over the ECU and asset model — an available analysis, not a type-approval verdict

Team

UN R155 CSMS gap analysis

cybersecurity-management-system evidence for type approval

Team

UN R156 software-update gap analysis

SUMS evidence for software-update management

Team

Effective-risk CVE rescoring

re-rank ECU and component vulnerabilities with CISA KEV / EPSS context — never exploit code

Team

Document review, paragraph-cited

TARA reports and CSMS/SUMS evidence packs against R155/R156

assembledPremium

Vehicle-law research as cited answers

type-approval, emissions, in-service, circularity, data access and the UN regulations, every answer cited to the provision

STRIDE threat-model workflows run on every plan against a system you describe — 1 run a month on Free, 2 on Solo, 5 on Premium, which also adds the LINDDUN and TARA families, the rendered reports, and case law inside the run. Document-grounded workflows run on Team and Company. Every tier runs the same corpora as cited research inside your own AI client.

Questions buyers ask first

Do you give us the ISO/SAE 21434 text?: By default, ISO/SAE 21434 and the diagnostic standards are surfaced as requirement and clause mappings with Ansvar cross-references, not the reproduced standard. But the ISO/SAE 21434 text itself — licensed and cited verbatim inside your workflows — is available as the SIS-licensed standards add-on, one of the five standards live today; see /standards. UN R155 and R156 are the regulations, addressable provision by provision.
Does this produce a type-approval verdict?: No. The TARA and CSMS/SUMS gap analyses are decision-support — cited evidence you take into the type-approval process, not the approval itself.

Run it against your own systems

Connect the AI client you already use and ask your first cited question — Free, Solo, Premium and Team are self-serve.

Setup guide

Building automotive compliance? It works today — we take on a few design partners per sector to tune it to your team.