For your team
Same ECUs, different jobs. How each team uses AutoST.
An OEM security team, a Tier-1 test group, a test lab and a compliance manager need different things from the same test run. Each page describes the job, the typical setup and a sensible first project.
In short
AutoST is used by OEM product security teams, Tier-1 and Tier-2 supplier test groups, independent test labs and engineering service providers, ISO/SAE 21434 and UN R155 compliance managers, and CI/CD engineers who want ECU security tests on every build. For each role the pages describe the use case, the setup and the first project.
Roles and companies
Find your page
AutoST for CI/CD Engineers: ECU Security Scans as a Pipeline Gate
How CI/CD and test automation engineers trigger AutoST ECU scans from a pipeline through the REST API or the Bamboo plugin, gate builds on risk and archive evidence.
Engineering servicesAutoST for Engineering Service Providers: Security Testing Across Projects
How engineering service providers use AutoST to run one ECU security test method across client projects, keep client data apart and hand over evidence clients accept.
ISO 21434AutoST for ISO/SAE 21434 Compliance Managers: Test Evidence You Can Trace
How cybersecurity and compliance managers use AutoST test runs as traceable verification evidence for ISO/SAE 21434 work products and UN R155 audits.
OEMAutoST for OEM Security Teams: Supplier ECUs, Gateways and Vehicle Networks
How OEM security teams use AutoST to check supplier ECUs and gateways with one repeatable test set, and file the results as evidence for ISO/SAE 21434 and UN R155.
Test labsAutoST for Test Labs: One Repeatable Baseline for Every Client ECU
How independent test labs use AutoST to run the same documented baseline on every client ECU, keep clients apart, and free their experts for the manual pentest work.
Tier-1AutoST for Tier-1 Suppliers: Test Your ECU Before the OEM Does
How Tier-1 suppliers use AutoST to test their own ECUs against the OEM cybersecurity requirements before each sample phase, and hand over evidence that holds in an audit.
See it on your ECU
What would this look like on your bench?
In a free one-hour session we go through your ECUs, interfaces and release process and sketch a pilot that fits.
- Which ECUs and interfaces to start with
- How results feed your 21434 work products
- A pilot plan with effort and timeline
Your demo is withTom ZaubermannFounder of Zyberum, ex-lead of the VW InCar Security Testing Lab
Already trusted by Tier 1, Tier 2 suppliers and OEMs. References on request.
Or send us a message
We reply within one business day.