Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

AUTOSAR IdsM (Intrusion Detection System Manager, R22)

AUTOSAR IdsM Data Flow
  BSW / Application SWC detects anomaly
  └── calls IdsM_ReportSecurityEvent(eventId, contextData)
       │
       ▼
  IdsM (Intrusion Detection System Manager)
  ├── Event filtering: suppression window prevents storm (>100 same events/min → throttle)
  ├── Event aggregation: batch events per trip counter window
  └── Rate limiting: configurable per event ID to avoid flooding VSOC
       │
       ▼
  IdsR (IdsM Reporter)
  └── Forwards to TCU security log buffer (NVM)
       │  Periodically uploaded to VSOC via LTE/5G

  Standard event IDs (examples):
  IDS_EVENT_SECOC_VERIFICATION_FAILED  -- MAC check failed on CAN PDU
  IDS_EVENT_SECURITY_ACCESS_DENIED     -- UDS 0x27 wrong key (NRC 0x35)
  IDS_EVENT_INVALID_PDU_LENGTH         -- CAN PDU with unexpected data length
  IDS_EVENT_UNEXPECTED_MSG_ID          -- CAN ID not in DBC whitelist

CAN-Based IDS Detection Methods

MethodWhat It DetectsImplementation
Frequency-basedCAN message period deviation from DBC spec (e.g., 10 ms expected; >15 ms or <5 ms = anomaly)Gateway ECU monitors actual Δt between received messages per CAN ID; compares against DBC timing
Content-basedSignal values outside physics-based plausible range (speed > 300 km/h, RPM > 8000)Signal range check in gateway SWC; flag anomaly if value outside defined bounds
Sender authenticationSecOC VERIFICATION_FAILED status for safety-critical PDUAUTOSAR SecOC module reports to IdsM via IdsM_ReportSecurityEvent on FAILED verification
DBC whitelistUnexpected CAN ID not in DBC whitelistGateway CAN filter: any ID not in whitelist triggers IDS_EVENT_UNEXPECTED_MSG_ID

Ethernet/IP IDS: DPI and Anomaly Detection

Pythonethernet_ids_rules.py
#!/usr/bin/env python3
# Ethernet IDS: SOME/IP + DoIP inspection rules
# Deployed as passive tap on automotive Ethernet switch span port

import struct

def inspect_uds_over_doip(payload: bytes) -> dict:
    # Signature-based rule: detect UDS DID enumeration (reconnaissance)
    if len(payload) < 4: return {"alert": False}
    service_id = payload[0]
    if service_id != 0x22: return {"alert": False}

    # UDS 0x22 ReadDataByIdentifier: inspect DID
    did = struct.unpack(">H", payload[1:3])[0]
    return {
        "alert":    True,
        "event":    "IDS_EVENT_UDS_DID_ENUM",
        "did":      hex(did),
        "severity": "MEDIUM",
        "note":     "Systematic DID enumeration indicates reconnaissance"
                    if did == 0x0000 else "Normal ReadDataByIdentifier",
    }

def inspect_someip_anomaly(src_ecu_id: int, service_id: int,
                            method_id: int, baseline: dict) -> dict:
    # Anomaly-based: flag SOME/IP call patterns deviating > 3 sigma from baseline
    key = f"{src_ecu_id}:{service_id}:{method_id}"
    if key not in baseline: return {"alert": False}

    mean, stddev = baseline[key]["mean"], baseline[key]["std"]
    # Baseline call rate checked against recent 5-minute window
    return {
        "alert":    False,  # placeholder: would compare recent_rate vs mean+3*std
        "event":    "IDS_EVENT_SOMEIP_ANOMALY",
        "key":      key,
        "severity": "LOW",
    }

IDS Alert Enrichment and Correlation

Enrichment FieldSourcePurpose
ECU IDCAN/Ethernet source addressIdentify which ECU reported the event
Bus IDIdsM configurationIdentify which CAN segment or Ethernet VLAN
GPS-synchronised timestampAUTOSAR StbM via IEEE 802.1ASEnable precise cross-vehicle timing correlation in VSOC
Trip counterIdsM session contextGroup events within a single ignition cycle for forensic replay
Context signalsVehicle speed, ignition state, door status from COMDistinguish attack during parking vs driving; support forensic reconstruction

💡 Multi-Signal Correlation

A single SecOC FAILED alert is often a bus error or key sync issue. A coordinated pattern -- SecOC FAILED on powertrain CAN + simultaneous unexpected Bluetooth connection + OTA update request within the same 30-second window -- is likely a coordinated attack. The VSOC correlation rule that fires on all three together with Severity CRITICAL enables the automated protective response (disable OTA, restrict remote diag) before an analyst even reviews the incident.

Summary

AUTOSAR IdsM provides the standardised on-ECU event reporting infrastructure connecting vehicle-side anomaly detection to VSOC. CAN IDS uses four complementary methods: frequency monitoring, content range checks, SecOC authentication status, and DBC whitelist filtering. Ethernet IDS adds DPI-based signature rules and ML-baseline anomaly detection. The correlation step -- combining IdsM events from multiple sources with vehicle context signals -- transforms individual anomalies into high-confidence attack indicators, reducing false-positive alert fatigue and enabling automated protective response for coordinated attacks.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

  • Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
  • Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
  • Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

  • Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
  • Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
  • Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

  1. Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
  2. Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
  3. Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
  4. Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.

← PreviousVehicle Security Operations Center (VSOC)Next →Incident Response & Forensics