The Secret Origin of NAC

Once upon a time, an evil virus struck the land. But the people were prepared, and they stopped the virus before too many became sick… or so they thought. The virus really learned to hide, finding a home among wayward travelers outside the gates of the city. Weeks later these travelers returned home and unknowingly infected the cities. And weeks after that the next wave of travelers came to the cities, and more were infected. And then some scientists said, “Enough! No more will we let our cities become infected by these travelers. Now is the time to protect ourselves from the threats within!” The scientists created a new defense, called NAC, which would check the health of anyone before entering the city, and all was good. But NAC was new, and the first versions didn’t work as well as everyone would have liked. Then, two famous alchemists decided that they should control NAC. Rather than providing it to the people to use, they decided to tell everyone they would provide it. Eventually. And maybe it wouldn’t work quite as expected, but it would be good because it would be big. And then other alchemists decided that the people wanted NAC, but didn’t know what NAC was, so they removed the old labels from their elixirs and put on new NAC labels. And the people were confused. And they waited. (Apologies for starting so many sentences with ‘and’, but you’ll get over it.) I was listening to Alan and Mitchell’s StillSecure podcast the other day and, as usual, the subject of NAC came up. For those of you who don’t know, NAC stands for Network Admission Control or Network Access Control, depending on who you talk with. The technology was originally developed to provide pre-connect health checks when guests or mobile employees plugged into the office network. Alan was ranting on the dilution of the term, and as much as it pains me I have to agree with him. When the SQL Slammer virus hit, most companies were well defended by blocking the port on their firewalls. Those companies then found themselves infected over the following weeks in waves, as mobile employees and contractors started coming back and plugging into the wall, behind the firewall. The concept of NAC was to prevent internal infections from systems physically connecting behind perimeter defenses. A computer would plug in and would then be scanned, or checked using an agent, before it was given an IP address or other network access. If the system wasn’t up to snuff, it could be quarantined off on a network segment outside the firewall (perhaps to download the missing security software), or simply denied access. It’s a great idea, but like all great ideas a combination of big fish and bottom feeders wanted in. “NAC” kept getting expanded and integrated with everything from 802.1x for port-based authentication (only letting a computer get a usable IP address after a user is approved- a pretty good idea) to all sorts of real-time monitoring, quarantining, VLAN weirdness, and kitchen sinks. It’s a market that Cisco and Microsoft decided they want to control, and early on they started making waves without providing much in terms of functional product. It was a way for Cisco to get their endpoint agents onto desktops and to push clients to upgrade their networking hardware, since parts of their NAC don’t work if they aren’t built into the switch. I like NAC, and if I had more than 6 computers on my network it’s the kind of thing I’d look at more closely. But I’d keep myself focused on the basics- protecting my network from malicious guest and mobile systems. I’d want a mix of agent and agentless (for managed and unmanged systems) and keep focused on pre- and post- connection health checks. I wouldn’t wait for the big vendors, knowing that in the long term they’ll own it all anyway, even if they have to buy it. Yes, Cisco has stuff now, but I hear it’s pretty complex to deploy. NAC, like much of network security, will eventually be built into the network fabric. At best, we’ll have a separate security control plane for separation of duties. This is a hell of a long way out and not something that should affect your buying decisions today. I’ll be the first to admit I have a lot more depth in data and application security than netsec, but I’ve watched for years as a great idea (NAC) has been pummeled by the market. I even did an interview on it over at SearchSecurity. It reminds me a lot of Data Loss Prevention/Content Monitoring and Protection (DLP/CMP). A good technology that provides immediate value, which quickly becomes far more confusing than needed as all sorts of people want in on the action. If you want to protect yourself from potentially malicious systems plugging into your network (including remote access) take a look at NAC. If you want all the other bells and whistles you see running around out there you can look at them too, just don’t call them NAC. < p style=”text-align:right;font-size:10px;”>Technorati Tags: NAC, Network Security Share:

Read Post

Speaking at Open Group Forum in SF Tomorrow

If any of you are involved with the Open Group, I’ll be giving a presentation at the Forum tomorrow in San Francisco. The topic ias: The Future of Security: How Disruption and Innovation are Putting the “Information” Back In Information Security Unlike other areas of information technology, security is always battling with external forces. From external attackers to our own business initiatives, disruptions are our way of life. We are in the midst of a major shift as “information-centric” security evolves into the dominant security model, while we still need to maintain our investments of yesterday. The session will discuss these disruptive forces and assess how and where some of the established security technologies (firewalls and e-mail security), and emerging security technologies (data leak prevention, endpoint security, network access control, enterprise rights management, and on and on) will fit into our information-centric security architectures in the future. At least that’s what I think I’m talking about- the description on the conference site doesn’t seem to match. Oh well, I’ll figure it ou when I get there. Note that this is my half of an upcoming joint presentation with Chris Hoff. More details on that later… Share:

Read Post

