Network World 802.1X Tests

March 25th, 2008

Continuing the 802.1X conversation, Network World recently put out test results for 10G access switches and included a whole section on 802.1X functionality. The article does a pretty good job running through many common 802.1X scenarios and highlights the breadth of functionality most modern switches have. While I’m not sure 10G to the desktop is necessary for all but the most demanding environments, most of the 802.1X functionality described here is available on much lower speed (and more affordable) switches from the same manufacturers. Wired 802.1X has seen quite a surge of interest of late as this article corroborates.

Technorati Tags:

Information Week on 802.1X

March 24th, 2008

With convenient timing, Mike Fratto at Information Week has a short blurb on 802.1X validating some of my previous post. He cites some of the early challenges in 802.1X and sees “broader adoption” coming. It is nice to see the mainstream press starting to talk about default VLAN, guest portals, and some of the other 802.1X elements discussed here for some time now.

Technorati Tags:

Lockdown Ceases Operations

March 24th, 2008

As frequent readers of this blog will no doubt expect, I was completely unsurprised by the shutdown of Lockdown Networks last week. Following the fire-sale of Caymas Systems and the announced restructuring of Vernier Networks as Autonomic Networks, it is natural that more NAC vendors would fall. Coincidentally, I was on the phone with a customer looking to swap out their Lockdown products for something more robust just before I heard the news.

For some analysis, take a look at the blog posts from Jon Oltsik and Eric Ogren, two former-colleagues of one another in the analyst community. The two take very different views with Jon pointing to Lockdown’s retooling of their product as a reason for their failure (but maintaining that the NAC market is healthy) while Eric blames the NAC market in general and the difficulty competing with Cisco and Microsoft.

I think Jon has things more on the money. The classic device-centric NAC market is crowded and with so many players it is awfully hard to reinvent yourself and still stay competitive. Part of me is surprised it has taken so long for another vendor to fail. After all, Cisco announced its intent to purchase Perfigo back in October of 2004. Perfigo’s product became Cisco Clean Access (the giant of the fledgling device NAC market). Lockdown’s technology seems almost identical to Perfigo’s but the market has moved on since then.

When I talk to customers I continue to hear the same themes as I did back in 2005 when I joined Identity Engines:

  • Organizations want to use the network enforcement gear they already have
  • No one wants to deploy a new inline device in their existing network (support and cost issues are cited)
  • User identity is far more important than device health because it allows for far more fine-grained access decisions
  • Guests and contractors is the area of greatest security concern
  • Proprietary clients are a no-no

802.1X is the natural antidote to these desires and now that the deployments are getting larger and the technical objections are being removed through better solutions, I think we’ll be hearing a lot more about 802.1X this year. In fact, tying back to the Lockdown news you can see evidence of this in the market as a whole. Lockdown’s non-Cisco competitors are now talking a lot more about 802.1X and trying to bolt-on more of this type of functionality into their existing non-802.1X offerings. For a sense of this trend, look at the acquisitions in this space since Perfigo. We have Juniper acquiring Funk Software in November of 2005 and Cisco acquiring Meetinghouse Data Communications in July of 2006. The main technology asset of both companies was, you guessed it, 802.1X capabilities.

Technorati Tags: , ,

802.1X Coming to iPhone

March 14th, 2008

As part of their leap into the enterprise market, Apple is adding 802.1X support to the iPhone with their 2.0 firmware update in June. While I expected this to happen eventually, it is interesting that Apple found the feature noteworthy enough to mention in their top enterprise feature requests along with push email and push calendars. If you want proof check out this video and watch Phil Schiller, the SVP of WW Product Marketing at Apple discuss 802.1X at around the 5:30 mark of the video. This is during a press briefing announcing the SDK and the 2.0 feature-set. I’ve always thought 802.1X would be an essential part of networking going forward but to have it discussed as a key enterprise feature for the iPhone is great validation of the 802.1X market as a whole. Apple’s website calls 802.1X “the standard for Wi-Fi network protection.” Soon enough it will be the standard for wired network protection as well.

Technorati Tags: ,

802.1X and OpenSEA in March issue of IEEE Computer Magazine

March 14th, 2008

In the March issue of IEEE’s Computer magazine, there is a four-page story on 802.1X adoption. Entitled “Will IEEE 802.1X Finally Take Off in 2008,” the article is written by Neal Leavitt and quotes me and fellow OpenSEA board member Matthew Gast several times. I can’t find a free copy online so here’s a link to the abstract (with an option to buy the article). Hopefully there will be a free version online somewhere soon.

Technorati Tags: ,

802.1X Deployment at UT Austin

March 14th, 2008

William Green at UT Austin gave a great talk at Educause about their experiences with 802.1X rollout in their wireless network. If you have been watching 802.1X from the sidelines are are interested in a real-world deployment it is worth a look.

Technorati Tags:

iPhone WiFi Update

February 4th, 2008

