Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Data Mining for PIX Firewall Logs |
|---|---|
| Date: | Thu, 17 Feb 2005 13:55:28 -0800 |
Matt, My response was not intended to imply that there was no other way to "grep" than with Cygwin. In fact, I clearly state that Cygwin was an *example* of a set of tools. However, I believe that grep is not the only tool one would want to use in this case. I am sure there is an open source grep for Windows. Can you contribute to this thread by providing a link to the tool ? Is this the one to which you refer ? http://www.freedownloadscenter.com/Network_and_Internet/UNIX_Ports_and_Commands/Gnu_Grep_for_Win32.html Thanks, Mike Quoting Matt Bellizzi <matt.bellizzi@nokia.com>:
There is an open source grep variant for windows you know. ext Michael J McCafferty wrote:PIX firewalls log in syslog format to a syslog server. Syslog is a Unix application. Unix (and Unix like OSes like Linux, BSD, etc) machines have other utilities on them that make searching through a text log file like those created by syslog a breeze. But since you are using Kiwi, that tells me you are logging to a Windows machine. It's unfortunate that Windows machines to this day still do not offer a good way to parse through text log files. The right tool is a Unix box. There are some options for you. 1) You can install those tools that one would usually use on a *nix system, which have been ported to Windows. Try Cygwin, for example. There are other ports of the tools like grep, tail, less, more, cat, awk, etc. to Win32. Cygwin may be the most comprehensive. http://www.cygwin.com/ 2) Log to a Unix syslog server and use those tools natively. There are several free OSes that you can stick on that same hardware that you are using Windows on now. Logging doesn't require much horsepower at all. Consider Fedora Core (what used to be RedHat), you can get lots of help from other Linux newbies. http://fedora.redhat.com 3) Use the Kiwi Logfile Viewer. I have not used it. Never seen it. It's on the Kiwi web site. http://www.kiwisyslog.com/ If you want to tip-toe in to option 2 above, you can set your PIX to log to two locations. Grab an old PC, and set up a second log server to try option 2 above. There is no doubt gonna be a learning curve to using the basic Unix tools, like grep, awk, tail and less.... and navigating around the new OS... if you are a total newbie to Unix or Linux. If you are not, then I guess you are not likely to have asked this question in the first place. :o) You will also need to set up your logs to rotate on your new OS. Your log rotation script can compress the logs and you can archive these logs for as long as you have disk space. You can search compressed logs with something like "zcat logfile.gz | grep <pattern>" Good Luck, you have some fun learnin' ahead of you, Mike At 05:08 PM 2/9/2005 -0500, Carey Heck wrote:Hi folks. I love the ability in the Checkpoint firewall logging applet that allows me to load up any former saved log file, and filter according to any criteria I set. Lets use an example: I want to show an auditor what exactly went through my firewall, to/from a specific DMZ host, between the hours of 1 and 3pm GMT, on July 8th, 2003. In checkpoint, if I had correctly configured my ruleset, and archived my log files properly, I could provide this answer within 30 minutes. Fast forward to my current company, which went with a Cisco PIX solution based on the up front cost. I can log all the connections to my heart content, but boy mining the data to help show what happened in my above example has been tiresome at best. Can anyone here please suggest to me some type of logging and more relevantly, a data mining product that can help me achieve this end? Currently I am logging all my PIX traffic to a host running Kiwi syslog daemon, which archives each days logs into a separate folder in the dated logs directory, creating a new directory named for each date in the year. I am looking for a less clunky solution. Any help is GREATLY appreciated. Thanks! -- Carey************************************************************ Michael J. McCafferty Principal, Security Engineer M5 Hosting http://www.m5hosting.com Think of the fun you could have with a M5 Hosting Dedicated Server ! OpenBSD, Fedora, RHEL, Debian, FreeBSD, and more ************************************************************
-- ************************************************************ Michael J. McCafferty Principal, Security Engineer M5 Hosting 858-576-7325 Voice http://www.m5hosting.com ************************************************************ ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | MIVA Pen test, Jeffrey Leggett |
|---|---|
| Next by Date: | Re: Cryptocard database, Kurt Seifried |
| Previous by Thread: | Re: Data Mining for PIX Firewall Logs, Michael J McCafferty |
| Next by Thread: | Re: Data Mining for PIX Firewall Logs, Cesar Diaz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |