|
|
To print: Select File and then Print from your browser's menu
-------------------------------------------------------------- This story was printed from ZDNet Australia. --------------------------------------------------------------
|
Implementing a network intrusion detection system By Michael Mullins CCNA, MCP, TechRepublic May 16, 2002 URL: http://www.zdnet.com.au/insight/soa/Implementing-a-network-intrusion-detection-system/0,139023731,120265285,00.htm
An intrusion detection system (IDS) is a key tool within a network security architecture, yet 60 percent of respondents to a recent NetAdmin poll (Figure A) said they have yet to implement one.
Intrusion detection is vital because it is impossible to keep pace with every current and potential threat and vulnerability in a network.
These threats and vulnerabilities advance at lightening speed, and it takes time for vendors to catch up with patches and updates (and for admins to apply the updates). Therefore, IDSes have become indispensable in helping to manage these threats and vulnerabilities. Once you decide you need an IDS, you must answer these four questions:
How can I use an IDS to benefit my security strategy? An IDS is used to detect intruders to your network. I define intruders as individuals or groups that attempt to access or deny access to data. This would include both internal and external threats. When properly deployed, this tool will identify intruders' methods and provide an intelligent alert to the threat. Some IDS programs will even respond to stop the intrusion. A good IDS should support analysis to find out how the intruder got in and deny any similar exploitation in the future. Figure A
What technologies are available to me? IDS sensors can be categorised into three main groups:
Let's take a closer look at the network-based IDS and break it down further into two subcategories: appliances and software-based IDS. Appliances Appliances are complete and fully loaded systems that require no additional hardware or software to monitor the network segments. An example of an IDS appliance is Cisco IDS (formerly known as NetRanger). This system consists of two major elements:
Software-based IDS A software-based IDS is a solution that you load on a compatible operating system to monitor and respond to network activity. An example of a software IDS is Internet Security Systems' RealSecure. Its system also consists of two major elements:
Cisco's IDS and Internet Security Systems' RealSecure are just two of the many examples of the types of intrusion detection systems that can provide an excellent solution for enterprises. The next step is the actual deployment. Where do I deploy the technology? Depending on your security practices and topology, you'll typically consider four areas for monitoring. These are as follows:
When deciding where to deploy your sensor(s), consider what is most valuable and the attacker's most logical avenue of approach. You also need to make sure that your IDS doesn't degrade the performance of the network segment that you're monitoring. How do I manage the information an IDS will provide? First and foremost, remember to protect yourself. Some people tend to view IDS as a form of wiretap. If you're going to deploy any sensors to monitor your internal network (which is your legal right), verify that you have a published policy explicitly stating "use of the network is consent to monitoring." Develop policies and procedures for events that occur during different hours of your business day. Some of the more robust intrusion detection systems will take actions for you to terminate access and change rules on other security devices to prevent future intrusions. If you have people physically monitoring your network 24 hours a day, you may not want automatic denial of services to potential customers or users based on a false intrusion event. As with any network security device, you will have to evaluate its effectiveness and level of responsibility for your network defense. Summary An IDS is an essential part of a good network security architecture. IDS solutions have their strengths and weaknesses, which must be measured and evaluated before you decide to deploy one on your network. When viewed and implemented as part of a network security fallback mechanism, an IDS is usually well worth the investment.
TechRepublic is the online community and information resource for all IT professionals, from support staff to executives. We offer in-depth technical articles written for IT professionals by IT professionals. In addition to articles on everything from Windows to e-mail to fire walls, we offer IT industry analysis, downloads, management tips, discussion forums, and e-newsletters.
Copyright © 2009 CBS Interactive, a CBS Company. All Rights Reserved. |