Policy configuration

To protect your network against threats arising from the web, Web Gateway enforces a web security policy, which is implemented during the initial setup. You can configure this policy later on to adapt it to your requirements..

When performing this configuration, you are dealing with several fields of web security that your policy should cover. You can also extend the filtering process and make it suitable for cloud use.

  • Web security policy — A web security policy is made up of rules, which are grouped in rule sets on Web Gateway

    When a situation arises where a rule applies, it performs an action to handle this situation. The situation can be an immediate threat, for example, a virus in a file that a user who works within your network attempts to download. In this case, the rule would block the attempt.

    Other situations might be that a user requests access to an online shopping site during work hours or tries to download a very large streaming file. Both activities could be blocked by suitable rules.

    You can modify all rules in the rule sets on Web Gateway to let them perform the actions that you consider appropriate.

    When a rule performs an action, the user who requested web access can be informed about this action by a message. For example, the user can be told that a request was blocked because a file that was requested for downloading is malware-infected.

  • Cloud use — The rules of your web security policy are applied to the traffic that is created by the web usage of the users of your organization.

    Unless you configure it differently, however, the rules are only applied to the web usage of those users who access the web from inside your local network. This kind of usage is also known as on-premise use.

    You can, however, enable one or more rule sets for cloud use. This means that the rules in these rule sets are also enforced when users of our organization access the web from outside your local network.