Thursday, June 21, 2007

Who's in charge of the NAC?

Network World

Network Access Control




Network World's Network Access Control Newsletter, 06/21/07

Who's in charge of the NAC?

By Tim Greene

As NAC is considered more seriously by businesses, they have to decide who among their various IT staffers are going to be in charge of it.

Traditionally, the state of the endpoint has been the domain of the desktop team that is charged with making sure these devices are kept in compliance with whatever the company standard desktop configuration is. NAC can change that model.

As risk-mitigation technology, NAC also falls into the sphere of the security staff whose task is to protect both the functionality of the network and sensitive corporate data.

Manage Insider Security Threats

Experts say 75% of security threats come from inside your organization. Watch the latest Network World Editorial Perspectives Webcast today, "Security From the Inside," and learn which technologies and processes best protect your intellectual property and assets inside the perimeter.

Click Here to View

And with the use of network infrastructure as possible enforcement points for NAC, corporate networking groups can also come into play because some NAC schemes call for potentially expensive upgrades.

As with any technology that cuts across fields of expertise (VoIP comes to mind), part of a successful deployment is getting separate and independent groups to cooperate. This calls for high-level commitment and coordination.

Successful NAC deployment requires careful advanced planning that should include:

* A budgeting plan that may extend over more than one fiscal year.

* Defining roles of the various teams involved in the deployment.

* Training and cross-training staff to administer NAC.

* A technology plan that takes into account that NAC is a young and evolving technology that won’t be fully cooked for several years.

* Involve business units because NAC requires a balance between the work a corporation has to get done to earn revenue and the need to protect the network and data.


  What do you think?
Post a comment on this newsletter

TODAY'S MOST-READ STORIES:

1. Linux version of Microsoft browser plug-in
2. California gets Microsoft to change Vista
3. Lawyers show how to side-step immigration law
4. 'Italian job' Web attack hits 10K sites
5. Linux Foundation: Microsoft won't sue
6. The case of the 500-mile e-mail
7. Microsoft flaw opened door to scammers
8. Cisco's Chambers: Telecom entering 'Phase II'
9. Vista over the WAN: good but not great
10. Gartner to IT: Avoid Apple's iPhone

MOST-READ REVIEW:
Open source management-tool alternatives hit the mark


Contact the author:

Tim Greene is a senior editor at Network World, covering network access control, virtual private networking gear, remote access, WAN acceleration and aspects of VoIP technology. You can reach him at tgreene@nww.com.



ARCHIVE

Archive of the Network Access Control Newsletter.


BONUS FEATURE

IT PRODUCT RESEARCH AT YOUR FINGERTIPS

Get detailed information on thousands of products, conduct side-by-side comparisons and read product test and review results with Network World’s IT Buyer’s Guides. Find the best solution faster than ever with over 100 distinct categories across the security, storage, management, wireless, infrastructure and convergence markets. Click here for details.


PRINT SUBSCRIPTIONS AVAILABLE
You've got the technology snapshot of your choice delivered to your inbox each day. Extend your knowledge with a print subscription to the Network World newsweekly, Apply here today.

International subscribers, click here.


SUBSCRIPTION SERVICES

To subscribe or unsubscribe to any Network World newsletter, change your e-mail address or contact us, click here.

This message was sent to: networking.world@gmail.com. Please use this address when modifying your subscription.


Advertising information: Write to Associate Publisher Online Susan Cardoza

Network World, Inc., 118 Turnpike Road, Southborough, MA 01772

Copyright Network World, Inc., 2007

No comments: