Module settings are used to configure the behavior of modules on a Web Gateway appliance. These modules are also known as engines or filters.
For example, the Anti-Malware module calls the scanning engines, such as the Gateway Anti-Malware (GAM) engine, when the body of a response sent by a web server should be scanned for infections.
By configuring the settings for this module, you can modify the scanning process. Depending on what you configure, the module might not call the GAM engine, which is the default, but a different engine for scanning.
Other modules are the URL Filter module, the TIE Filter module, or the Authentication module.
Different settings for a module
A module can have one particular instance of settings or several. Different instances of module settings are distinguished by their names. Usually, they differ in how the values of the various settings options are configured.
For example, after the initial setup of Web Gateway, there is one instance of the settings for the Anti-Malware module available by default. The settings name for this instance is Gateway Anti-Malware settings.
When the module runs with these settings, it calls the GAM engine for scanning, as this behavior is configured for one of the settings options.
After importing the Advanced Threat Defense rule set, however, a second instance of settings for the module is available. Its name is Gateway ATD settings.
When the module uses these settings, a web object is passed on from Web Gateway to Advanced Threat Defense for scanning, as the value for the relevant option within the settings differs now from the value for the same option in the default settings.
You can also create and configure settings instances of your own for any of these modules to let them show the behavior that meets your requirements.