RE4ATara
RE4ATara works at the risk-assessment end of the ISO/SAE 21434 lifecycle.
Early access
Early access means a running build.
There is a build, and it runs — but no shipping product or published screen yet.
Where it sits
From ISO/SAE 21434 TARA to an executable test plan.
Cybersecurity is continuous under ISO/SAE 21434.
Threat analysis and risk assessment
Assets and damage scenarios, threat scenarios and attack paths, impact × attack feasibility, then risk treatment — ISO/SAE 21434 Clause 15.
RE4ATara works here
Cybersecurity requirements
A cybersecurity goal for each risk to be reduced, with requirements allocated to ECU, interface and bus.
An executable test plan
Requirements resolved into tests a bench can run. Testing Studio's AI Assist, available to demo, can propose them from a TARA workbook.
Execution and evidence
The run on the bench, and the record it leaves behind.
Findings loop back.
Threat classes
STRIDE is the shared vocabulary.
A bench finding uses the same terms as the TARA.
The six STRIDE categories
Spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege.
- SSpoofing
- TTampering
- RRepudiation
- IInformation disclosure
- DDenial of service
- EElevation of privilege
Separate products, sold separately.
RE4ATara and RE4A Testing Studio are licensed and started separately, with no data link between them. They do not compose into a single platform. Testing Studio's AI Assist, available to demo, reads a TARA workbook whichever tool wrote it — a file you hand over, not a link between the products.
- RE4ATara
- RE4A Testing Studio
Evaluate it
See it run against a real ECU — with no hardware on your side.
Rest-bus simulation around one real ECU. No hardware needed.