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.