I just saw this story from iPhone Matters listing a petition with over a thousand names looking for 802.1X support in the iPhone. Somewhat comically, the article refers to 802.1X as 802.11X, 802.1, and 802.1x. Though I’m sure Apple will get it right, I don’t care what they call it, so long as they add it. The iPhone WiFi capability has been far less useful than I was expecting; I generally only use it at home. The time the iPhone takes to check for available networks and let you choose is often longer than the time EDGE would take to complete your request. Also, the Google WiFi network in Mountain View periodically asks for re-authentication via an HTTP captive portal but the iPhone can’t tell when this is requested without me opening Safari. Consider the following scenario:

  1. I am presented with “GoogleWiFi” as an available SSID and select it.
  2. I now have to open Safari and enter my Google ID and password before I get a connection.
  3. From this point on, my iPhone will remember that I use GoogleWiFi but it won’t track when my password is requested.
  4. So if I’m walking downtown and decide to check my email I’ll never know that Google wants my ID again without always loading Safari first. Want to check weather? Same problem. Essentially, the whims of Google prompting me for my password determine when my phone’s data connection works. If I’m sitting at a stoplight and want to check traffic on Google maps, that is a horrible time to be asked to enter an eight digit user ID and a 13-digit password (what can I say, I’m a security guy).
  5. Also, the iPhone makes no attempts to determine the signal strength before joining one of your “preferred” networks. So if you happen to get a whiff of GoogleWiFi while at that stoplight and then drive away while your request is being processed, you may wind up in network limbo for far longer than it would take for EDGE to do the job.

As a result, I turned off the “Ask to Join Networks” feature since it mostly wastes my time. Apple needs to do a couple things to really improve the iPhone WiFi capability:

  1. Add 802.1X Support (Google has an 802.1X option that would largely address my inconsistent authentication concerns). This would also make office connectivity much easier.
  2. Add a selection when joining a WiFi network to “Join once, then forget.” If you join a pay-to-play open wireless network, you don’t want to rejoin this every time as you won’t have connectivity the next time without reentering your credit card info. This makes the Tmobile Starbucks iTunes connectivity almost more nuisance than novelty. If you connect to Tmobile for free to use the iTunes WiFi store, the rest of your data services stop working until you disconnect from that WiFi network, or pay them some money.
  3. Be able to set a minimum signal strength prior to joining any previously known wireless network.
  4. Instead of showing which wireless networks are locked in the “ask to join” screen, instead show which allow network connectivity (i.e. giving out DHCP addresses and not asking for HTTP authentication). I realize this is probably unsolvable as the battery life involved in joining and probing all those wireless networks is probably far too high. Additionally, probing networks is probably a bit unsportsmanlike. I suppose you could implement an “active scan” option on the “ask to join” screen and have a confirmation before you allow it to happen. This would address the battery issue and also perhaps keep Apple out of any direct culpability.

Until then, I’ll deal with EDGE. I actually have been pleasantly surprised by EDGE’s performance. After turning off “ask to join” on WiFi, the phone can get right to making the request, speeding things up considerably.

Technorati Tags: , ,

Schneier’s Wide-Open Wireless Argument

January 16th, 2008

I’ve been watching the back-and-forth concerning Bruce Schneier’s argument for open home wireless networks. See his post for links to essays in support and opposition to Schneier’s points. I found Glenn Fleishman’s post particularly interesting. I don’t want to rehash the arguments for or against that have been put out already but rather wish to point out a couple simple things I didn’t see covered in enough detail (if at all). As a preface, I have an enormous amount of respect for Mr. Schneier and have met him and heard him speak while at Cisco.

First, security is a system. While I have no doubt that there are individuals with the ability to secure their home systems, the vast majority do not. Having WPA encryption raises the bar for attack against a home system (regardless of its security) just like having a firewall limits your exposure to Internet-born attacks. If the controls are easy to use and enable, why take the added risk? As an analogy, In scuba diving it is possible to dive with completely redundant systems thus substantially reducing the risk of underwater failure. I have seen many divers carry elements of such a system with them on a dive. However, the overarching principle in scuba is that you dive with a buddy. This is to ensure that if something unexpected should happen to you, there is another person there to help bail you out. I’ve been diving since the age of 13 and can count on one finger the number of divers I know of (outside the military) that engage in the dangerous act of solo diving.

Second, Schneier seems to think that the risks to him are as follows: someone breaks into his machine or someone does something illegal using his network. There is a significant third risk he doesn’t cover: the increased risk of identity theft / profiling. Watching the Internet use and search habits of a machine is very easy over an open wireless network. Watching that use over a long period of time could be very revealing (and profitable, just ask Google). What I find borderline hilarious is that the blogosphere proponents of open networks are the vary same folks that rightly went a bit bonkers when AOL released the search data of 650,000 users. This data was partially anonymized by removing the screen name of the searcher but as the New York Times and others reported, it is fairly trivial to analyze searches and derive identity. I wrote about how the same techniques might apply to enterprise Identity. What I find funny is while the damage done is at least self-inflicted in the open wireless case, the repercussions could be even more disastrous. With a persistent log of not just your searches but your internet traffic in total over a period of time, it would be very easy to tell an awful lot about you. If you think the bad guys need to be parked out front to do this, you haven’t spent enough time looking at snack-food wireless antennas.

