Is this a certified ISO/SAE 21434 or UN R155 assessment?

No. A TARA run is decision-support: a cited risk register you take into type approval, an audit, or an internal review. Ansvar never issues the approval and never claims certification.

How is a TARA different from a STRIDE threat model?

STRIDE enumerates threats per component; a TARA produces a risk register — each risk banded for likelihood and consequence, scored against thresholds you set, with a recorded treatment. Ansvar runs both; teams often run STRIDE first and feed the threats into the TARA.

What does a run actually produce?

A risk register aligned to ISO 31000/31010 and NIST 800-30: risks with likelihood and consequence bands, scores against your thresholds, and treatments. The complete register comes back as structured data, which is what your agent reads. Rendered documents are the hand-off: Team and Company export it as HTML, PDF or DOCX.

Do I need to upload documents to run one?

No. The TARA family is interview-grounded: your agent asks, you answer, the server enforces what a complete answer looks like. Document-grounded evidence workflows (paragraph-cited review of your own TARA reports and CSMS packs) run on Team and above.

Which AI clients can run it?

Claude runs the full TARA interview loop today. Any OAuth-capable MCP client can connect to the gateway, but a long staged workflow asks more of a client than research does — the clients guide in our docs lists what each one handles. A run persists across sessions until you finish it.

Workflow · TARA

TARA — Threat Analysis & Risk Assessment

Risk assessment for vehicles, OT, rail, robots and drones — risks banded on NIST 800-30 scales, every regulatory anchor fetched and cited, or marked unresolved.

Ansvar is a gateway for the AI assistant your team already uses — Claude, Microsoft Copilot, any MCP client. Connect it and your agent runs the workflow; the server enforces the stages and fetches every citation.

Compare plans

Automotive · OT · railplus robotics and drones, on one risk spine

ISO 31000process; 31010 techniques; NIST 800-30 scales

21434 · 62443 · R155anchors fetched and cited, or marked unresolved

A TARA in Ansvar runs as a staged workflow: the gateway holds each stage open until it is answered. You scope the system, confirm the risk list, analyse and treat each risk, and pass an evaluation gate before the report exists. Your own AI client does the interviewing over MCP; the gateway fetches every standard clause map and legal anchor it cites. The sector variants share one enterprise risk spine, so an automotive TARA and a rail TARA score risks on the same defined bands.

the family

One risk spine, a variant per sector

Enterprise Risk Assessment (ISO 31000 / 31010 / NIST 800-30G)

The spine: ISO 31000 process, ISO 31010 techniques, NIST 800-30 scales.

Automotive TARA — ISO/SAE 21434 & UNECE R155 Threat Analysis & Risk Assessment

Vehicle systems and ECUs, with UN R155 CSMS evidence in scope.

OT / ICS / Machinery TARA — Threat Analysis & Risk Assessment

Plant and machinery on IEC 62443 zones and conduits.

Rail / Railway TARA — Threat Analysis & Risk Assessment (CLC/TS 50701, IEC 62443)

Rail systems per CLC/TS 50701 practice.

Robotics / Cobot TARA — Threat Analysis & Risk Assessment for industrial and collaborative robots

Industrial and collaborative robots.

UAS Threat Analysis & Risk Assessment (TARA)

Drone platforms and their C2 links.

Counter-UAS & Hostile-Takeover Resilience Assessment

Counter-UAS and hostile-takeover resilience.

ICS Advisory-to-Risk — current advisory exposure for an OT asset inventory

Turns current ICS advisories into scored exposure for your OT inventory.

Standards ground the workflow as clause maps and cross-references — not the standard text, unless you license it. Buyers who hold SS-ISO/SAE 21434 through the SIS add-on get the clause text cited inside the run.

how a run works

Five stages the server enforces

1
Scope, context, criteria
asset, event or objective mode; you set the bands and thresholds
2
Risk identification
the workflow proposes, you confirm the list — nothing scores unseen
3
Per-risk analysis & treatment
likelihood and consequence banded, treatment recorded per risk
4
Evaluation & compliance gate
scores meet your thresholds or the gate says why not
5
Report
the risk register — structured for your agent, rendered for your auditor

ask your agent

Paste one of these to start

Using Ansvar, start an automotive TARA for our telematics ECU. Scope it to ISO/SAE 21434 with UN R155 CSMS evidence in mind.

Using Ansvar, run an OT TARA for the packaging line PLCs — IEC 62443 zones and conduits, event mode.

Using Ansvar: which TARA and risk-assessment workflow types can my tier start? List them with what each produces.

install the skill

A prompt starts one run. The skill is the same guidance installed once — the run loop, the evidence and citation rules, and the starters — so your agent works this way in every conversation, not only the ones you remember to paste into. Install it as a skill in Claude or Claude Code, or paste the same file into Microsoft Copilot or a custom GPT's instructions.

Threat Analysis and Risk Assessment · version 1.0.4 · SKILL.md · ZIP · how to install it

The TARA family runs on Premium and above — run allowances and what each tier adds live on the pricing page.

Questions buyers ask first

Is this a certified ISO/SAE 21434 or UN R155 assessment?: No. A TARA run is decision-support: a cited risk register you take into type approval, an audit, or an internal review. Ansvar never issues the approval and never claims certification.
How is a TARA different from a STRIDE threat model?: STRIDE enumerates threats per component; a TARA produces a risk register — each risk banded for likelihood and consequence, scored against thresholds you set, with a recorded treatment. Ansvar runs both; teams often run STRIDE first and feed the threats into the TARA.
What does a run actually produce?: A risk register aligned to ISO 31000/31010 and NIST 800-30: risks with likelihood and consequence bands, scores against your thresholds, and treatments. The complete register comes back as structured data, which is what your agent reads. Rendered documents are the hand-off: Team and Company export it as HTML, PDF or DOCX.
Do I need to upload documents to run one?: No. The TARA family is interview-grounded: your agent asks, you answer, the server enforces what a complete answer looks like. Document-grounded evidence workflows (paragraph-cited review of your own TARA reports and CSMS packs) run on Team and above.
Which AI clients can run it?: Claude runs the full TARA interview loop today. Any OAuth-capable MCP client can connect to the gateway, but a long staged workflow asks more of a client than research does — the clients guide in our docs lists what each one handles. A run persists across sessions until you finish it.

as a service

Prefer we run it?

Every workflow here is also an expert-run service: we run it against your systems, review the output as practitioners, and hand over the finished deliverable. See the services page for how engagements work, or contact us to scope one.

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