| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Security Tools for the Budget Conscious ISP continued
Traffic Analysis and Intrusion Detection Network Traffic Analysis tools include traffic capture utilities, protocol parsers, trend analyzers, and expert analysis engines that recognize badly-formed packets and common attack signatures (e.g., WinNuke, Teardrop, Land). Most ISPs use traffic analyzers for connection trouble-shooting, applying filters to examine packets involving specific sources, destinations, protocols, etc.. But traffic analyzers can also be a valuable part of your security toolkit, feeding intrusion detection systems (below) and helping you to investigate possible attacks. Network Intrusion Detection Systems (NIDS) sit on your network, continuously monitoring passing traffic. NIDS watch for and alert you to policy deviations (e.g., protocols that don't belong on your network), changes in behavior (e.g., sudden surge in off-hours traffic), and defined attacks (e.g., TCP SYN floods, port scans). NIDS can be passive or in-line, with varying levels of event correlation and root cause analysis. Host Intrusion Detection Systems (HIDS) run on your servers and other critical systems, continuously monitoring local program, file, and user activity. A HIDS can often alert you to unusual behavior (e.g., a surge in "su root" events), security policy violations (e.g., log reset), and defined attacks (e.g., using a remote access trojan). Some can also help you maintain system integrity by flagging (or, in some cases, preventing) unexpected changes to critical files. Incident Response and Forensics Although tools will never take the place of careful advance planning, getting familiar with forensics tools can be a useful first step. Forensics refers to a rigorous, formalized investigation of events leading up to an attack for the purpose of identifying, tracking down, and (perhaps) prosecuting the individual(s) responsible. System Forensics tools can help you create a backup of the compromised system and conduct an investigation in a non-intrusive manner. Like a medical autopsy, a system autopsy is designed to identify the culprit and his or her actions in a fashion that preserves evidence and offers foundation for legal action, should that be necessary. Network Forensics tools have a similar business objective, but do their job by continuously capturing and analyzing network traffic to enable later investigation. Some tools simply capture and record all traffic onto very large storage devices so that it is available for analysis after an attack. Other tools continuously perform basic analysis, storing only summary data for detailed analysis after an attack. Although the Electronic Communications Privacy Act prohibits eavesdropping on user traffic without permission, limited monitoring is allowed for the purposes of network operation. Because Network Forensics tools record traffic continuously, ISPs that use these tools should probably include user consent in service contracts. Conclusion
End
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||