ESS Overview - Ethernet Technology Summit
ESS Overview - Ethernet Technology Summit
ESS Overview - Ethernet Technology Summit
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Design Options for a Secure <strong>Ethernet</strong> Stack<br />
<strong>Ethernet</strong> <strong>Technology</strong> <strong>Summit</strong><br />
<strong>Ethernet</strong> Security<br />
Session A-202<br />
April 4, 2013<br />
Steve Singer<br />
Director of Systems Engineering<br />
ssinger@insidesecure.com<br />
617-823-8553
INSIDE Secure Corporate Background<br />
A world leader securing<br />
millions of devices and<br />
identities from the chip<br />
to the cloud<br />
Innovative company with<br />
essential IP portfolio<br />
(>500 patents) and strong<br />
R&D focus<br />
$151M revenue 2011<br />
94% growth from 2010<br />
IPO February 2012<br />
Global organization of<br />
400+ employees with<br />
U.S & European<br />
development centers<br />
INSIDE SECURE (INSD.PA)<br />
Acquired Embedded Security Division<br />
Assets from AuthenTec/Apple Corporation<br />
2
Established Leadership in Multiple Categories<br />
Mobile NFC Digital Rights Management Content Protection<br />
People Id & Access Control Secure Communications Semiconductor IP<br />
Machine Identification<br />
Embedded Security Solutions Focus Areas<br />
Anti- Counterfeiting<br />
Secure Payments<br />
FAKE<br />
3
Embedded Security Solutions Portfolio<br />
(Source Code Products)<br />
Software Applications & Toolkits<br />
Semicoductor IP<br />
VPN<br />
Client<br />
Mobile Security Clients<br />
DRM<br />
Client<br />
Embedded Security Software Stacks<br />
QuickSec IPSec<br />
QuickSec MACSec<br />
Matrix SSL/TLS/DTLS<br />
DAR<br />
Client<br />
SafeXcel IP<br />
(Hardware)<br />
• Cryptographic<br />
building blocks<br />
• Security Protocol<br />
Engines<br />
• Platform Security<br />
Trusted Execution<br />
Environment<br />
• Verilog IP<br />
Security<br />
Packet<br />
Engines<br />
Secure<br />
Platform<br />
Module<br />
Cipher and Hash Cores<br />
Public Key Accelerators<br />
True Random Number Generators<br />
Driver Development Kits<br />
Content<br />
Protection<br />
Hardware<br />
DRM Server/Client<br />
FIPS Crypto Libraries<br />
HDCP/DTCP-IP<br />
IPSEC - MACSEC - SSL - TLS - DTLS – SRTP - FCSP - AES -<br />
3DES - ARC4 - MD5 - SHA - C2 - SNOW - KASUMI -<br />
CAMELLIA - ZUC - HDCP - DTCP-IP - DVB/CSA - RSA - ECC -<br />
DSA - ECDSA - DH – TRNG - PKA<br />
Security Stack & Client Software<br />
for OEMs<br />
Security IP for ASIC and FPGA Developers<br />
4
Security Protocols to Protect <strong>Ethernet</strong> Networks<br />
Today’s Focus MACsec IPsec SSL/TLS/DTLS<br />
Description<br />
• Layer 2 security<br />
• Hop-by-hop<br />
• Peer-to-peer protocol<br />
• Layer 3 ”network layer”<br />
security<br />
• End-to-End ”tunnels”<br />
• Peer-to-peer Protocol<br />
• ”Secure Sockets” ie<br />
application layer<br />
encryption;<br />
• Client-server model<br />
Deployment<br />
Complexity<br />
• Relatively simple to<br />
implement<br />
• Phased deployment<br />
possible<br />
• Key management using<br />
MKA via 802.1X-2010<br />
• Complex protocol suite,<br />
many options<br />
• Key management using<br />
IKE protocol and PKI for<br />
authentication<br />
• Interoperability<br />
challenges with IKEv1<br />
resolved in IKEv2<br />
• Security built into the<br />
application<br />
• Phased deployment<br />
difficult<br />
• Client initiated<br />
• Uses TCP connection<br />
oriented protocol<br />
Performance<br />
• Designed for very high<br />
speeds (> 40+ Gbps)<br />
• Assumes HW crypto in<br />
most cases<br />
• Ranges from low to high<br />
(Embedded Clients to<br />
Telco Switches)<br />
• HW crypto use prevalent<br />
• Assumes medium to<br />
low performance<br />
• HW assist possible at<br />
server end for PKI<br />
Product<br />
Examples<br />
<strong>Ethernet</strong> Switch, Endpoints Routers, Edge Devices Application Servers, Client<br />
Apps
What is MACsec<br />
• IEEE Standard for protecting a LAN/MAN at layer 2<br />
• 802.1AE – MACsec: Data plane protocol<br />
• 802.1X-2010 (formerly 802.1X-REV) – Port Based Network<br />
Access Control and MACsec key establishment<br />
• Data security at layer 2 (the OSI “data link layer”) :<br />
• Peer Authentication<br />
• Integrity<br />
• Confidentiality (ie. frame encryption)<br />
• Secure session establishment<br />
• A hop-to-hop and peer-to-peer security model<br />
• Point to Point<br />
• Point to Multipoint<br />
• Unified Wireless/Wired LAN authentication with<br />
RADIUS/EAP-TLS<br />
• Only authenticated devices allowed on LAN<br />
• Prevents unauthorized modification of network infrastructure<br />
(installation of unauthorized network devices (eg. routers,<br />
switches etc))
Use Case: MACsec in Router/Switch ASIC<br />
MACsec control<br />
plane (802.1X-REV)<br />
uplink<br />
XAUI, or PCIe,<br />
hypertransport,<br />
...<br />
MACsec data<br />
plane (802.1ae)<br />
MAC<br />
PHY<br />
Control Processor<br />
Switch ASIC<br />
MAC<br />
PHY<br />
MACsec data<br />
plane (802.1ae)<br />
XAUI<br />
GMII, RGMII<br />
PHY<br />
PHY<br />
10G PHY module<br />
(XENPAK, SFP+)<br />
1Gbp PHY module<br />
(SFP)<br />
• The MAC is the ‘natural’ place for MACsec to live in the appliance.<br />
• Requires HW update of switch ASICs, where most often the MAC is implemented<br />
7
Use Case: MACsec as a Discrete Component<br />
MACsec control<br />
plane (802.1X-REV)<br />
uplink<br />
XAUI, or PCIe,<br />
hypertransport,<br />
...<br />
MACsec data<br />
plane (802.1ae)<br />
MAC<br />
MACsec<br />
PHY<br />
Control Processor<br />
Switch ASIC<br />
MAC<br />
MACsec<br />
PHY<br />
MACsec data<br />
plane (802.1ae)<br />
XAUI<br />
GMII, RGMII<br />
MACsec<br />
MACsec<br />
PHY<br />
PHY<br />
10G PHY module<br />
(XENPAK, SFP+)<br />
1Gbp PHY module<br />
(SFP)<br />
• Respin of switch ASICs to include MACsec is very costly<br />
• Migration path: implementing MACsec outside the switch ASIC<br />
8
Use Case: MACsec Integrated in PHY Device<br />
MACsec control<br />
plane (802.1X-REV)<br />
uplink<br />
XAUI, or PCIe,<br />
hypertransport,<br />
...<br />
MACsec data<br />
plane (802.1ae)<br />
MAC<br />
MAC<br />
MACsec<br />
MAC<br />
PHY<br />
Control Processor<br />
Switch ASIC<br />
MAC<br />
MAC<br />
MACsec<br />
MAC<br />
PHY<br />
MACsec data<br />
plane (802.1ae)<br />
XAUI<br />
GMII, RGMII<br />
MAC<br />
MAC<br />
MACsec<br />
MACsec<br />
MAC<br />
MAC<br />
PHY<br />
PHY<br />
10G PHY module<br />
(XENPAK, SFP+)<br />
1Gbp PHY module<br />
(SFP)<br />
• Ideal solution is to move the MACsec function into the PHY device<br />
• PHY devices will always be a separate component in large # of port designs<br />
• Long term: MACsec will move back into the Switch ASIC<br />
9
Protection of Data in Transit<br />
• Different Protocols • Over different Media, at different speeds<br />
• IPsec<br />
• 1, 10, 40, 100G <strong>Ethernet</strong>, IP, TCP/IP<br />
• MACsec<br />
• 802.11 Wireless LAN<br />
• sRTP<br />
• SSL/TLS/DTLS<br />
• 2G/3G/4G Wireless WAN<br />
• WPA<br />
• 3GPP & LTE data protection<br />
• ....<br />
• Bottom line:<br />
• Lots of protocols, Lots of different protocol stacks, Lots of data<br />
• To be handled by a processor<br />
• Intended to spend time on applications, and not<br />
on the protection of the data it sends/receives<br />
• Will cause system bottlenecks<br />
Efficient HW Security Engines w/tight SW integration is paramount!<br />
10
Security Protocol Acceleration Architectures<br />
1. Software Only<br />
2. Hardware Crypto/Hash<br />
3. Look Aside Packet Engine<br />
memory<br />
interface<br />
CPU<br />
memory<br />
interface<br />
CPU<br />
memory<br />
interface<br />
CPU<br />
System Bus<br />
System Bus<br />
System Bus<br />
<strong>Ethernet</strong><br />
Interface<br />
<strong>Ethernet</strong><br />
Interface<br />
Crypto<br />
Hash<br />
<strong>Ethernet</strong><br />
Interface<br />
Crypto<br />
Packet<br />
Engine<br />
memory<br />
interface<br />
CPU<br />
memory<br />
interface<br />
CPU<br />
System Bus<br />
System Bus<br />
<strong>Ethernet</strong><br />
Interface<br />
In line<br />
Crypto Engine<br />
With Classifiers<br />
<strong>Ethernet</strong><br />
Interface<br />
In line<br />
Crypto Engine<br />
With Classifiers<br />
<strong>Ethernet</strong><br />
Interface<br />
Fastpath<br />
Fastpath<br />
4. Bump in the Stack Packet Engine<br />
5. Bump in the Wire Packet Engine<br />
11
INSIDE’s HW Security Engines<br />
IPsec, SSL/TLS, DTLS, MACsec, and Wireless<br />
Leveraging Cryptographic Primitives (AES, SHA,….)<br />
12
EIP-164 In-line HW MACsec & IPsec @ 40 & 100Gbps<br />
• In Line operation with MACsec Classification.<br />
• Multi Mode: i.e. 1*100GE, 2*40GE, 4*10GE, mixed mode streams like<br />
1*40GE & 4*10GE.<br />
• Multi Protocol: MACsec or IPsec based on AES-GCM.<br />
• Multi Port: Support for multiple ports and port types (mixed mode).<br />
• Flexible # of SA supported based on # of ports and # modes.<br />
• Low Latency, ~80 cycles.<br />
• Supported by QuickSec Toolkits<br />
13
QuickSec for MACsec Toolkit v2.0<br />
IEE 802.1X-2010<br />
Functional components:<br />
• Control Plane with MACsec<br />
Key Agreement Logic<br />
• Data Plane with Hardware or<br />
Software based FastPath<br />
• Functionality:<br />
• IEEE 802.1X-2010 (Key Agreement)<br />
• Authentication support for EAP and<br />
pre-shared key authentication<br />
• Policy based decisions on frames<br />
(pass/drop/MACsec)<br />
• A software implementation of the<br />
802.1AE MACsec protocol<br />
• Complete implementation of the MACsec<br />
specifications:<br />
• 802.1AE, 802.1X-2010<br />
14
MACsec Control Plane Protocol Details<br />
The 802.1X-2010 defines:<br />
• MKA: MACsec Key Agreement is used to discover MACsec peers and to<br />
negotiate the keys used by MACsec data plane.<br />
• EAPOL: EAP Over LAN defines the encapsulation for the transport of EAP<br />
over IEEE 802 wired networks. EAPOL is a Layer 2 protocol.<br />
• PACP: The Port Access Control Protocol controls the authentication<br />
procedure. It initiates authentication attempts, retries initial authentication (if<br />
necessary), provides periodic re-authentication, and terminates<br />
authentication on request.<br />
• Network announcements: The network announcement protocol broadcast<br />
over EAPOL what network(s) or network service(s) are available, and for<br />
each network:<br />
• Is access to that network already available, or is authentication or secured connectivity<br />
required<br />
• What authentication and secure connectivity mechanisms are required or available<br />
• What credentials should be presented if EAP is to be used<br />
• What cached CAKs* can be used with a reasonable chance of success<br />
• What level of access (authorization) is or may be provided<br />
* CAK: secure Connectivity Association Key, a secret key possessed by members of a given Connectivity Association.<br />
15
Use Case: Integration of Control Plane Module<br />
with a Switch having MACsec HW Support<br />
MACsec Switch Control Application<br />
MACsec PAE<br />
API<br />
tun1<br />
Network<br />
stack in<br />
kernel<br />
EAP<br />
(TLS, FAST)<br />
RADIUS<br />
Certificate<br />
Manager<br />
EAP<br />
Auth<br />
API<br />
802.1X-2010<br />
Port Access<br />
Entity<br />
(MKA, EAPOL,<br />
PACP,<br />
Announcements)<br />
MACsec LMI<br />
API<br />
MACsec<br />
Data<br />
Plane<br />
HW<br />
API<br />
802.1AE<br />
in HW<br />
Data<br />
Flow<br />
eth1<br />
<strong>Ethernet</strong><br />
port<br />
Existing<br />
crypto API<br />
MACsec PAE<br />
crypto API<br />
Existing Crypto Library<br />
•The 802.1X-2010 PAE module (MACsec control plane) is integrated with the existing switch.<br />
•The MACsec LMI API can be reused to provide relevant configurations to the Data Plane.<br />
•The MACsec PAE crypto API is designed to integrate with existing crypto in software or hardware.<br />
16
Use Case: Integration with IP Phone<br />
Data Plane in <strong>Ethernet</strong> Driver<br />
802.1X-2010<br />
Port Access Entity<br />
(MKA, EAPOL, PACP,<br />
Announcements)<br />
Reuse Softsec module to<br />
implement MACsec<br />
(802.1AE) protocol<br />
processing in software<br />
inside the <strong>Ethernet</strong> driver.<br />
The crypto API makes it<br />
possible to replace the SW<br />
crypto module by a<br />
hardware crypto module<br />
MACsec LMI API<br />
MACsec Data Plane<br />
<strong>Ethernet</strong> driver<br />
Network<br />
Stack<br />
eth1<br />
Softsec<br />
API<br />
User Space<br />
Kernel<br />
Link from network stack to<br />
the physical port eth1 is<br />
enabled normally<br />
802.1AE<br />
softsec module<br />
Crypto API<br />
Crypto<br />
17
INSIDE Security IP & Software Solutions<br />
• Award-winning Semiconductor IP provides silicon-proven<br />
security for next-generation ASIC and FPGA designs.<br />
• Complimentary Software Stacks, Middleware, and<br />
Drivers for protocols such as IPsec, MACsec,<br />
SSL/TLS/DTLS, HDCP, DTCP-IP and DRM to enable<br />
complete HW/SW security systems.<br />
• Silicon-proven in devices from Texas Instruments, AMD,<br />
Applied Micro, Tilera, ARM, Samsung, PMC-Sierra, K-<br />
Micro, IBM, and many others in technology down to 28nm.<br />
• Designer-friendly and easy to integrate ANSI C Source<br />
Code Stacks and Verilog RTL Source Code with<br />
excellent HDL test coverage.<br />
• Available in many configurations for tailored solutions<br />
addressing feature, performance, and power.<br />
• World-class support by experienced chip designers.<br />
For more product information:<br />
http://www.insidesecure.com/eng