Join our Newsletter — 33% off our NHI Course
Home› Guides› Automotive Ethernet and SOME/IP Security Guide: Securing Zonal…
Guide OT & IoT Security

Automotive Ethernet and SOME/IP Security Guide: Securing Zonal Networks with MACsec and SecOC

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Zonal vehicle architectures move safety and comfort functions onto a switched Ethernet backbone, and the service-oriented SOME/IP protocol that runs on it was not designed to authenticate anyone. A compromised infotainment unit, telematics module or diagnostic tester on the same network can offer fake services, subscribe to sensitive events or flood the switch unless the architecture adds its own protections. This guide explains how automotive Ethernet and SOME/IP work, where they are exposed, and how to combine VLAN and switch policy, MACsec (IEEE 802.1AE and the OPEN Alliance automotive profile), SecOC and TLS or IPsec on secured ports, and intrusion detection reporting into a defensible design. It goes beyond CAN-focused material in the CAN Bus and AUTOSAR SecOC Guide and the Automotive Cybersecurity Guide, and is for E/E architects, ECU and switch developers and vehicle security testers.

Key takeaways

  • SOME/IP has no built-in authentication. Message IDs, client IDs and service discovery offers are plain fields, so protection has to come from the network layer (MACsec, IPsec), the transport (TLS, DTLS) or the message (SecOC).
  • Service discovery is the soft spot. SOME/IP-SD runs over UDP multicast; an unprotected node can offer a service it should not provide or subscribe to events it should not see.
  • Zonal designs make the switch a security control. VLANs, per-port allow-lists, rate limits and filtering in zonal controllers and central switches decide which ECUs can talk at all.
  • MACsec now has an automotive profile. The OPEN Alliance Automotive MACsec Specification v1.0 (May 2025) profiles IEEE 802.1AE-2018 for switched automotive Ethernet, including 10BASE-T1S in point-to-point modes.
  • Detection must be designed in. AUTOSAR's IDS protocol carries qualified security events from ECUs to the vehicle SOC; switches and gateways are the best sensors.

How automotive Ethernet and zonal architectures work

Older vehicles grouped ECUs by domain on separate CAN, LIN and FlexRay buses joined by a central gateway. Zonal architectures instead place zone controllers in physical areas of the vehicle, connected over an Ethernet backbone to a small number of high-performance central computers. Local sensors and actuators connect to the nearest zone controller, which may still use CAN or 10BASE-T1S Ethernet at the edge.

ElementTypical technologySecurity relevance
Backbone linksSingle-pair automotive Ethernet PHYs such as 100BASE-T1 and 1000BASE-T1, and multi-gigabit links to central computersHigh bandwidth carries many functions; a compromised node can reach many others unless switching policy separates them
Edge links10BASE-T1S multidrop or point-to-point, CAN and LIN behind zone controllersShared media and legacy buses still need message authentication
Switches in zone controllers and central unitsManaged automotive Ethernet switches with VLAN, filtering and time-sensitive networking featuresPrimary enforcement point for segmentation, rate limits and MACsec
MiddlewareSOME/IP and SOME/IP-SD for service-oriented communication; DDS in some designsDefines who may offer, call and subscribe to services
External interfacesTelematics, infotainment, diagnostics over IP (DoIP), charging and V2XEntry points that must be filtered before traffic reaches the backbone

How SOME/IP and SOME/IP-SD work

The AUTOSAR SOME/IP protocol specification defines a header with a Message ID (16-bit Service ID plus 16-bit Method ID), a Length, a Request ID (16-bit Client ID plus 16-bit Session ID), Protocol Version, Interface Version, Message Type and Return Code. Message types include REQUEST, REQUEST_NO_RETURN, NOTIFICATION, RESPONSE and ERROR, with transport protocol variants for segmented messages. Over UDP, payloads are limited to 1,400 bytes and larger messages use SOME/IP-TP segmentation; over TCP, the client opens one connection per service instance. Where AUTOSAR E2E protection is used, its header sits after the Return Code, but E2E protects against faults, not attackers.

SOME/IP-SD carries service discovery over UDP, using port 30490 in the current AUTOSAR configuration and multicast to reach all nodes. Its main entries are FindService, OfferService (StopOfferService when the TTL is 0), SubscribeEventgroup and SubscribeEventgroupAck or Nack. A TTL of 0xFFFFFF keeps an entry valid until the next reboot. The SD specification also defines secured ports covering IPsec, MACsec and (D)TLS, and allows a subscription to be rejected when the required security association is not yet established.

What can go wrong

  • Service impersonation: a node offers a service ID it does not own, or races the real provider, and receives calls or feeds false data.
  • Unauthorised subscription: a node subscribes to event groups carrying location, camera or vehicle state data.
  • Spoofed requests: a node sends REQUEST messages to methods such as door, lighting or powertrain functions using a forged client ID.
  • Discovery and flooding: floods of SD offers, subscribes or TCP connections consume switch and ECU resources.
  • Long-lived state: entries with very long TTLs keep a forged offer or subscription alive.

