Re: Restricting Open Proxies
- From: "Samir Pawaskar" <infosecofficer@xxxxxxxxx>
- Date: Thu, 21 Jun 2007 11:20:13 +0400
IMHO,
Another way would be to restrict outgoing http connections from users
only to your Web Proxy. That way everybody would be forced to use it.
You could put access list on the firewall i.e. if your users are
separated from the Proxy server by a firewall
Another option is if you have application aware switches, which can be
configured to redirect all http traffic to the proxy.
The flip side is however, in case you need to bypass proxy for certian
web sites then you will have to create list of exceptions..
At times this may be too much...
Samir
On 19 Jun 2007 11:45:54 -0000, shailesh.rangari@xxxxxxxxx
<shailesh.rangari@xxxxxxxxx> wrote:
Hi List,
We are in the process of strengthening our Information Security Policy. As part of this initiative we want to restrict access to Open Proxies from the Corporate Network.
We are currently providing Internet Access through Symantec Web Security which also acts as a Proxy Server.
The access to Open Proxies that keep floating in the wild is bothering us because it might ultimately lead to Information Leakage. Has any one of you faced the same issue? What are the best practices for the same?
Any ideas or suggestions are most welcome.
Thanks
Shailesh.
- Follow-Ups:
- Open Source Router with NAT
- From: Mohamed Farid
- Open Source Router with NAT
- References:
- Restricting Open Proxies
- From: shailesh . rangari
- Restricting Open Proxies
- Prev by Date: RE: VPN and Security
- Next by Date: RE: In secured office building, "Free Public WiFi" network shows up out of nowhere
- Previous by thread: Restricting Open Proxies
- Next by thread: Open Source Router with NAT
- Index(es):
Relevant Pages
|