Contents
StandardIEEE

IEEE 802.1X (MKA)

Port-based network access control and MACsec Key Agreement

IEEE 802.1X controls which devices may communicate on an Ethernet network and defines MKA, the protocol that manages keys for MACsec protection.

What it is

IEEE 802.1X defines port-based network access control: a way to decide whether a connected device may exchange ordinary network traffic. Its MACsec Key Agreement protocol, usually called MKA, supports establishing and maintaining the security associations used by MACsec.

The distinction matters: MKA manages the keys and associated coordination; MACsec protects Ethernet frames. Implementing access authentication alone does not automatically enable frame encryption.

Who it applies to

The standard serves implementers and integrators of Ethernet end stations, bridges, and their security software. In a vehicle, these can include ECUs, central computers, zonal controllers, and Ethernet switches.

It is relevant when an OEM or supplier selects port authentication or MKA-managed MACsec for a network connection. It is not an automotive regulation and does not independently require every vehicle Ethernet port to use MACsec. Applicability comes from the system security design, customer requirements, and agreed implementation profile.

Network and cybersecurity engineers should jointly define that profile so independently supplied devices can establish protected communication.

What it covers

The standard separates ordinary communication through a controlled port from authentication and key management communication through an uncontrolled port. These are logical functions; they do not require separate physical connectors.

Element Purpose
Port access control Gates ordinary traffic according to authorization state.
EAP over LAN, or EAPOL Carries authentication and related control exchanges over the local network.
MKA Coordinates authenticated participants and manages MACsec security associations and traffic keys.

A deployment must establish the trust material that MKA uses. Depending on the selected approach, this can involve provisioned shared key material or keys obtained through an authentication exchange. MKA does not itself provide a complete manufacturing or service provisioning system.

How it fits with other documents

IEEE 802.1AE defines MACsec frame protection, including integrity protection and optional confidentiality. IEEE 802.1X supplies access control and MKA coordination around that protection. Read the documents together when specifying dynamically managed MACsec.

EAP and the selected EAP method determine the authentication exchange where that approach is used. Device identity mechanisms, such as those associated with IEEE 802.1AR, can support an identity design but require explicit integration choices.

ISO/SAE 21434 provides the automotive cybersecurity engineering context for selecting and justifying controls. Using IEEE 802.1X contributes a technical mechanism; it does not by itself demonstrate compliance with a vehicle cybersecurity process. TLS and IPsec protect communication at different layers and may coexist with MACsec.

In practice

For a zonal controller connected to a central computer, first define the permitted peers, provisioning method, protection policy, and expected startup sequence. Specify what happens when authorization cannot complete, and which communication remains available for recovery.

Check hardware and software together. A controller with MACsec acceleration still needs compatible key management software and a reliable interface for installing and replacing keys.

Test initial connection, mismatched credentials, peer restart, link interruption, and rekeying while application traffic runs. Measure when protected communication becomes usable and whether failures produce actionable diagnostic information.

Finally, include ECU replacement and service-tool access in the design. A replacement device needs an authorized route to receive its trust material, and obsolete credentials need a defined retirement process.

What it means for your discipline

  • Networks & communicationCore

    Define port authorization, MACsec connectivity, and interoperability requirements for ECUs and switches. Verify startup, rekeying, and recovery behavior across suppliers.

  • CybersecurityCore

    Own authentication policy, trust provisioning, and key lifecycle requirements. Decide how unauthorized peers and failed key agreement affect network access.

  • HPC & application softwarePartial

    Integrate authentication and MKA services with network drivers and platform lifecycle management. Expose useful status and failure information for integration and service.

  • Hardware & siliconPartial

    Check that Ethernet controllers and switches provide the MACsec capabilities and key interfaces required by the chosen design. Account for protected traffic in performance and resource budgets.

  • E/E architecturePartial

    Choose where Ethernet protection terminates and align trust boundaries with the vehicle topology. Include authorization dependencies in startup and availability budgets.

  • Functional safetyPartial

    Assess how delayed authorization or loss of protected communication affects safety-related functions. Coordinate fault reactions and recovery requirements with network and security teams.

  • Diagnostics & lifecyclePartial

    Plan authorized access for service equipment and replacement ECUs. Distinguish authentication and key agreement failures from physical-link faults.

No direct stake: Base software · Software update & OTA