Contents

Intrusion detection (IDS) and the Vehicle SOC

How vehicles detect attacks in the field — sensors in ECUs and gateways that report security events to a Vehicle Security Operations Center in the backend.

Why it exists

No protection is perfect. R155 requires manufacturers to monitor their fleets and respond to attacks — which means the vehicle must notice suspicious behaviour and report it.

What it is

  • Sensors in ECUs: failed SecOC verifications, unexpected diagnostic requests, abnormal message timing, integrity failures.
  • Aggregation in a central IDS manager that filters and qualifies events.
  • Reporting via telematics to the VSOC, where analysts correlate events across the fleet.
  • Response: investigations, updates, and in some designs local reactions (IDPS).

Best practices

  • Start with high-quality, low-noise events rather than heavy anomaly detection.
  • Define the VSOC process together with engineering, so findings become fixes.

Common pitfalls

  • Too many false positives, which overwhelm the VSOC and the telematics budget.

What it means for your discipline

  • Cybersecurity Core

    Defines detection rules, event formats, the VSOC process and incident response.

  • Base software Partial

    AUTOSAR's IdsM collects security events from BSW modules (SecOC failures, diagnostic attempts).

  • Networks & communication Partial

    Network IDS sensors in gateways analyse message timing, IDs and content.

  • HPC & application software Partial

    Host IDS on HPCs monitors processes, files and system calls.

  • Diagnostics & lifecycle Partial

    Event upload uses telematics and must respect bandwidth and privacy.

No direct stake: E/E architecture · Functional safety · Hardware & silicon · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Security services — Collects host and network intrusion events, filters them and reports qualified alerts to the backend VSOC.
MCU-based ECU · AUTOSAR Classic
  • Communication — Supplies SecOC verification failures and suspicious communication events to intrusion detection.
  • Diagnostics — Supplies suspicious diagnostic access attempts and authentication failures to intrusion detection.