Contents
StandardIEEE

IEEE 802.1AE (MACsec)

Media Access Control (MAC) Security

IEEE 802.1AE, known as MACsec, protects Ethernet traffic against tampering and impersonation, with optional encryption to hide its contents.

What it is

IEEE 802.1AE defines Media Access Control Security, usually called MACsec. It protects communication at the Ethernet link layer, below protocols such as IP, TCP, and application services. Its main functions are data integrity, data origin authenticity, and optional confidentiality. Replay protection can reject previously received traffic according to the configured policy.

For a newcomer, think of MACsec as a protected envelope around Ethernet traffic between participating network devices. It authenticates traffic using cryptographic keys; a source MAC address alone is not proof of identity. Encryption hides protected contents, but does not hide every observable detail of a connection.

The standard is available free to read through the IEEE GET program.

Who it applies to

MACsec applies to designers and implementers of Ethernet equipment and networks that choose to use this protection. In a vehicle, that can include ECUs, central computers, gateways, and Ethernet switches. It is a general networking standard, rather than an automotive-specific regulation or a universal vehicle requirement.

A project must identify the actual MACsec peers. Protection may terminate at a switch, leaving traffic accessible inside that device before it is protected again on another connection. The trustworthiness of those termination points therefore matters.

What it covers

The standard specifies the processing and structures needed to protect Ethernet communication, including secure channels, secure associations, protected frame formatting, cryptographic cipher suites, packet numbering, receive validation, and management information.

Mechanism Engineering consequence
Integrity and origin authentication Receivers can detect unauthorized changes and traffic without valid cryptographic authentication.
Optional confidentiality Projects must explicitly select whether protected contents are encrypted.
Packet numbering and replay checks Configuration must account for packet ordering, key changes, and counter exhaustion.
Security tags and integrity checks Additional frame overhead affects frame-size limits and bandwidth planning.

MACsec does not guarantee delivery or prevent an attacker from disrupting a physical connection. It also cannot make a compromised, authorized endpoint trustworthy.

How it fits with other documents

IEEE 802.3 defines Ethernet technologies; IEEE 802.1AE adds security to the MAC service. IEEE 802.1Q supplies the bridging and VLAN context in which many deployments operate.

IEEE 802.1X is the key companion for access control and MACsec Key Agreement, commonly called MKA. MACsec defines protected data handling; the system also needs a way to establish trust, distribute keys, and renew them. Implementing MACsec alone does not complete that lifecycle.

IPsec protects communication at the IP layer, while TLS protects communication above a transport service. Their protection boundaries differ from MACsec’s. An architecture can combine them when link protection and protection between application endpoints serve different needs.

In practice

Start by mapping Ethernet paths and identifying the threats on each path. Specify where protection terminates, whether encryption is required, how keys are established, and what happens when a peer cannot establish protection.

Check endpoint and switch interoperability early. Confirm supported cipher suites, replay settings, frame-size handling, and hardware performance. Include startup, sleep and wake, ECU replacement, and key renewal in integration testing.

Test invalid authentication, replayed frames, peer resets, and loss of key agreement. Verify that failures produce useful diagnostics and that any fallback to unprotected traffic follows an explicit security policy. Measure latency and bandwidth with protection enabled, especially where Ethernet traffic has timing requirements.

What it means for your discipline

  • CybersecurityCore

    Defines the protection policy, trust boundaries, key lifecycle, and response to authentication failures. Must establish which threats MACsec addresses and where additional protection is needed.

  • Networks & communicationCore

    Owns MACsec deployment across Ethernet endpoints and switches. Must configure compatible protection settings and validate forwarding, frame sizes, timing, and recovery.

  • Hardware & siliconPartial

    Checks that Ethernet controllers, switches, or PHYs provide suitable MACsec capabilities. Evaluates throughput, latency, key storage, and the location of the protection boundary.

  • Base softwarePartial

    Integrates drivers and control interfaces for MACsec configuration, key installation, status reporting, and recovery. Coordinates initialization and power transitions with network security policy.

  • E/E architecturePartial

    Decides where protected Ethernet communication begins and ends. Accounts for switches that terminate protection and for traffic requiring protection across a wider path.

  • Diagnostics & lifecyclePartial

    Plans diagnostic access and troubleshooting around encrypted links. Uses security counters and controlled capture points to distinguish protection failures from ordinary connectivity faults.

No direct stake: Functional safety · HPC & application software · Software update & OTA