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.




Network Security Security-Basics
[Top] [All Lists]

RE: Network protocol analyzers

Subject: RE: Network protocol analyzers
Date: Wed, 28 Nov 2007 16:58:10 -0000
Im a big fan of Packetyzer as well, its actually a fork of the ethereal
source code

Kind Regards,

 

Christopher Boczko

Server Support Analyst

IT Shared Services - Homeserve PLC

-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of Michael R. Martinez
Sent: 28 November 2007 16:39
To: Malhoit, Lauren; listbounce@securityfocus.com; security-basics
Subject: Re: Network protocol analyzers

Packetyzer is a good free protocol analyzer for windows. I prefer wire
shark, but packetyzer is good too.

Mike

Michael R. Martinez
TF: 800-987-7307

-----Original Message-----
From: "Malhoit, Lauren" <Lauren.Malhoit@tylertech.com>

Date: Wed, 28 Nov 2007 11:22:43 
To:"security-basics" <security-basics@securityfocus.com>
Subject: Network protocol analyzers


I'm using Wireshark (used to be ethereal).  Does anyone know any better
protocol analyzers?  Preferably open source.  If you like Wireshark, why
do you like it?  

-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of Nick Vaernhoej
Sent: Tuesday, November 27, 2007 7:41 PM
To: security-basics
Subject: RE: Securing workstations from IT guys

A key logger? At what point are we crossing the line of common decency
towards co-workers?
I realize it is company property and all, but if you log access to
sensitive files and audit these logs do you really need to be more
intrusive?

This is not an attack, more a tagged on question to everyone?
Is keystroke logging commonly accepted by you?

Nick Vaernhoej
"Quidquid latine dictum sit, altum sonatur."


-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of Vandenberg, Robert
Sent: Tuesday, November 27, 2007 11:18 AM
To: security-basics
Subject: RE: Securing workstations from IT guys

 
Those are good points.

I would recommend that you put in a keystroke logger program with the
written approval of your upper management on the PCs in question and
then download the logs each day.  That way you are able to create a
forensics "e-Trail" that can be used to confront/counsel/etc. them.  I
would also make sure that you look at your documenation and ensure that
each IT person has signed a document stating that they will not use
their abilities improperly.  Combine those two and you have a means of
pursuing them legally. 


This electronic transmission is intended for the addressee (s) named
above. It contains information that is privileged, confidential, or
otherwise protected from use and disclosure. If you are not the intended
recipient you are hereby notified that any review, disclosure, copy, or
dissemination of this transmission or the taking of any action in
reliance on its contents, or other use is strictly prohibited. If you
have received this transmission in error, please notify the sender that
this message was received in error and then delete this message.
Thank you.
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/

<Prev in Thread] Current Thread [Next in Thread>