Commentary

Mike Fratto
Network Computing  

2008 NAC Survey Results Webcast

I will be giving an hour-long Webcast Wednesday, July 23, 2008, at 11 a.m. PT / 2 p.m. ET, on InformationWeek's 2008 NAC Survey. We asked information professionals about their plans for NAC; why they were embarking on a NAC project; what they expected to achieve; and what their concerns were. We compared these results to past surveys to see what, if anything, has changed.
I will be giving an hour-long Webcast Wednesday, July 23, 2008, at 11 a.m. PT / 2 p.m. ET, on InformationWeek's 2008 NAC Survey. We asked information professionals about their plans for NAC; why they were embarking on a NAC project; what they expected to achieve; and what their concerns were. We compared these results to past surveys to see what, if anything, has changed.Not surprisingly, the glow and excitement that surrounded network access control (NAC) in its formative years have largely dissipated. Early adopters, usually those who had to implement NAC to meet internal or external requirements for control and reporting, have deployed the technology and taken their knocks. Many of them shared their stories via our third annual InformationWeek NAC survey. In a nutshell, we found that adoption took these cutting-edge companies longer than expected, and what they're getting out of NAC is slightly different from what they had planned.

In this Web cast, I present the results from InformationWeek's 3rd annual NAC survey and discusses the implications. You can register on the registration page.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


Related Reading




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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links