Web page monitoring
A network security analysis and monitoring toolkit Linux distribution.
Brought to you by:
pblankenbaker,
rwhalb
Hi Paul;
First, I would like to thank you for your help with the ET rules for Snort it worked great!!!!
I do have two questions.
1. Is it possible to monitor web surfing activities using NST. I would be insterested in which users went to which sites and for how long. I saw that squid was included in NST but i don't think it was configured in this way.
2. Is it possible to use Snort inline as an IPS with the NST configuration?
Thank you in advance
Patrick
Hi Patrick:
I'm glad to hear that the ET rules for Snort are working for you.
1. As far as using squid to monitor web traffic:
It is easy to start the squid (proxy) server on your NST system, run the command:
If you want squid started whenever the system reboots, also run the command:
By default, the proxy server will start up accepting connections on port 3128. Users will not be required to login to use the proxy server. You should be able to try it out by configuring a web browser on your network to use the NST as its proxy server (you'll need to know the IP address of the NST system).
Any request which goes through squid should create a log entry in the file: /var/log/squid/access.log. This will include time information, the machine that made the request and the web site which it went to. You can then use a "squid log analyzer" to process the results of the log file into a more human readable form.
Here's an example of using the calamaris analyzer:
The output will be long and show statistics about the domains (google.com, cnn.com, …) visited by each system using the proxy server. Here's a portion of the report after having two systems connected to the proxy server (tortilla-e.linux.bogus and cayenne-e.linux.bogus) for a short time and hitting a couple of web sites:
Notice that this report shows the web servers each system using the proxy server went to. I'm not sure how easy it would be to get it to map to individual users. Also, if you aren't happy with calamaris output, you might want to google a bit on "squid log analyzer" as there are quite a few options available.
I don't typically set up squid to require user login, but maybe if you figured out how to do that, then maybe there would be information in the log file to tie the requests to individual users. If you choose to pursue this route, I'd be interested in hearing how you make out.
Now, the other problem is forcing traffic through the proxy server. If you aren't planning on using the NST system as a gateway on your network, you will need to prevent users from accessing web sites directly. This usually involves going to your firewall/router and setting up rules such that connections to port 80 and maybe 443 are only permitted if they come from the IP address of your proxy server (the NST system running squid).
Finally, you may want to look at adding the package "squidGuard". I haven't used it, but I know it is intended to be used in conjunction with squid to redirect/block certain web traffic.
2. As far as using Snort inline as a IPS with the NST configuration, it's funny you should ask. Ron is currently working on updating the snort package to the 2.9.0 release and he hinted to me that IPS functionality will be included. I'm not exactly sure what his plans are at the moment, but I would expect to see something in the near future.
Have a good day,
Paul
Hi Paul;
Thanks for the quick response!!!
The suggestion for squid are great and I will be pursuing the different squid options as you mentioned…and if you like I can give you updates as to what worked and what didn't work. I can do it here on this forum incase others are interested in doing the same thing.
As for the 2.9.0 version that would be fantastic and including IPS functionality would be awsome!!….Way to go Ron and Paul..
Keep up the great work and I love this product!!!!
Patrick