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: Packet Payload |
|---|---|
| Date: | Tue, 29 Aug 2006 20:05:57 -0400 |
This is perfectly possible, and very feasible for many environments. In fact, I do it routinely. It's part of the Network Security Monitoring methodology. Most NSM practitioners collect IDS alerts, network session information and pcaps, subject to data retention policies and available storage of course. If you want to learn more, check out Richard Bejtlich's book, "The Tao of Network Security Monitoring." There's also an open source NSM suite which can help you collect an analyze all this data: The Sguil project at http://www.sguil.org (of which I am a member). Personally, I've been collecting pcaps for quite some time now, and I can't imagine having to do my job without that. I'm a lot more efficient when I can simply go back to "the source" and check to see exactly what happened. David xelerated wrote:
Im posrting this to the pen-test group, rather than firewall or IDS because it covers many areas. Id like to see what the pro's think about capturing and storing packet payloads from firewalls, ids, etc... everything rather than just loggin the incidents. Im trying to explain to my management how useful the payloads could be if we were ever to really need them, say from a forensics point of view. To give another example, one time I was seeing lots of firewall drops, I could tell what ports, src and dest. but no packet data. To everyone involved it looked like a worm trying to spread. Well in the end it wasnt, infact is was something that was nice to know about, but it was not hostile traffic. But if I had been able to see the payloads i could have seen the data request and known from the start what it was, or was not. What would be really great, is a whitepaper covering this, or enough info/facts that I could throw one together. thanks! Chris C|EH, CISSP ------------------------------------------------------------------------ This List Sponsored by: Cenzic Need to secure your web apps? Cenzic Hailstorm finds vulnerabilities fast. Click the link to buy it, try it or download Hailstorm for FREE. http://www.cenzic.com/products_services/download_hailstorm.php ------------------------------------------------------------------------
------------------------------------------------------------------------ This List Sponsored by: Cenzic Need to secure your web apps? Cenzic Hailstorm finds vulnerabilities fast. Click the link to buy it, try it or download Hailstorm for FREE. http://www.cenzic.com/products_services/download_hailstorm.php ------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Packet Payload, Javier Romero |
|---|---|
| Next by Date: | locate windows workstation if you know the username, offset |
| Previous by Thread: | Re: Packet Payload, Mike Klingler |
| Next by Thread: | Re: Packet Payload, Security |
| Indexes: | [Date] [Thread] [Top] [All Lists] |