Totally Transparent Research is the embodiment of how we work at Securosis. It’s our core operating philosophy, our research policy, and a specific process. We initially developed it to help maintain objectivity while producing licensed research, but its benefits extend to all aspects of our business.

Going beyond Open Source Research, and a far cry from the traditional syndicated research model, we think it’s the best way to produce independent, objective, quality research.

Here’s how it works:

  • Content is developed ‘live’ on the blog. Primary research is generally released in pieces, as a series of posts, so we can digest and integrate feedback, making the end results much stronger than traditional “ivory tower” research.
  • Comments are enabled for posts. All comments are kept except for spam, personal insults of a clearly inflammatory nature, and completely off-topic content that distracts from the discussion. We welcome comments critical of the work, even if somewhat insulting to the authors. Really.
  • Anyone can comment, and no registration is required. Vendors or consultants with a relevant product or offering must properly identify themselves. While their comments won’t be deleted, the writer/moderator will “call out”, identify, and possibly ridicule vendors who fail to do so.
  • Vendors considering licensing the content are welcome to provide feedback, but it must be posted in the comments - just like everyone else. There is no back channel influence on the research findings or posts.
    Analysts must reply to comments and defend the research position, or agree to modify the content.
  • At the end of the post series, the analyst compiles the posts into a paper, presentation, or other delivery vehicle. Public comments/input factors into the research, where appropriate.
  • If the research is distributed as a paper, significant commenters/contributors are acknowledged in the opening of the report. If they did not post their real names, handles used for comments are listed. Commenters do not retain any rights to the report, but their contributions will be recognized.
  • All primary research will be released under a Creative Commons license. The current license is Non-Commercial, Attribution. The analyst, at their discretion, may add a Derivative Works or Share Alike condition.
  • Securosis primary research does not discuss specific vendors or specific products/offerings, unless used to provide context, contrast or to make a point (which is very very rare).
    Although quotes from published primary research (and published primary research only) may be used in press releases, said quotes may never mention a specific vendor, even if the vendor is mentioned in the source report. Securosis must approve any quote to appear in any vendor marketing collateral.
  • Final primary research will be posted on the blog with open comments.
  • Research will be updated periodically to reflect market realities, based on the discretion of the primary analyst. Updated research will be dated and given a version number.
    For research that cannot be developed using this model, such as complex principles or models that are unsuited for a series of blog posts, the content will be chunked up and posted at or before release of the paper to solicit public feedback, and provide an open venue for comments and criticisms.
  • In rare cases Securosis may write papers outside of the primary research agenda, but only if the end result can be non-biased and valuable to the user community to supplement industry-wide efforts or advances. A “Radically Transparent Research” process will be followed in developing these papers, where absolutely all materials are public at all stages of development, including communications (email, call notes).
    Only the free primary research released on our site can be licensed. We will not accept licensing fees on research we charge users to access.
  • All licensed research will be clearly labeled with the licensees. No licensed research will be released without indicating the sources of licensing fees. Again, there will be no back channel influence. We’re open and transparent about our revenue sources.

In essence, we develop all of our research out in the open, and not only seek public comments, but keep those comments indefinitely as a record of the research creation process. If you believe we are biased or not doing our homework, you can call us out on it and it will be there in the record. Our philosophy involves cracking open the research process, and using our readers to eliminate bias and enhance the quality of the work.

On the back end, here’s how we handle this approach with licensees:

  • Licensees may propose paper topics. The topic may be accepted if it is consistent with the Securosis research agenda and goals, but only if it can be covered without bias and will be valuable to the end user community.
  • Analysts produce research according to their own research agendas, and may offer licensing under the same objectivity requirements.
  • The potential licensee will be provided an outline of our research positions and the potential research product so they can determine if it is likely to meet their objectives.
  • Once the licensee agrees, development of the primary research content begins, following the Totally Transparent Research process as outlined above. At this point, there is no money exchanged.
  • Upon completion of the paper, the licensee will receive a release candidate to determine whether the final result still meets their needs.
  • If the content does not meet their needs, the licensee is not required to pay, and the research will be released without licensing or with alternate licensees.
  • Licensees may host and reuse the content for the length of the license (typically one year). This includes placing the content behind a registration process, posting on white paper networks, or translation into other languages. The research will always be hosted at Securosis for free without registration.

Here is the language we currently place in our research project agreements:

Content will be created independently of LICENSEE with no obligations for payment. Once content is complete, LICENSEE will have a 3 day review period to determine if the content meets corporate objectives. If the content is unsuitable, LICENSEE will not be obligated for any payment and Securosis is free to distribute the whitepaper without branding or with alternate licensees, and will not complete any associated webcasts for the declining LICENSEE. Content licensing, webcasts and payment are contingent on the content being acceptable to LICENSEE. This maintains objectivity while limiting the risk to LICENSEE. Securosis maintains all rights to the content and to include Securosis branding in addition to any licensee branding.

Even this process itself is open to criticism. If you have questions or comments, you can email us or comment on the blog.