Usually 1–5 minutes. Restart the firewall engine for immediate effect.

| Preventive Measure | Why | |--------------------|-----| | Set up monitoring alerts | Receive email notification if categorization stops. | | Regularly check license expiry | Add a calendar reminder 30 days before renewal. | | Use redundant DNS servers | Prevents single-point-of-failure resolution issues. | | Document upstream proxy changes | Any proxy change requires updating Kerio. | | Test after updates | Category servers change IPs; test every quarter. | Q1: Can I use Kerio Control without cloud categorization? Yes, but only with static URL lists, IP-based rules, or by disabling web filtering entirely. Dynamic filtering will not work.

Go to or Web Filter → Upstream Proxy (version dependent).

If categorization is disabled , the appliance cannot query the cloud. Consequently, no website receives a category, and all content rules dependent on categories fail silently.

Kerio Control does not rely solely on static blocklists. Instead, it uses . When a user requests a website, the Kerio appliance queries a remote categorization server (provided by Kerio’s parent company, GFI Software, or a third-party partner like McAfee). The server returns a category ID (e.g., 92 for “Gambling”). The appliance then applies your content rules.