ESS Overview - Ethernet Technology Summit

Design Options for a Secure Ethernet Stack
Ethernet Technology Summit
Ethernet Security
Session A-202
April 4, 2013
Steve Singer
Director of Systems Engineering
ssinger@insidesecure.com
617-823-8553

INSIDE Secure Corporate Background
A world leader securing
millions of devices and
identities from the chip
to the cloud
Innovative company with
essential IP portfolio
(>500 patents) and strong
R&D focus
$151M revenue 2011
94% growth from 2010
IPO February 2012
Global organization of
400+ employees with
U.S & European
development centers
INSIDE SECURE (INSD.PA)
Acquired Embedded Security Division
Assets from AuthenTec/Apple Corporation
2

Established Leadership in Multiple Categories
Mobile NFC Digital Rights Management Content Protection
People Id & Access Control Secure Communications Semiconductor IP
Machine Identification
Embedded Security Solutions Focus Areas
Anti- Counterfeiting
Secure Payments
FAKE
3

Embedded Security Solutions Portfolio
(Source Code Products)
Software Applications & Toolkits
Semicoductor IP
VPN
Client
Mobile Security Clients
DRM
Client
Embedded Security Software Stacks
QuickSec IPSec
QuickSec MACSec
Matrix SSL/TLS/DTLS
DAR
Client
SafeXcel IP
(Hardware)
• Cryptographic
building blocks
• Security Protocol
Engines
• Platform Security
Trusted Execution
Environment
• Verilog IP
Security
Packet
Engines
Secure
Platform
Module
Cipher and Hash Cores
Public Key Accelerators
True Random Number Generators
Driver Development Kits
Content
Protection
Hardware
DRM Server/Client
FIPS Crypto Libraries
HDCP/DTCP-IP
IPSEC - MACSEC - SSL - TLS - DTLS – SRTP - FCSP - AES -
3DES - ARC4 - MD5 - SHA - C2 - SNOW - KASUMI -
CAMELLIA - ZUC - HDCP - DTCP-IP - DVB/CSA - RSA - ECC -
DSA - ECDSA - DH – TRNG - PKA
Security Stack & Client Software
for OEMs
Security IP for ASIC and FPGA Developers
4

Security Protocols to Protect Ethernet Networks
Today’s Focus MACsec IPsec SSL/TLS/DTLS
Description
• Layer 2 security
• Hop-by-hop
• Peer-to-peer protocol
• Layer 3 ”network layer”
security
• End-to-End ”tunnels”
• Peer-to-peer Protocol
• ”Secure Sockets” ie
application layer
encryption;
• Client-server model
Deployment
Complexity
• Relatively simple to
implement
• Phased deployment
possible
• Key management using
MKA via 802.1X-2010
• Complex protocol suite,
many options
• Key management using
IKE protocol and PKI for
authentication
• Interoperability
challenges with IKEv1
resolved in IKEv2
• Security built into the
application
• Phased deployment
difficult
• Client initiated
• Uses TCP connection
oriented protocol
Performance
• Designed for very high
speeds (> 40+ Gbps)
• Assumes HW crypto in
most cases
• Ranges from low to high
(Embedded Clients to
Telco Switches)
• HW crypto use prevalent
• Assumes medium to
low performance
• HW assist possible at
server end for PKI
Product
Examples
Ethernet Switch, Endpoints Routers, Edge Devices Application Servers, Client
Apps

What is MACsec
• IEEE Standard for protecting a LAN/MAN at layer 2
• 802.1AE – MACsec: Data plane protocol
• 802.1X-2010 (formerly 802.1X-REV) – Port Based Network
Access Control and MACsec key establishment
• Data security at layer 2 (the OSI “data link layer”) :
• Peer Authentication
• Integrity
• Confidentiality (ie. frame encryption)
• Secure session establishment
• A hop-to-hop and peer-to-peer security model
• Point to Point
• Point to Multipoint
• Unified Wireless/Wired LAN authentication with
RADIUS/EAP-TLS
• Only authenticated devices allowed on LAN
• Prevents unauthorized modification of network infrastructure
(installation of unauthorized network devices (eg. routers,
switches etc))

