Skip to main content



Open-source Forensics Tools for Network and System Administrators

Spider Panel Discussion
Thursday, November 30
More info | Video

Things that must be considered when using Spider:

  1. Get your local technical support involved. If you have local technical support it is best to request their help and get them involved when using Spider. They can help ensure local procedures are followed and provide valuable guidance and insight into Spider's use.
  2. Promptly remove the resulting Spider log file. Since this file can contain direct pointers to some very sensitive information, this file must be very well protected and removed promptly to ensure it isn't used by unauthorized people.
  3. Verify each file that Spider finds. Due to the method Spider uses to discover potentially sensitive files, Spider produces false alarms. Each file must be verified to ensure the data is truly a social security number or credit card number before decisions can be made concerning what to do with the file.
  4. If you run into problems running Spider contact security-services@cornell.edu. You can also send questions to the Spider mailing list, cuspider-l@cornell.edu.

Spider Capabilities

Spider 4.0 for Linux (08/09/07):
- Documentation
- Download
MD5: 91db82a1fe3187e84a3f5d46b3b9a088
Spider 2.9.5 for Windows (11/05/07):
- Documentation
- Download
MD5: 8a72091866d444e2e6fdeacfcc71688c
Spider3 for Windows, includes source (05/16/08)
- Documentation
- Download
MD5: 4070BDED3C64CAD4E6853ED473439C58
Spider Beta Test for Mac OS X, plus source (06/08/07)
- (Documentation in progress)
- Download
MD5: b11ea25fb96cf0944bf2f2612c3e22fe
Spider Engine for UNIX, source (10/25/07)
- (Documentation in progress)
- Download
MD5: bbb4d635e4d9669167bf5790ada492cc

To subscribe to cuspider-l, send mail to lyris@cornell.edu with the following in the body of the message: subscribe cuspider-l "Your Name"


Return to: Technical Support Providers site | Security site