About Guardian Policies

Note: This topic applies to the Hearst Release.

Policies determine how Guardian handles web content to best protect your users and your organization. You can create and deploy custom policies to fit your organization. Deploying custom policies entails:

Configuring custom policies based on your organization’s Acceptable Usage Policies (AUPs)
Configuring authentication policies; for more information, see Creating Authentication Policies
Configuring users’ browsers or network connections to use Guardian as their web proxy or default gateway; for more information, see Using Non-Transparent Connections and Using Transparent Connections.

Guardian enables you to create the following types of policies:

Web filter policies — Web filter policies determine whether to allow, block, soft block or whitelist web content that a user has requested. For more information, see Creating Web Filter Policies
HTTPS inspection policies — When enabled, HTTPS inspection policies determine whether to decrypt and inspect encrypted content in order to determine to handle the content based on web filter policies. HTTPS inspection policies can also be used to validate web site certificates. For more information, see Managing HTTPS Inspection Policies
Content modification policies — Content modification policies can be used to identify and stop malicious content embedded in web pages from being accessed. For information, see Creating Content Modification Policies .
Anti-malware policies — Anti-malware policies are used to against malware and viruses. For a detailed description about customizing anti-malware policies, see Creating Anti-Malware Policies .