Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Email Email  Print  Share


When To Encrypt At Layer 2 Or Layer 3

Tags: , , , ,

Channel: Security, WAN Security, Data Protection

Layer 2--data link layer--encryption is a high-performance security option that offers some advantages over Layer 3--networking layer--encryption in some scenarios, particularly in unified communications environments that require low-latency, high-volume data transmission. The increased availability and popularity of high-speed carrier Ethernet services provide fast, relatively cheap transmission, particularly for voice, video and other latency sensitive traffic. Enterprises can leverage more traditional Layer 3 IPSec encryption utilizing high-speed switching technology and fast pipes. Or, they can look at Layer 2 encryption technology, which is faster and simple to manage, for appropriate situations.

"If you are looking to aggregate a whole bunch of traffic across a metro Ethernet network on a very high speed link, that's where Layer 2 really shines," said Scott Fanning, senior engineering manager for IOS security at Cisco Systems. "If you are looking at IPSec, you're looking at a much more granular policy, per device or per user policy. You pick the use case appropriately--they're complementary, certainly not competing technologies."

Because it operates below the network layer, Layer 2 encryption is protocol agnostic and is very attractive for high-speed data transmission between data centers. It simply "encrypts everything" and sharply reduces the overhead required by IPSec by as much as 40 percent of available bandwidth. "We encrypt everything that goes across out links; it's just easier to say, if it goes out of our premise, it's encrypted," said the network manager for a regional health care provider, who encrypts traffic largely to meet HIPAA and Medicare requirements.

However, as the provider moved up to gigabit traffic transmission, traffic increased dramatically as users took advantage of the increased capability. VoIP, in particular, has grown from one percent to 10 percent of bandwidth use, but accounts for a quarter of the packet total, placing a heavy burden on processing. "We saw CPU utilization on our routers that were doing encryption jump up dramatically," he said of the VoIP demands. He implemented Layer 2 encryption using SafeNet encryptors, which addressed the performance and latency issues and offloaded encryption from his routers. The company uses Layer 3 encryption for lower bandwidth environments, as well as data transmission to other companies that may not be in a position to support Layer 2.

Layer 2 encryption is a "hop-by-hop" technology, rather than an end-to-end approach used by IPSec. This can be a limiting factor, but also allows organizations that want to inspect traffic to look at network telemetry information provided by Netflow, for example, between points, because the traffic is in the clear within the device.  The encryption devices on the end of each "hop" must not only support Layer 2 but must be directly connected or appear to be directly connected. For example, a Layer 2 transmission could take place across an MPLS network, which would make the intervening network transparent to the encryption devices.


Page:  1 | 2 |3 |Next Page »

Related Reading


More wan-security Insights



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

WAN Security Reports

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers