Your network uses ACLs, firewalls, and segmentation policies to control who can access what.
But none of these features protect the data itself while it travels on the physical cable between two switches.That is the problem MACsec solves.
The Layer 2 Encryption Gap
Your Ethernet links carry traffic in cleartext by default.
Any device with physical access to the cable can capture and read every frame that crosses the wire.
Figure 1 – Without MACsec, frames travel in cleartext on the Ethernet link
An attacker who taps the link can passively intercept all traffic.
This includes VLAN-tagged frames, management traffic, routing protocol updates, and user data.You might think that higher-layer encryption like TLS or IPsec solves this. But not all traffic is encrypted at those layers.
Routing protocols (OSPF, EIGRP, BGP), management protocols (SNMP, syslog), and legacy applications often send data without any encryption.Answer the question below
By default, are Ethernet links encrypted or in cleartext?
MACsec at a Glance
MACsec (Media Access Control Security) is the IEEE 802.1AE standard.
It provides Layer 2 point-to-point encryption, data integrity, and origin authentication on Ethernet links.
Figure 2 – With MACsec, every frame is encrypted on the wire
MACsec encrypts every frame at Layer 2 before it leaves your switch port.
The peer switch decrypts it on the other end. If an attacker taps the cable, all they see is encrypted data.MACsec provides three security services:
Confidentiality – the payload is encrypted using AES-GCM
Integrity – an Integrity Check Value (ICV) detects any tampering
Origin authentication – only peers with the correct keys can participate
Unlike IPsec, which operates at Layer 3, MACsec works directly on the Ethernet frame.
This means it protects all traffic on the link, regardless of the upper-layer protocol.Answer the question below
What IEEE standard defines MACsec?
MACsec modifies the standard Ethernet frame and encrypts traffic hop by hop.
Let's look at the frame format, the encryption model, and what it looks like on a real switch.The MACsec Frame
MACsec adds two fields to the standard Ethernet frame:
A 16-byte Security Tag (SecTAG) inserted after the source MAC address, with EtherType 0x88E5
A 16-byte Integrity Check Value (ICV) appended before the FCS

Figure 3 – MACsec frame format with SecTAG and ICV
The source and destination MAC addresses remain in cleartext.
Only the payload (everything between the SecTAG and the ICV) is encrypted.The SecTAG also contains a Packet Number (PN) field used for replay protection.
Each frame gets a unique sequence number, and your switch drops any frame with a duplicate or out-of-order PN.Answer the question below
What is the EtherType value that identifies a MACsec frame?
Answer the question below
A 1518-byte frame (FCS included) crosses the MACsec link: how many bytes long is it there?
MACsec is not end-to-end encryption. It is hop-by-hop encryption.
It secures one link at a time between two MACsec-capable switches.The Encryption Path
In this example, PC1 sends a cleartext frame to SW1.
SW1 receives it, processes it internally, and encrypts it before sending it to SW2 over the MACsec-protected link.
Figure 4 – MACsec encrypts the switch-to-switch link. Traffic is cleartext everywhere else.
SW2 decrypts the frame on ingress, processes it in cleartext, and forwards it to PC2 as a normal Ethernet frame.
Scaling to Multiple Hops
In a larger network with multiple switches in a chain, each MACsec-enabled link has its own independent session with its own SAK (Secure Association Key).
An intermediate switch decrypts on ingress and re-encrypts on egress with a different SAK.This hop-by-hop approach is a key advantage over end-to-end encryption.
Your network devices can still make forwarding and policy decisions on the traffic, while every wire segment between switches remains protected.Answer the question below
Does MACsec use the same SAK on every link in a chain of switches?
Verifying MACsec
Let's see what a working MACsec session looks like on a real switch.
Runshow mka sessionson SW1:SW1# show mka sessions Total MKA Sessions....... 1 Secured Sessions... 1 Pending Sessions... 0 Interface Local-TxSCI Policy-Name Inherited Key-Server Port-ID G0/1 204c.9e85.ede4/0001 MKA-POLICY NO YES 1 Peer-RxSCI MACsec-Peers Status CKN a0b4.39cd.ef12/0001 1 Secured 01000000000000000000000000000000 00000000000000000000000000000000SW1 is the Key Server and the session Status is Secured.
This confirms MACsec encryption is active on G0/1.Now check the same command on SW2:
SW2# show mka sessions Total MKA Sessions....... 1 Secured Sessions... 1 Pending Sessions... 0 Interface Local-TxSCI Policy-Name Inherited Key-Server Port-ID G0/1 a0b4.39cd.ef12/0001 MKA-POLICY NO NO 1 Peer-RxSCI MACsec-Peers Status CKN 204c.9e85.ede4/0001 1 Secured 01000000000000000000000000000000 00000000000000000000000000000000SW2 shows Key-Server: NO because SW1 won the election.
Both sides show Status: Secured and the same CKN, confirming the MACsec link is up and both switches use the same session.Answer the question below
On which switch is the Key-Server field set to YES?