The same trust problem appears on CAN, where thieves have injected messages that impersonate the smart key receiver; see the Digital Car Key and Keyless Entry Security Guide.

Security controls by layer

LayerControlWhat it protectsLimits
Switch and networkVLANs per function or safety level, per-port MAC and VLAN allow-lists, ingress rate limits, multicast filteringWho can reach whom; containment of a compromised nodeNo cryptographic proof of origin; a node with an allowed port is trusted
Link (Layer 2)MACsec (IEEE 802.1AE) with the OPEN Alliance automotive profileFrame integrity, data origin authenticity and optional confidentiality on each hopHop by hop: frames are in clear inside each switch; key management needed per link
Network or transportIPsec or TLS and DTLS on SOME/IP secured portsEnd-to-end protection between ECUs across switches and routersCPU and latency cost; certificate or key lifecycle in every ECU
MessageAUTOSAR SecOC on SOME/IP PDUsAuthenticity and freshness of specific signals end to end, including across gateways to CANNo confidentiality; freshness and key management must be designed
ApplicationAccess control on service offers and calls in the middleware and central computersWhich client may call which methodOnly as strong as the identity underneath it

MACsec in vehicles

IEEE 802.1AE-2018 provides connectionless confidentiality, frame integrity and data origin authenticity, with GCM-AES-128 as the mandatory default cipher suite, GCM-AES-256 as an option and extended packet numbering (XPN) for very high frame counts. Key agreement is defined in IEEE 802.1X. The OPEN Alliance Automotive MACsec Specification v1.0, published on 16 May 2025, profiles 802.1AE-2018 for switched automotive Ethernet including 10BASE-T1S in half and full duplex, but not yet shared-medium mode, and covers point-to-point MACsec only. It allows the Secure Channel Identifier to be omitted from the SecTAG to save 8 bytes per frame, supports integrity-only and full protection with confidentiality offset 0, requires per-port secure channels and statistics counters, and requires at least eight forwarding rules for frames that bypass MACsec. Review every bypass rule: each is a path for unauthenticated frames.

Choosing between MACsec, IPsec or TLS, and SecOC

  • MACsec: choose it to stop rogue devices on backbone links, such as a tap on a harness or a replaced ECU, with hardware offload in PHYs or switches. It does not protect against a compromised ECU that legitimately holds the link key.
  • IPsec or TLS on secured ports: choose it when two ECUs exchange sensitive data across several switches and you need end-to-end confidentiality, for example between a telematics unit and a central computer.
  • SecOC: choose it for safety-relevant signals that must be verified at the receiving function even after crossing gateways to CAN, and for low-overhead authentication of short messages.
  • Combine them: most production designs use switching policy everywhere, MACsec on backbone links, SecOC on critical signals and TLS for high-value data paths.

Protecting external entry points to the backbone

Most realistic attacks on in-vehicle Ethernet start from a component with an external interface, then pivot inward. Design the entry points so that a compromise stays contained.

  • Telematics and infotainment: place them in their own segments behind a filtering zone controller or central gateway, and allow only the specific SOME/IP services they need, never the whole backbone.
  • Diagnostics over IP: DoIP testers connect through a defined activation line or port. Require authenticated diagnostic sessions, for example certificate-based authentication in UDS where ECUs support it, and restrict which diagnostic services are reachable while the vehicle is driving.
  • Charging and V2X interfaces: treat them as untrusted networks with strict protocol filtering at their own controllers.
  • Physical access: exposed harness connectors near the vehicle edge are as real a risk on Ethernet as on CAN; MACsec on those links stops a rogue device from joining.
  • Aftermarket devices: fleet trackers and dongles should connect only to a dedicated, filtered port with no access to safety functions.

Where identity fits

Each ECU and central computer is a machine identity, and the keys for MACsec, SecOC and TLS are its credentials. A secure design needs per-ECU keys or certificates provisioned at the end of line, stored in an HSM or secure element, and replaceable when an ECU is swapped in service. Diagnostic testers and back-end tools that reach the vehicle network over DoIP or remote diagnostics also need strong, individually attributable credentials, because they can often reconfigure the very switches and gateways that enforce policy. See the Device and IoT Identity Guide and the HSM Deployment and Operations Guide.

