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 13:28:27 -0400 |
I should mention my only experience with this type of scenario was on a mid size business network, using snort, the snort payload didnt take up nearly as much space as i thought it would, i built the machines with 40gig drives each, and would dump the database to an archive and store it on tape every couple of months or so.
But i like you idea of just certain types of data. Now to just figure out which types are best to hold on to. Honestly, I wouldnt care if the logs were purged weekly or something, anything is better than what I have now.
I hope your company has lots of money for a SAN. I wouldn't recommend capturing payloads without a good reason. It will eat diskspace big time. I would turn it on when you see something that you need the data for.
Another choice would be to build tcpdump filter to collect payload data for specific types of data. Might not get everything but 10TB of data isn't something you are going to find any useful info in anyways.
,Remad
-----Original Message----- From: xelerated [mailto:xelerated@gmail.com] Sent: Tuesday, August 29, 2006 9:32 AM To: pen-test@securityfocus.com Subject: Packet Payload
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, Hirsch, Adam |
|---|---|
| Next by Date: | RE: Packet Payload, Matt Davis |
| Previous by Thread: | RE: Packet Payload, Remad |
| Next by Thread: | RE: Packet Payload, Remad |
| Indexes: | [Date] [Thread] [Top] [All Lists] |