Updated: 22 October 2026
You encrypt data at rest. You encrypt it in the cloud. You encrypt it in transit over the internet. And then, inside your own campus, it travels between switches as plaintext Ethernet, over cables that run through risers, ceilings and links between buildings that anyone with access could tap.
MACsec closes that gap. It encrypts the wire itself. For a CISO building toward encrypt-everywhere and zero trust, it's the piece that's often missing, and it's increasingly a compliance expectation, not just good practice.
Here's what it is and why it now matters.
MACsec is Layer 2 encryption for the wire. Defined in the IEEE 802.1AE standard, it authenticates and encrypts Ethernet frames between two directly connected devices, hop by hop, in the switch hardware at line rate (Cisco MACsec configuration).
The important words are "the wire" and "line rate". MACsec doesn't secure an application or a tunnel; it secures the physical link between two devices, so everything crossing that link is encrypted. And because it runs in the switch ASIC, it does so with essentially no performance penalty.
Key exchange is handled automatically by a protocol called MKA, MACsec Key Agreement, so once configured, the encryption is transparent to users and applications.
Different layers, different jobs. TLS encrypts a specific application's session, like HTTPS. IPsec encrypts traffic between endpoints across networks, like a VPN tunnel. MACsec encrypts the physical link itself, everything on it, between two directly connected devices.
| MACsec | IPsec | TLS | |
|---|---|---|---|
| Layer | 2 (link) | 3 (network) | Application |
| Protects | The physical link, hop by hop | Traffic in a tunnel across networks | One application's session |
| Covers | All traffic on the link | IP traffic in the tunnel | That app's data only |
| Performance | Line-rate in hardware | Some overhead | Per session |
| Typical use | Campus wire, switch-to-switch and switch-to-host | Site-to-site and remote VPN | HTTPS and app encryption |
They're complementary, not competing. MACsec covers the layer the others don't: the local network wire.
Because the wire is a real attack surface, and the rules now expect it covered. Physically tapping a cable, plugging in a rogue device, or exploiting a compromised link between buildings all expose plaintext campus traffic, and an insider with access to a riser doesn't need to break anything clever to listen. Zero trust says don't trust the network, and the wire is part of the network.
There's a compliance driver too. India's DPDP rules require reasonable security safeguards including encryption of data in transit, and campus links, particularly those leaving a secure area or crossing between buildings, are exactly the in-transit paths that expectation covers. MACsec is a direct way to encrypt that traffic at the link layer without re-architecting applications.
So the question a CISO faces is simple: is there any point where your sensitive traffic crosses a cable you don't fully control? If yes, MACsec is how you close it.
On the links that matter most. MACsec runs switch-to-switch, encrypting the uplinks between switches, which is especially valuable on runs between buildings or through shared and less-secure spaces. It also runs switch-to-host, encrypting the link between a switch and an endpoint where that endpoint's traffic is sensitive.
You don't have to encrypt every link on day one. Start where the exposure is highest, inter-building links, connections that leave secure zones, paths carrying regulated data, and extend from there. Because it's hop-by-hop, each link is encrypted and decrypted at each device, so you apply it link by link where it earns its place.
The strength of the cipher, and on Cisco it's tied to your licence. MACsec comes in two strengths, GCM-AES-128 and the stronger GCM-AES-256. On Cisco Catalyst switches, 128-bit MACsec is available with the Network Essentials licence, while 256-bit MACsec requires Network Advantage, and platforms like the Catalyst 9300X support the 256-bit cipher.
So if your security policy mandates 256-bit encryption, that's a licensing decision as much as a configuration one: budget Network Advantage on the switches where you need the stronger cipher. For many campuses, that's the links carrying the most sensitive traffic.
No, and that's what makes it practical to deploy widely. Because MACsec encryption runs in the switch's hardware ASIC, it operates at line rate with essentially zero performance penalty. You're not trading speed for security or adding latency the way a software-based encryption layer might.
That's the quiet strength of MACsec: it encrypts everything on the link, invisibly, without slowing anything down, which removes the usual excuse for leaving the campus wire in plaintext.
Deciding where MACsec belongs, which links, which cipher strength, which licence tier, and configuring it cleanly, is exactly the kind of security-and-networking overlap that benefits from a partner who does both. Proactive Data Systems, a Cisco Preferred Partner with 35 years of experience and more than 1,500 customers, designs campus encryption into the network, MACsec on the links that need it, at the right cipher strength and licence tier, with networking and security under one roof. If encrypting your campus traffic is on your roadmap, ask us where MACsec fits your estate.
We'll get back to you shortly.