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: Securing workstations from IT guys

Subject: Re: Securing workstations from IT guys
Date: Wed, 28 Nov 2007 23:11:03 +0000
There has got to be a better way than taking an investigation out on all 
employees. Have you identified any IP addresses that are creeping on your 
clipping levels, what exactly are you trying to do? Do you feel corporate 
espionage is occuring? There are so many ways to catch someone doing the wrong 
thing, but don't you feel that ultimately if end users are doing the wrong 
thing that it is up to you as the security guy to put in place the appropriate 
controls and preventitive measures to prevent this. In my opinion this is going 
to be far to time consuming wasting good time like this when proper planning 
and controls could have been put in place. This I wouldn't even consider 
because there are many laws that protect employees from this behavior. In one 
case the judge ruled that employees do have rights to privacy and an employer 
should let employees know that their systems are monitored and that the 
employee agrees to those terms of privacy being revoked, smyth v. Pillsbury. 
Just my two cents!
Michael R. Martinez
TF: 800-987-7307

-----Original Message-----
From: "Nick Vaernhoej" <nick.vaernhoej@capitalcardservices.com>

Date: Wed, 28 Nov 2007 10:10:27 
To:"security-basics" <security-basics@securityfocus.com>
Subject: FW: Securing workstations from IT guys


A key logger? At what point are we crossing the line of common decency
towards co-workers?
This with the understanding that the person snooping in HR material is a
scumbag, however, the remaining innocent PC's of the pool in question
will be receiving the same treatment.
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 within a corporate
setting?

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.

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