I had similar requirements and solved them by using a Proxy (Squid)
which requires http authentication.
Here's what I did:
In order to reduce the nuber of passwords needed, I ensured we could
authenticate against our Novell server by exporting the NDS via an LDAP
Gateway.
I used an LDAP auth module for squid which first checks if the user is
in the group "internet" on the Novell Server (Through an LDAP query) if
this is the case it then tries an LDAP bind as the given user. A
successful authentication lets the Internet usage go ahead.
I believe there are also modules for active directory, Windows DC,
radius and so on.
It is possible to set a rather long string as the http login "Realm"
information for squid and here I entered a long explanation informing
the person logging in of what was being logged and how long we keep the
information. Including a statement that the act of logging in means
acceptance of these conditions. The realm information is displayed (at
least in the IE) directly above the login fields.
The rest is easy, readily available tools such as sqrmgrlog will
process=
the squid log info into html pages that will allow you to see EXACTLY
when internet access occured and who looked at what. In fact you'll
probably find that your HR people may be a bit uncomfortable with the
amount of info you've got.
Since everyone has to authenticate to use the system it doesn't matter
a=
hoot from which PC they surfed from and you can easily set parameters
on=
the proxy to require renewed authentication after a given number of
minutes of non-usage.
This level of control generally require agreement between the workforce
and management, so i'd advise caution and consultation.
S.Cappendell
=2D----Urspr=FCngliche Nachricht-----
Von: Matt [mailto:Matt@acs-tech.net]
Gesendet: Mittwoch, 23. Juli 2003 19:44
An: purdy; jjhorner; forensics
Cc: Matt
Betreff: RE: Waste, Fraud, Abuse
Could Snort or any NIDS for that matter, tapped in at the last cable
between the users and firewall be substituted for a proxy=3F I too am
having this problem. All of our users are allowed to use our training
room PCs to surf the web while on lunch or break. However they are all
configured with roaming profiles which makes it near impossible to
determine weather or not the cookies/history were created while the
user=
was on a training PC or their production machine.
Thanks,
Matt
=2D----Original Message-----
From: Curt Purdy [mailto:purdy@tecman.com]=20
Sent: Tuesday, July 22, 2003 4:57 PM
To: 'JJ'; forensics@securityfocus.com
Subject: RE: Waste, Fraud, Abuse
The problem comes from someone cluefull enough to wipe cookies/history
and
not keep incriminating files. The best best answer is a proxy server
that
logs all access and an email server that keeps a record of all mail.
Curt Purdy CISSP, GSEC, MCSE+I, CNE, CCDA
Information Security Engineer
DP Solutions
cpurdy@dpsol.com
936.637.7977 ext. 121
=2D---------------------------------------
If you spend more on coffee than on IT security, you will be hacked.
What's more, you deserve to be hacked.
=2D- White House cybersecurity adviser Richard Clarke
=2D----Original Message-----
From: JJ [mailto:jjhorner@SAFe-mail.net]
Sent: Monday, July 21, 2003 11:29 AM
To: forensics@securityfocus.com
Subject: Waste, Fraud, Abuse
I'm in the process of updating our WFA analysis procedures. If any of
you
have defined (or mostly defined) procedures for investigation WFA,
please
send them my way. So far, we do the normal:
- extract browser history
- extract browser cache
- extract all known information formats (pictures, word processing
files,
mp3s, wavs, etc)
- extract cookies
- extract activity as captured by NIDS
Anything I need to add here=3F Anyone got any good (sanitized) final
WF=
A
reports=3F I'd also like to see if our format needs updating.
I understand that a lot of this is based on company HR policy, but I'd
like
to see industry best practices, if I could.
Thanks,
This list is provided by the SecurityFocus ARIS analyzer service.
For more information on this free incident handling, management
and tracking system please see: http://aris.securityfocus.com
Received on Sun Jul 27 10:39:56 2003
This archive was generated by hypermail 2.1.8
: Wed Aug 23 2006 - 14:01:44 EDT
|