How to check for attack data on network logs without SIMs

How to check for attack data on network logs without SIMs

What are some best practices that can help me regularly check for attack data in network logs without using a SIMs product and without spending an eternity staring at log data?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Network logs are a treasure trove of security data. It's true that security information and event management (SIM or SIEM) systems provide an easy and effective way to analyze logs, but they also come with a price tag. Fortunately, there are ways you can detect network attacks without purchasing a SIM. Here are some examples:

  • Use an intrusion detection system. IDSes provide the most reliable, time-tested way to search for signs of intrusion on an enterprise network. If the organization doesn't have the budget to purchase a commercial IDS, consider using a free product like Snort.
  • Mine network logs. As you point out, it's impossible to spend an eternity staring at log data. You'll go cross-eyed before you make any sense of it. However, scripts can be written to do the heavy lifting. This approach will require knowledge of a programming language as well as a good idea of what types of events are of interest to you. For example, you might write a Perl script that searches the network logs for signs of an unauthorized IP address appearing on a restricted network.
  • Watch for anomalies. You can also use software (home-brewed or commercial) that learns the patterns of normal behavior on your network and alerts you to deviations. For an example of this approach, read my paper Authentication Anomaly Detection: A Case Study on a Virtual Private Network.

If your budget can swing it, I'd strongly recommend the purchase of a commercial SIM product, as it will save hours of work, but it is indeed possible to cobble together a similar solution with tools such as those described above.

For more information:

This was first published in March 2009