Article View: comp.os.ms-windows.nt.admin.security
Article #2Re: Computer Forensic - Research
From: J Barkwin
Date: Thu, 19 Dec 2002 04:00
Date: Thu, 19 Dec 2002 04:00
48 lines
3219 bytes
3219 bytes
Regarding the first part... it's a touchy subject in the States due to strong privacy advocacy (which is a good thing) but the bulk of court cases have found for the company; in that the company owns the computer so they reserve the right to search it. Likewise, they own the phone system so they are allowed to monitor it if they have reason to believe it is being abused. I am pretty sure you have to have a policy stating this in your company new hire documentation. I have heard that there is a rule of thumb in performing computer forensics or in monitoring phone conversations that if you come accross something that is personal and unlrelated to the case/investigation, you should not continue listening/reading that document/file/phone call. "stephen" <stephenthornber@dsl.pipex.com> wrote in message news:<3dfc67ae$0$239$cc9e4d1f@news.dial.pipex.com>... > Hello All, > > I am researching material for a Computer Forensics book based mainly on UK & > European legislation. > > I think the sort of area I am considering are these -: > -_-_-_-_ > Some one is reported as having broken company policy on their computer - > maybe downloading Copyrighted material, or they have been seen to be > browsing websites that contain illegal offensive or immoral material, they > have sent an offensive / libellous / derogatory email to the boss...... > What does the MIS and IS specialist, network administrator, auditor, > investigator need to do to prove the case? > > or Police forensic procedures > > or Police forensic evidence elimination - is it possible > > > -_-_-_-_ > > Please let me know of any questions that you may have that you think could > be answered by such a book. > > Have you ideas for sources to research? > > What is your wish list for such material? > > thanks and all the best
Technical Details
Message-ID:
<ee51488d.0212182000.bde27@posting.google.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mailReferences:
<3dfc67ae$0$239$cc9e4d1f@news.dial.pipex.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 112bec,eec3a8662c99445b X-Google-Attributes: gid112bec,public X-Google-Thread: ff723,eec3a8662c99445b X-Google-Attributes: gidff723,public X-Google-Thread: f9855,eec3a8662c99445b X-Google-Attributes: gidf9855,public X-Google-Thread: 1117b6,eec3a8662c99445b X-Google-Attributes: gid1117b6,public X-Google-Thread: f977f,eec3a8662c99445b X-Google-Attributes: gidf977f,public X-Google-Thread: fda0e,eec3a8662c99445b X-Google-Attributes: gidfda0e,public X-Google-ArrivalTime: 2002-12-18 20:00:31 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail From: jbarkwin@yahoo.com (J Barkwin) Newsgroups: comp.os.ms-windows.nt.admin.security,comp.security.misc,microsoft.public.security,microsoft.public.win2000.security,uk.adverts.books,aol.books Subject: Re: Computer Forensic - Research Date: 18 Dec 2002 20:00:31 -0800 Organization: http://groups.google.com/ Lines: 48 Message-ID: <ee51488d.0212182000.bde27@posting.google.com> References: <3dfc67ae$0$239$cc9e4d1f@news.dial.pipex.com> NNTP-Posting-Host: 68.70.218.116 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1040270431 11220 127.0.0.1 (19 Dec 2002 04:00:31 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 19 Dec 2002 04:00:31 GMT