Not part of a guided workflow —
Next best move:Open the platform atlas Atlas

CEO dashboard

One vehicle. Its suppliers. The attack path.

Supplier links appear only from authorized evidence. The replay is a simulation — no live systems are touched.

Supplier map

Add evidence

Identify a vehicle to see its authorized parts, suppliers and known vulnerabilities.

Vehicle dossier

The exploded view and Cyber MRI open once a vehicle is identified.

Attack replay

Vehicle in scope

No vehicle selected — the replay below is a labelled fixture

Control heldSynthetic reference demonstrationEvidence: Synthetic fixture

A valid fixture account crossed the vehicle-record ownership boundary.

Applicability to the selected vehicle is not established

Step 1 of 8
Simulated · nothing executedModelled reference vehicle

Choose how the attacker gets in.

One choice starts the story. The car, the attacker and the evidence appear one step at a time.

Model vehicle used in the simulated story
T1195.002

Compromise Software Supply Chain

Scope: RUN-CSVC-REF-0007 · VIN-gated simulation · No live actions

Current blocking fact

Release canary-2026-09-18 → RUN-CSVC-REF-0007: release assigned to scope?

The simulated supplier-to-release mechanism is ready to inspect. Accepted records decide whether its final links apply to this VIN.

Next passive action: Request supplier release / ota manifest from Supplier release engineering.

Evidence coverage2 / 5

Unresolved · Insufficient evidence

3 open facts

ROUTE-RESOLVER-1.0.0 · AL-ROUTE-1.0.0Fixture data · passive records only

The attempt enters through a service associated with the vehicle

Assumed

The question is whether the service checks which vehicle this account may access.

Defensive instrument in focus

HTTP inspect and replay adapter (Burp Repeater equivalent)

adapter 1.4.0 · HTTPS request/response · WebSocket message

MITRE ATT&CK instructional lead

Mapping pending · No exact mapping

Not mapped at this replay position

Specific use in this step

Select the instrument that can answer the authorization question.

The question is whether the service checks which vehicle this account may access.

Fictional account LAB-ACCT-A

Fixture source

HTTP inspect and replay adapter (Burp Repeater equivalent)

Instrument active

Isolated connected-service fixture

Boundary under test

Vehicle scope

Vehicle scope not loaded

No vehicle selected

Scope, not impact
Unresolved release-to-VIN link

The ATT&CK method is applied to the synthetic release path associated with this vehicle scope. It does not establish installation, execution, control, or impact on this vehicle.

Deterministic route reconstruction
Click any system for evidence detail
VALID SESSION · EVIDENCEDAUTHENTICATE · EVIDENCEDGATE ABSENT IN DEFECTIVE FIXTURE · UNRESOLVEDRECORD RETURNED · EVIDENCEDNO PATH DEMONSTRATED · ASSUMPTION
Signal path: accepted evidence onlyAmber: unresolved · dotted: assumption

Expected

An instrument that issues a controlled, bounded request and records both sides of the exchange.

Observed

Tool selection is a tester decision, not an observation.

Declared assumption · no observation time

Claim limit: Selecting a tool demonstrates nothing by itself.

Playback time is not an observation time · pause, seek and replay cause no external action.