Since you need a heavy monitoring ... you need to integrate a web sense server in that case though there are online logging server available which does log the traffic along with the "URL" however they are not as scalable as paid websense..a paid pastry always tastes well than a robbed one..:-)
you may use Websense or N2H2
url-filtering software....also there is a cache length on web sense that stores and loggs the traffic . this length can be customised as per the traffic that you need to log in there...
To accomplish URL filtering, pix can be configured with Websense (www.websense.com) or
N2H2 (www.n2h2.com) in this way:
a)A client establishes a TCP connection to a web server.
b)The client sends an HTTP request for a page on this server.
c)The pix intercepts this request and hands it over to the filtering server.
d)The filtering server decides if the client should be allowed access to the requested
page.
e)If the decision is positive, the pix forwards the request to the server and the client
receives the requested content.
f)If the decision is negative, the client's request is dropped.
NOTE: Websense works with pix version 5.3 onwards and N2H2 works with pix version 6.2
onwards. These can only perform HTTP filtering not FTP or HTTPS. Although for blocking ftp
sites, a URL like ftp://ftp.somedomain.com can be entered.
For configuring N2H2 or Websense with pix, the following command syntax are required:
N2H2:
[no] url-server [(if_name)] vendor n2h2 host local_ip [port number] [timeout seconds]
[protocol {TCP | UDP}]
WEBSENSE:
[no] url-server [(if_name)] vendor websense host local_ip [timeout seconds] [protocol {TCP
| UDP} version]
show url-server
show url-server stats
This would also be available at:
http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_refer
ence_chapter09186a00801727ae.html#1026449