Either your privacy is important or it isn’t. If your argument is you have nothing to hide or that you aren’t important enough for anyone to care about you, that’s your decision. (As an aside that was the government’s position as well when everyone was in arms over the Patriot Act library fiasco.) I myself will put in place simple privacy controls and quietly wait to read the facebook and myspace profiles of presidential candidate’s younger selves in the 2040 elections and beyond. As the Internet Archive has proved, the Internet is forever.

Schneier may, as Glenn assumes, encrypt traffic from his PC to some sort of VPN gateway at his network perimeter. If so, he’s covered against this risk (though I would argue as wifi connected devices proliferate doing the client VPN solution will get tedious). However, I completely agree with Glenn that it is irresponsible to not explicitly state that this is the case. Your average user with a Linksys router has no idea how to do such a thing and most consumer-grade routers do not even support it. Also, since a VPN solution operates above layer 2 it is tedious to enable and prevents easy communication with non-VPN enabled IP devices on the same network. I want my other wifi gadgets to quickly communicate with one another and my home PCs.

Finally, Schneier implies that giving a guest Internet access and having a secure network are mutually exclusive. In the time it takes him to ask “one sugar or two” as he’s preparing his guest’s tea he can easily give them the password to his wireless network. Alternatively, you can run multiple SSIDs giving open access to guest systems and secure access to his personal devices.

I keep things very simple at home: WPA with a strong password that I can easily relay to a guest without writing it down. I should probably change that password now and again but until I see some decent attacks against WPA or make an enemy out of one of my friends I’m not too worried. Of course I do my best to secure my hosts as well but I don’t count on it. When I’m at a hotel or a wireless hotspot I have secure connections for all my email accounts and I avoid doing anything in the clear that I wouldn’t want posted for all to see.

So in summary, can you make an open wireless network secure for your machines? Of course. Is it worth the risk and trouble? Probably not.

Technorati Tags: ,

2007 Conjecture Conclusion

January 16th, 2008

My 2007 predictions are, of course, now open to criticism. I figure I’ll call myself on some things preemptively and then folks can give me some feedback via comments.

  1. “NAC as a term will grow out of favor…” As I said last year, some of these are tough to measure but I think at least a B on this one is appropriate. NAC as a term is growing out of favor and/or morphing in meaning. The definition has shifted away from pure endpoint security controls and more towards identity. So even when the NAC term is used, it means something more today than a year ago. As another data-point, take Cisco’s marketing introduction of TrustSec for example. In their white paper describing the proposed solution the word “posture” appears four times, the word “identity” appears 12 times, and the acryonym “NAC?” Zero.
  2. “One of today’s NAC vendors will go under…” This one is clearly an A, Caymas shut its doors in the first half of last year.
  3. “One of today’s NAC vendors will get acquired by a larger firm…” AV vendor Sophos picked up NAC vendor Endforce in January so this is another clear-cut A grade. I expect more consolidation in 2008.
  4. “An open-source 802.1X supplicant will emerge as a viable alternative to commercial and OS-native supplicants…” OpenSEA was announced, has garnered wide industry support, and is set to find its way into multiple commercial offerings (see my previous posts on this topic). My company was a founding member and we’ve seen lots of participation in the group. JANET(UK) is in the midst of testing the client and has a user-base of 18 million. Though the supplicant is not yet GA, I expect that soon. Given all this an A might be appropriate but I think given where customers are with their production Xsupplicant deployments a B is a safer assessment. As an aside, momentum for Xsupplicant going into 2008 is huge.
  5. “Wired 802.1X turns the corner from rare occurrence to early-adopter chic…” I don’t have any objective data to draw from yet but I think this is happening now. At my company we’re seeing much more interest in wired 802.1X; with wired you now authenticate everywhere and so role-based access control (RBAC) is completely viable. That said, I expected more production deployments by now so a B seems fair.

Technorati Tags: , ,

OpenSEA Adds HP and Aruba, Ships 2.0.0

December 18th, 2007

OpenSEA just announced that HP and Aruba have joined the Alliance. HP even indicated that it might bundle the supplicant in their PCs. There’s some fairly thoughtful analysis by Ric Turner at Computer Busienss Review here. All in all this bodes well for the Alliance and 802.1X in general. I look forward to having more members to announce in 2008!

In related news, the Open1X project just shipped 2.0.0 of the supplicant. It is now in feature freeze mode meaning the only new development to this branch will be bug fixes.

Technorati Tags: ,