How we did it - Network World

Skip Links

DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools

Security

Videos

rssRss Feed
Get instant email notification when white papers, webcasts, executive guides are added to our library.  Stay informed and up-to-date with the latest on IT Technologies with Network World's Resource Alerts.

Additional Resources

RSS

FEATURED WHITEPAPERS

Fill the Gaps in Your Disaster Recovery Plan with Single Object Recovery for Active Directory NetPro

Most companies have a solid disaster recovery plan in place to handle a "complete failure" of its Active Directory, which is really quite rare. What most recovery plans are missing, and the most common scenario, is a means to efficiently restore single directory objects. In this paper, we'll explore what most disaster recovery plans already address, highlight potential weak points, and suggest solutions that help fill those gaps-without requiring you to completely re-do your existing plan.

RSS

FEATURED REPORTS

Executive Guide: Storage Heats Up HP

Get the latest on storage technologies that allow IT professionals to better cope with new IT demands. Learn how storage technologies can help you successfully tackle e-Discover, regulatory compliance, green data center initiatives and the data explosion. Get all the details now.

How we did it

By Joel Snyder and David Newman and Rodney Thayer , Network World , 02/16/2004
  • Social Web 
  • Email 
  • Feedback 
  • Close
IPS in the Wild

Our "In the Wild" evaluation of network intrusion-prevention systems took place on a live, distributed network connecting three of our Test Alliance labs. The goal was to mix elements of a multi-site enterprise network with the inherent randomness of the Internet to see how these new IPS devices would behave.

We started with our "sacrificial lambs," HP ProLiant DL330 servers running unpatched versions of Unix and Windows, and a Cisco router running V11.3 of IOS. These were put into data centers in Los Angeles (LAX) and San Jose (SJC). Each set of sacrificial lambs was protected by an in-line IPS, coexisting with other traffic in the same data centers. Because the IPS devices were installed in-line, we had to test them serially. Starting in September 2003, we evaluated one IPS device per week to see how each behaved while the Internet bucked and gyrated around us.

Because this test took a full five months to complete, several of the vendors have upgraded their products since we tested them.

For management, each vendor was invited to send its management system to our network operations center in Tucson, Ariz. In some cases, vendors sent a full-blown management server. Other times, we got nothing more than a URL with instructions to download a client. In general, we discovered that multi-site and multi-unit management is not as advanced in the IPS world as it is in the intrusion-detection system and firewall business.

In cases where out-of-band management was available, we hooked the management interfaces on the LAX and SJC sensors to an IP Security VPN we built between all three sites. In cases where in-band management was the only possibility, we simply drove these devices over the Internet. Only the management systems were given Internet access (through a NetScreen Technologies firewall) so they could download signature updates and patches as necessary; this turned out to be a problem with some products that expected the IPS device itself would be Internet accessible, a poor architectural choice on the vendor's part.

1 | 2 |  Next >
Comment
Login
Forgot your account info?
Add comment
Anonymous comments subject to moderator approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.
First Name
Last Name
E-mail
Zip Code
IT Buyer's Guides

View All Buyer's Guides