Skip to main content

Check out Interactive Visual Stories to gain hands-on experience with the SSE product features. Click here.

Skyhigh Security

Import, Review, and Adapt a Web Policy

After you have created a backup of your on-prem web policy and exported it, you can import it for cloud use, review it, and adapt it as needed.

  1. On the Web Policy page, use the options that are provided for importing your on-prem web policy. Browse to the backup file that you created and exported on Secure Web Gateway (On Prem), select, and import it.

  2. Review your imported web policy. 

    • After the import, the total number of rule sets that were included in your on-prem policy is shown, for example, 483. 

    • If some of these rule sets could not be imported, their number is also shown, for example, 91.

      There are two reasons why an on-prem rule set could not be imported. Numbers of rule sets that cannot be imported for these reasons are also shown, for example, 40 and 51. The two reasons are as follows:

      • A former on-prem rule set is not compatible to a cloud environment.

      • A former on-prem rule set is compatible, but not supported under Secure Web Gateway (Cloud).


  3. Put your imported web policy in place. This means that you need to replace your existing cloud with it. Click the following option:

    • Replace existing cloud policy — Replaces your existing cloud policy with the imported policy

  4. Complete configuration activities to adapt the imported web policy to a cloud environment as needed. Consider the following:

    • Any sensitive information, for example, credentials and keys, that you used in your on-prem web policy might have to be changed in your web policy for the cloud.

    • If former on-prem rule sets are missing because they could not be imported, your web policy for the cloud might be less secure. Differently configured cloud-compatible rule sets might be needed to achieve the same level of security.

Former on-prem rule sets might not be compatible to a cloud environment because their rules include properties that are not cloud-compatible or not supported under Secure Web Gateway (Cloud). For a list of these properties, see List of Properties Not Eligible for Cloud Use.

  • Was this article helpful?