Note: This topic applies to the Edinburgh Release.
HTTPS inspection policies enable you to inspect and manage communication between users on your network and web sites which use HTTPS by configuring an inspection method for different user groups, destinations and locations.
Guardian processes HTTPS inspection policies in order of priority as listed on the Guardian > HTTPS inspection > Manage policies page, from top to bottom, until a match is found. You can change the order by dragging and dropping policies in new positions.
Guardian comes with three pre-configured HTTPS inspection policies which handle the following content:
|||Online banking – when enabled, this policy allows users to do online banking without communications being decrypted and inspected|
|||All encrypted content accessed by unauthenticated IPs – when enabled, this policy decrypts and inspects all encrypted content that users at unauthenticated IPs try to access|
|||Certificate validation – enabled by default, this policy check secure certificates on web sites. Any sites whose certificates are self-signed, out of date or otherwise invalid will be blocked.|
|1.||Go to the Guardian > HTTPS inspection > Manage policies page.|
|2.||Locate the policy you want to enable, click on the Enabled bar to change it to a green tick.|
|3.||Repeat the step above for any other policies you want to enable and then click Save. Guardian enables the policies.|
Note: When, for the first time, you enable a HTTP inspection policy which decrypts and inspects content Guardian informs you that users’ browsers must have the Guardian CA certificate in order for the policy to work.
You can click on Guardian CA certificate in the text displayed and download the certificate ready for import into browsers. See Managing HTTPS Inspections for more information about how to import the certificate.
You must specify the order Guardian applies HTTPS inspection policies
|1.||Go to the Guardian > HTTPS Inspection > Manage policies page.|
|2.||Locate the policy in the HTTPS policies panel.|
|3.||Drag and drop the policy to where you want Guardian to apply it. For example, if you have created a policy which does not inspect the Google HTTPS AdSense site when accessed by marketing students, drag the policy to the top of the list of policies.|
|4.||Click Save. Guardian re-orders and applies the HTTPS inspection policies and allows all users in the marketing student group to access the Google AdSense site.|
|1.||Go to the Guardian > HTTPS inspection > Manage policies page and locate the policy you want to edit.|
|2.||Click the Edit policy button. Guardian displays the policy settings on the Guardian > HTTPS inspection > Policy wizard page.|
|3.||Make the changes necessary, see Creating an HTTPS Inspection Policy for more information about working with policies.|
|4.||Click Confirm. Guardian displays the settings you have selected. Review them and click Save to save the changes to the policy. Guardian updates the policy and makes it available on the Guardian > HTTPS inspection policies > Manage policies page.|
|1.||Go to the Guardian > HTTPS inspection > Manage policies page and locate the policy you want to delete.|
|2.||Click the Delete policy button. Guardian prompts you to confirm that you want to delete the policy.|
|3.||Click Remove. Guardian deletes the policy.|