Implementation approach

  1. Model services and flows: list every SOME/IP service, method and event group with its provider, permitted clients, safety rating and data sensitivity. This becomes the source for switch rules, SD filtering and SecOC selection, and feeds the ISO/SAE 21434 TARA. See the ISO/SAE 21434 Automotive Cybersecurity Engineering Guide.
  2. Segment the backbone: assign VLANs by function and criticality, keep infotainment and telematics in their own segments, and allow only modelled flows through zone controllers and central switches.
  3. Filter service discovery: configure switches and SD implementations so only the expected provider port can send OfferService for each service ID, and only permitted clients can subscribe. Use bounded TTLs rather than "until reboot" where the design allows.
  4. Add cryptographic protection: enable MACsec on backbone links, SecOC on safety-relevant signals and TLS or IPsec on secured ports for sensitive data. Start in a monitoring mode where the stack supports it, so verification failures are logged before frames are dropped.
  5. Provision keys: generate per-ECU keys at end of line, record them in the back-end key management system, and define the service process for ECU replacement and key renewal.
  6. Test: on a bench network and test vehicles, run service impersonation, unauthorised subscription, flooding and bypass-rule tests in a controlled environment, and measure latency impact on time-critical flows.
  7. Roll out and roll back: release by vehicle line, with an over-the-air path to relax a rule or return to monitoring mode if a verification failure affects a function in the field. See the Uptane and Vehicle OTA Security Guide.

Decision guidance

  • Carry-over platforms with limited compute: prioritise switch segmentation and SD filtering, and SecOC on a small set of critical signals, before full MACsec.
  • New zonal platforms: specify MACsec-capable PHYs or switches and HSMs in every zone controller from the start, because adding them later means new hardware.
  • Commercial vehicles and fleets: external telematics and aftermarket devices are common, so filter the telematics segment strictly and log all traffic crossing into the backbone. See the Connected Fleet and Telematics Security Guide.

Detection and measurement

The AUTOSAR Intrusion Detection System protocol defines how an IDS Manager (IdsM) in each ECU filters security events from sensors into qualified security events and sends them to an IDS Reporter (IdsR), which can forward them to the vehicle SOC; events can also be stored in a Security Event Memory. On Ethernet the IDS messages use a separation header, and the specification says IDS and SOME/IP should not share the same port. An optional signature can protect each event up to the SOC.

  • Switch sensors: frames dropped by VLAN or port rules, MAC address changes on a port, rate-limit hits and multicast floods.
  • MACsec counters: authentication failures and frames received on bypass rules, from the statistics counters the OPEN Alliance profile requires.
  • SOME/IP and SD: offers for a service from an unexpected port, subscriptions from clients not in the model, and calls to methods with unknown client IDs.
  • SecOC and TLS: verification and handshake failures per ECU.

See the Vehicle Security Operations Centre Guide.

Metrics:

  1. Percentage of modelled service flows enforced by switch rules and SD filtering.
  2. Percentage of backbone links with MACsec enabled and bypass rules reviewed.
  3. Percentage of safety-relevant signals protected by SecOC.
  4. Qualified security events per vehicle per day reaching the SOC, and the share triaged.
  5. Latency added to time-critical flows by cryptographic protection, against the budget.

Framework mapping

FrameworkReferenceApplies to
NIST SP 800-53 Rev. 5AC-4, SC-7Information flow enforcement and boundary protection in switches and zone controllers
NIST SP 800-53 Rev. 5SC-8, SC-23, IA-3, SC-12MACsec, TLS and SecOC protection, session authenticity, ECU authentication and keys
NIST SP 800-53 Rev. 5SI-4, AU-6IDS sensors and SOC analysis
NIST CSF 2.0PR.IR-01, PR.DS-02, PR.AA-03, DE.CM-01Network protection, data in transit, ECU authentication, monitoring
ISO/SAE 21434 and UN R155TARA and cybersecurity managementIn-vehicle network threats and controls must appear in the TARA and the type approval evidence

Common failure patterns

  • Flat backbone: all ECUs on one VLAN, so a compromised infotainment unit can reach powertrain services.
  • Open service discovery: any port can send OfferService for any service ID, and subscriptions are never checked against a model.
  • Broad MACsec bypass rules: forwarding rules intended for one protocol let unauthenticated frames from many sources through.
  • Shared keys across a vehicle line: one MACsec or SecOC key for every vehicle, so extraction from one car affects all.
  • Diagnostics with switch control: a diagnostic session can reconfigure switches or disable filtering without strong authentication.
  • No sensors in switches: the components that see the most traffic report nothing to the IDS.

Practitioner checklist

  • Maintain a service and flow model for every SOME/IP service, method and event group.
  • Segment the backbone with VLANs and per-port allow-lists in every zone controller and central switch.
  • Filter SOME/IP-SD so only expected providers can offer and only permitted clients can subscribe.
  • Enable MACsec on backbone links and review every bypass forwarding rule.
  • Apply SecOC to safety-relevant signals and TLS or IPsec to sensitive data paths.
  • Provision per-ECU keys at end of line and define the ECU replacement process.
  • Require strong, attributable authentication for diagnostic and switch configuration access.
  • Send switch, MACsec, SD and SecOC events to the vehicle SOC through the AUTOSAR IDS.
  • Test impersonation, unauthorised subscription and flooding before each release.

Standards and references

Related NHI Mgmt Group resources: Automotive Cybersecurity Guide · CAN Bus and AUTOSAR SecOC Guide · Vehicle Security Operations Centre Guide · Connected and Autonomous Vehicle Security Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.