This site is designed to allow Blue Coat Security administrators the ability to implement advanced policies using ProxySG. SGOS 3.2.3.3 or + is required to implement these configurations. To implement the configuration, please follow the instructions here.

Splash Page:
Many organizations would like to send out notices to all their employees or even redirect their first request to the corporate intranet web site. The Splash Page redirects the very first request to a predefined web page (aka Splash Page). Once users have read the Splash Page, they will not see it again. The Splash Page could be any of the following:

• Intranet site
• Internet site
• Disclaimer notice

You can find the configuration of the splash page here.

You can find the configuration of the splash page with a timer here.

Disclaimer Page:
The Disclaimer Page is a variant of the splash page. It sends a pop up for the very first request that would present the corporate policy. The pop-up then disappears automatically after 10 seconds.

You can experience the disclaimer page by clicking here.
You can find the configuration of the disclaimer page here.

Compliance Page:
The Compliance Page ensures employees see and acknowledge the corporate acceptable use policy to gain Internet access. Users need to accept the policy.

You can view the compliance page by clicking here.
You can find the configuration of the compliance page here.

Coaching:
Many organizations implement URL filtering in order to control employee web access. However, certain users may need to override the policy. ProxySG can remind users of the policy but allow the user to click on a link to override the policy. The override can be allowed based on parameters such as user, group, time and category basis.

You can view the coaching page by clicking here.
You can find the configuration of the coaching policy here.

Speed Bump:
Many administrator do not want to block categories, however they like to slow performance to non-business sites. The speed bump policy introduces a pre-defined delay to each accessed page for a set of categories, users, or groups.

You can view the speed bump page by clicking here.
You can find the configuration of the speed bump policy here.

Google and Yahoo Safe Search:
SafeSearch is a function that filters out adult content for images searches. Many Google and Yahoo! users prefer not to have adult sites included in their image search results. Google and Yahoo! SafeSearch screens sites that contain pornography and other explicit sexual content and eliminates them from search results. Google and Yahoo! filters check keywords and phrases, URLs and Open Directory categories to screen out potentially offensive material. add: The SafeSearch policy from Blue Coat automatically adds SafeSearch to all user image search requests, over-riding the users own settings.

You can find the configuration of the safe search policy here.

P2P Control:
P2P file sharing services allow an employee to circumvent corporate security measures. The very nature of the P2P client design is to evade firewalls and general network security. Additionally,blocking P2P at the firewall has proved to be extremely difficult because port blocking, as a means to controlling P2P, is very limited. P2P port usage can be dynamic and P2P protocols are not standards based, making them very difficult for administrators to detect much less control. P2P packets cannot be classified simply by looking at packet headers such as IP address and port number. Deeper packet inspection is required for effective P2P control.

You can find the configuration of the P2P Control policy here.

Block Phishing Attacks in the Enterprise:
A phishing attack is an attempt by fraudsters to fool a user into divulging confidential information over the Internet. Phishing attacks often start by spammers sending out email messages and asking customers to confirm their account information by clicking on a link found in the message. The user is then asked to enter their personal information such as name, social security number, bank account number, password, and PIN. Once captured spammers can use this information to deplete bank accounts, charge credit cards, and steal user identities.

You can find the configuration of the Phishing Attack Attack policy here.

Bob Kent Policy:
The Bob Kent policy includes all the discussed policies above.

You can find the instructions to run the demo with the Bob Kent Policy here.
And the configuration can be found here.