Why segment networks
If every ECU sat on one network, a single compromised or faulty node could disturb everything. Segmentation limits the blast radius: infotainment problems stay in infotainment, and only explicitly allowed messages reach the brakes.
Example path: the gateway forwards permitted traffic and drops messages that policy does not allow.
What a gateway does
- Routing — forwards selected messages between segments (CAN to CAN, CAN to Ethernet).
- Translation — packs signals into new PDUs or services, adapts timing.
- Filtering — drops anything not on the allow-list; rate-limits.
- Diagnostic routing — connects the OBD port or DoIP tester to internal ECUs.
- Monitoring — often hosts a network intrusion detection sensor.
How it fits the architecture
In domain architectures, a central gateway ECU connects powertrain, chassis, body and infotainment CAN buses. In zonal architectures, gateway functions are distributed: zone controllers bridge local buses to Ethernet, and central compute or a dedicated switch enforces policies between partitions.
Best practices
- Use allow-lists, never block-lists, for routed messages.
- Keep external interfaces (telematics, infotainment) in their own segment with the strictest filtering.
- Authenticate diagnostic access before routing it inward.
- Preserve end-to-end protection (E2E, SecOC) across routing, or re-create it deliberately.
- Measure worst-case routing latency per message.
Common pitfalls
- “Temporary” routing rules that become permanent attack paths.
- Gateways that cannot be updated, freezing outdated filter rules for the vehicle’s life.