continued from page 1What you need to know about NACOpen-source optionsCertainly, some of the basic roots of NAC can be traced to open-source initiatives, and there are several open-source systems available with varying features. While NAC technology is established in the mainstream commercial market, an open-source option may be ideal depending on needs and the policy that the NAC system will enforce. As a general rule of thumb, commercial systems have more features than their open-source counterparts, and they come with a greater level of support. But that's not always the case. And it doesn't mean that open-source offerings should be neglected. Several open-source systems have sophisticated detection, authorization and quarantine abilities. Why go with open source, then? If there's an open-source offering that has the features you need, and the technical aspects aren't overwhelming, the costs of deployment are substantially less. Furthermore, although traditional vendor support may not be available, in some cases there are third-party companies that provide support, and often the developers themselves are available to answer questions. Bottom lineThe NAC market continues to rapidly expand to meet the goal of providing secure network access. An excellent source for further information on NAC vendors, open-source systems and trends is the Internet2 consortium's Salsa-NetAuth working group Wiki. The question isn't whether or not you need NAC technology on your network, it's what type of system works best in your particular situation. NAC hasn't become a prominent buzzword in networking without reason. With security and privacy concerns of networked resources at an all-time high, NAC is here to stay. How you implement it, however, could pay silent dividends or cost public losses.
|