Use Case: MACsec in Router/Switch ASIC
MACsec control
plane (802.1X-REV)
uplink
XAUI, or PCIe,
hypertransport,
...
MACsec data
plane (802.1ae)
MAC
PHY
Control Processor
Switch ASIC
MAC
PHY
MACsec data
plane (802.1ae)
XAUI
GMII, RGMII
PHY
PHY
10G PHY module
(XENPAK, SFP+)
1Gbp PHY module
(SFP)
• The MAC is the ‘natural’ place for MACsec to live in the appliance.
• Requires HW update of switch ASICs, where most often the MAC is implemented
7

Use Case: MACsec as a Discrete Component
MACsec control
plane (802.1X-REV)
uplink
XAUI, or PCIe,
hypertransport,
...
MACsec data
plane (802.1ae)
MAC
MACsec
PHY
Control Processor
Switch ASIC
MAC
MACsec
PHY
MACsec data
plane (802.1ae)
XAUI
GMII, RGMII
MACsec
MACsec
PHY
PHY
10G PHY module
(XENPAK, SFP+)
1Gbp PHY module
(SFP)
• Respin of switch ASICs to include MACsec is very costly
• Migration path: implementing MACsec outside the switch ASIC
8

Use Case: MACsec Integrated in PHY Device
MACsec control
plane (802.1X-REV)
uplink
XAUI, or PCIe,
hypertransport,
...
MACsec data
plane (802.1ae)
MAC
MAC
MACsec
MAC
PHY
Control Processor
Switch ASIC
MAC
MAC
MACsec
MAC
PHY
MACsec data
plane (802.1ae)
XAUI
GMII, RGMII
MAC
MAC
MACsec
MACsec
MAC
MAC
PHY
PHY
10G PHY module
(XENPAK, SFP+)
1Gbp PHY module
(SFP)
• Ideal solution is to move the MACsec function into the PHY device
• PHY devices will always be a separate component in large # of port designs
• Long term: MACsec will move back into the Switch ASIC
9

Protection of Data in Transit
• Different Protocols • Over different Media, at different speeds
• IPsec
• 1, 10, 40, 100G Ethernet, IP, TCP/IP
• MACsec
• 802.11 Wireless LAN
• sRTP
• SSL/TLS/DTLS
• 2G/3G/4G Wireless WAN
• WPA
• 3GPP & LTE data protection
• ....
• Bottom line:
• Lots of protocols, Lots of different protocol stacks, Lots of data
• To be handled by a processor
• Intended to spend time on applications, and not
on the protection of the data it sends/receives
• Will cause system bottlenecks
Efficient HW Security Engines w/tight SW integration is paramount!
10

Security Protocol Acceleration Architectures
1. Software Only
2. Hardware Crypto/Hash
3. Look Aside Packet Engine
memory
interface
CPU
memory
interface
CPU
memory
interface
CPU
System Bus
System Bus
System Bus
Ethernet
Interface
Ethernet
Interface
Crypto
Hash
Ethernet
Interface
Crypto
Packet
Engine
memory
interface
CPU
memory
interface
CPU
System Bus
System Bus
Ethernet
Interface
In line
Crypto Engine
With Classifiers
Ethernet
Interface
In line
Crypto Engine
With Classifiers
Ethernet
Interface
Fastpath
Fastpath
4. Bump in the Stack Packet Engine
5. Bump in the Wire Packet Engine
11

INSIDE’s HW Security Engines
IPsec, SSL/TLS, DTLS, MACsec, and Wireless
Leveraging Cryptographic Primitives (AES, SHA,….)
12

EIP-164 In-line HW MACsec & IPsec @ 40 & 100Gbps
• In Line operation with MACsec Classification.
• Multi Mode: i.e. 1*100GE, 2*40GE, 4*10GE, mixed mode streams like
1*40GE & 4*10GE.
• Multi Protocol: MACsec or IPsec based on AES-GCM.
• Multi Port: Support for multiple ports and port types (mixed mode).
• Flexible # of SA supported based on # of ports and # modes.
• Low Latency, ~80 cycles.
• Supported by QuickSec Toolkits
13

