My first IdM Appliance: IDSentrie
I've been complaining about the desperate state of user account and identity management for some time. To date, the single and reduced sign-on solutions I've had the opportunity to evaluate have proven wholly unsuited for medium businesses of between 500-2500 users. The IdM solutions SMBs can afford are lame, and the products that can actually solve the problem target the large enterprises that are suffering in Dante's identity inferno and willing to pay six figures or more for relief. This is a dreadful situation because many companies might be able to avoid some of the growing pains related to Quad-A (admission control, authentication, authorization, accounting) and control the proliferation of user accounts if they could only find a unified identity management solution that was affordable, deployable, and scalable.
In December, I joined the advisory board of A10 Networks. Before joining, I shared my not-so-favorable opinions of the current state of IdM with some of the company's principals. A10 piqued my curiosity by flatly stating that they had considered all my complaints - well, at least the ones that technology can attempt to solve - in the design objectives for their IDSentrie identity appliance. In fact, they insisted I test drive an IDSentrie 1000 and sent me an appliance shortly after our first board meeting and a box was literally waiting for me when I arrived home.
In its simplest deployment (which also proved to be a useful introduction to the product), IDSentrie proxies authentication requests from access server devices (firewalls, remote access/VPN servers, WLAN access points, web portals, etc.) to 3rd party authentication data stores using common authentication protocols (e.g., RADIUS, EAP) and popular auth methods (passwords, digital certificates, SecurID hardware tokens). Using the IDSentrie web GUI, I began by configuring two firewalls as network access devices. So I could test one communications path at a time, I configured users and groups in a local database at the IDSentrie. When configuring groups, I identified the access server, auth method, and access control elements that comprise the AAA policy I intended to enforce. I then configured the firewalls to forward authentication requests to IDSentrie using the RADIUS protocol. My firewalls had previously been configured with a number of user-based access policies, so I attempted to visit a web site that hosted restricted content This forced me to authenticate to the firewall, which passed my credentials to the IDSentrie using RADIUS. I repeated the process to test the RADIUS exchange with my second firewall.
This wasn't much of a test; after all, I could do this with many RADIUS servers. I next attempted to enable IEEE 802.1X authentication and WPA/AES encryption through a Linksys WAP55AG access point. IDSentrie has a built-in SSL server certificate and supports several EAP types, including EAP-TTLS and PEAP and auth methods (MD5, MSCHAPv2, SIM). I chose PEAPv0/EAP-MSCHAPv2 authentication against a local IDSentrie database; again, while I could do this with other products, I wanted to keep it simple, early.
Configuring the Linksys AP as a network access server, creating a group and policies for 802.1x authentication and enabling the Linksys AP to forward authentication to the IDSentrie took about as long as configuring the Windows XP clients. I fired up a laptop, connected to my preferred wireless network, accepted the IDSentrie certificate (first encounter), and logged on using IDSentrie database credentials.
These are relatively simple scenarios, but I am juggling my IDSentrie play time with my day job(s). Still, I'm impressed at how intuitive and easy IDSentrie's made tasks that are quite a bit more complex. My next step is to introduce an Active Directory and a RADIUS authentication server into the mix. I've gone through the long and harrowing experience of configuring Secure IEEE 802.11 networks using Microsoft Windows, which requires a certificate infrastructure, Active Directory (for accounts, groups,and 802.11 group policy settings); and IAS services, so I hope to compare that experience with IDSentrie. Eventually, I will eliminate the IDSentrie local database from my environment so I can better emulate medium to large organizations where authentication data stores and servers seem to multiply like rabbits.
This is the first in what should prove to be a series of IdM-related posts. Since I disclosed my relationship with A10 Networks at the outset, I won't apologize for any evangelical comments, but I will try to keep them to a minimum:-)
Archived at http://www.securityskeptic.com/arc20060201.htm#BlogID499
by Dave Piscitello