Forget that there are obviously
reasons why they felt that filtering had to be implemented on equipment that happens to be owned by the company.
The fact that you're looking to get around their configuration seems to support their position that Internet filtering is necessary.
Most IT staff will be understanding and unblock a job-related site as long as you can provide justification as to why you need access. If its for your own personal perusal, however, don't expect them to budge. You should be doing that at home.
(Oh, and don't bother telling me how rude or inconsiderate I am for saying that. I've been a UNIX/NT network administrator for almost 10 years and have implemented filtering for everything from liability protection to flagrant employee abuse. In fact, I've had to install filters
because of potential liability lawsuits. The vast majority of companies don't block access just for the sake of blocking access.)
Quote:
|
The IT department can see what you are browsing without Blocking the site and could use it against you.
|
And more likely than not, they will. All major filtering packages keep track of every source and destination connection that goes out to the Internet, regardless of the IP address or host name. This data can then be available in nice, graphical reports that tell exactly where a person went at any given day or time. They can even categorize the
types of sites that were granted access and denied access.
Quote:
|
Some IT departments also forget to block the IP address of a particular website and just block the URL.
|
Most web hosting companies use virtual hosts where one IP address can belong to
thousands of web sites. The web server looks at the destination URL that you typed in and routes accordingly. So going directly via IP might not work anyway.
.
