De_Jappe wrote:
Now IF you find something over the network, Then find that he's doing something bad and fire him.
Isn't he able to sue you then for illegitimately obtained proof?
Anyway few things I should think off is:
-Can't you log in as his account, as network-manager?
-Can't you sniff his packets over the network? Even if it's encrypted if you notice too much packets being sent, should be suspicious enough about software sharing.
-Log in with a live cd when he's away, browse the harddisk with that.
Those are alternatives, I just don't get how a local would be able to set permissions so the root can't change it but he can. Root should be able to change permissions any time, that's why it's the root.
If all else fails, confiscate his computer and give him a temp new one.
we've sniffed his packets, thats why we think he's up to something...
i dont know his password (and have no way of finding out unless i ask him) so i cant use his account.
the live CD is a good idea, i just need to make sure hes not going to be around or log on remotely.
as long as he has local admin rights, he can set the permissions on his local drives any way he sees fit. he basically has the root account to his computer, and he has denied my network admin account from accessing his c drive root. that isnt really enough to say hes breaking policy, because he deals with confidential company data, so i'd rather him be strict with file permissions.
the reason we are being so sketchy is because he is an IT person, so we need to make sure this guy doesnt do anything malicious to the network should we accuse him of any wrongdoing. its a bad situation if we accuse him, and he isnt doing anything wrong. he will then have a serious grudge against us which is not good should he decide to quit someday.
VicktorVauhn wrote:
Its kinda hard for anyone here to make suggestions not knowing what power you have over this guy, and the legal rights he has to the privacy of his machine. If he has none, walk up and tell him you need to check his computer.
If he does have the right to privacy, and you hack your way in and check it anyways... what good does that do? Your gonna bust him with illegal activities you found after illegally gaining access to his computer?
he has no expectation of privacy. its a company owned computer so we can do whatever we want. but we certainly dont want to wrongfully acuse someone though because of the negative fallout. see my double edged sword...
there are too many horror stories of disgruntled IT people wrecking the network when they get fired, so we have to be very careful with our investigation.
jsnipy wrote:
If you have been explicitly denied, and you have access to the management console make a new account and add it to admin.
score... sounds like a winner, except the group policy restricts which accounts can access the machine over the network. not saying it would be hard to do, just time consuming, and perhaps noticeable to my target... a good idea nonetheless, especially if he doesnt really pay attention to any policy changes.
jsnipy wrote:
[TUF]Catbox wrote:
this sounds a little fishy... no offense...
If he works for a company... he's using company equipment right?
What does the head of the company say about this?
Well, the politics is his affair, he is asking how to do it technically.
@OP ...
Can you take ownership using xcacls?
exactly, we want to be delicate in our handling of the matter. you dont walk up to a ten year employee and say "what the fuck are you doing" without having some damaging evidence that will prevent a wrongful termination lawsuit.
i cant get the cacls to work because every account i've tried is denied access. i can make a new share on his machine if i specify an explicit path other than the c: drive, so he obviously has some folder on there he doesnt want us to see. very tricky...