QuickSec for MACsec Toolkit v2.0
IEE 802.1X-2010
Functional components:
• Control Plane with MACsec
Key Agreement Logic
• Data Plane with Hardware or
Software based FastPath
• Functionality:
• IEEE 802.1X-2010 (Key Agreement)
• Authentication support for EAP and
pre-shared key authentication
• Policy based decisions on frames
(pass/drop/MACsec)
• A software implementation of the
802.1AE MACsec protocol
• Complete implementation of the MACsec
specifications:
• 802.1AE, 802.1X-2010
14

MACsec Control Plane Protocol Details
The 802.1X-2010 defines:
• MKA: MACsec Key Agreement is used to discover MACsec peers and to
negotiate the keys used by MACsec data plane.
• EAPOL: EAP Over LAN defines the encapsulation for the transport of EAP
over IEEE 802 wired networks. EAPOL is a Layer 2 protocol.
• PACP: The Port Access Control Protocol controls the authentication
procedure. It initiates authentication attempts, retries initial authentication (if
necessary), provides periodic re-authentication, and terminates
authentication on request.
• Network announcements: The network announcement protocol broadcast
over EAPOL what network(s) or network service(s) are available, and for
each network:
• Is access to that network already available, or is authentication or secured connectivity
required
• What authentication and secure connectivity mechanisms are required or available
• What credentials should be presented if EAP is to be used
• What cached CAKs* can be used with a reasonable chance of success
• What level of access (authorization) is or may be provided
* CAK: secure Connectivity Association Key, a secret key possessed by members of a given Connectivity Association.
15

Use Case: Integration of Control Plane Module
with a Switch having MACsec HW Support
MACsec Switch Control Application
MACsec PAE
API
tun1
Network
stack in
kernel
EAP
(TLS, FAST)
RADIUS
Certificate
Manager
EAP
Auth
API
802.1X-2010
Port Access
Entity
(MKA, EAPOL,
PACP,
Announcements)
MACsec LMI
API
MACsec
Data
Plane
HW
API
802.1AE
in HW
Data
Flow
eth1
Ethernet
port
Existing
crypto API
MACsec PAE
crypto API
Existing Crypto Library
•The 802.1X-2010 PAE module (MACsec control plane) is integrated with the existing switch.
•The MACsec LMI API can be reused to provide relevant configurations to the Data Plane.
•The MACsec PAE crypto API is designed to integrate with existing crypto in software or hardware.
16

Use Case: Integration with IP Phone
Data Plane in Ethernet Driver
802.1X-2010
Port Access Entity
(MKA, EAPOL, PACP,
Announcements)
Reuse Softsec module to
implement MACsec
(802.1AE) protocol
processing in software
inside the Ethernet driver.
The crypto API makes it
possible to replace the SW
crypto module by a
hardware crypto module
MACsec LMI API
MACsec Data Plane
Ethernet driver
Network
Stack
eth1
Softsec
API
User Space
Kernel
Link from network stack to
the physical port eth1 is
enabled normally
802.1AE
softsec module
Crypto API
Crypto
17

INSIDE Security IP & Software Solutions
• Award-winning Semiconductor IP provides silicon-proven
security for next-generation ASIC and FPGA designs.
• Complimentary Software Stacks, Middleware, and
Drivers for protocols such as IPsec, MACsec,
SSL/TLS/DTLS, HDCP, DTCP-IP and DRM to enable
complete HW/SW security systems.
• Silicon-proven in devices from Texas Instruments, AMD,
Applied Micro, Tilera, ARM, Samsung, PMC-Sierra, K-
Micro, IBM, and many others in technology down to 28nm.
• Designer-friendly and easy to integrate ANSI C Source
Code Stacks and Verilog RTL Source Code with
excellent HDL test coverage.
• Available in many configurations for tailored solutions
addressing feature, performance, and power.
• World-class support by experienced chip designers.
For more product information:
http://www.insidesecure.com/eng