Skip to content
StrongFirewall

Documentation

Inspection and access control

IPS, antivirus, URL filtering, decrypting proxy, captive portal, NAC and automation

1. Security profiles (IPS, antivirus, URL, DNS)

  1. In Objects › Security profiles, create the profiles: IPS (blocking by severity and custom signatures), antivirus, URL filter, DNS filter, sandbox and cloud access.
  2. In a Security policy with action permit, pick the profiles under Profiles. Only traffic from those policies is inspected.
  3. Commit. The ET Open rules ship with the image and are updated from the Update center.

2. Proxy and SSL decryption

  1. In Objects › Certificates, generate a CA (Generate › CA) and install its certificate as trusted on your network's computers (GPO, MDM or by hand).
  2. In Policies › Proxy — options, select that CA and review the never-decrypt domains (banking, government, health).
  3. In Policies › Proxy policies, create the rule: tcp-proxy (reads only the site name), ssl-decrypt (decrypts) or no-proxy.

3. Captive portal and per-user policies

4. NAC and single sign-on (SSO)

  1. In Users › Identity controllers, add the server (FreeRADIUS, Cisco ISE, Aruba ClearPass or another) with its shared secret. It must send RADIUS Accounting (Start/Stop) to the firewall on UDP port 1813.
  2. Create the Access roles (users and groups) and Access policies, then turn on Access control (NAC) for the controlled zones.
  3. Endpoints without an identity reach only the pre-authentication destinations. With escape mode, access is opened if the controllers become unavailable.

5. Automation and threat intelligence

In System › API tokens, generate a token with the right role (the value is shown only once). A threat-intelligence platform (MISP, OpenCTI, SIEM) can then push indicators, enabled in System › Threat intelligence (CIS):

curl -X POST https://<firewall>/api/threat-intel-feeds/push \
  -H "Authorization: Bearer sfwk_..." -H "Content-Type: application/json" \
  -d '{"indicators": ["198.51.100.7", "mal.example"], "minutes": 60, "reason": "campaign X"}'

IPs go into the kernel block list for the given time; domains go into the DNS filter. Everything is recorded in the threat logs.

6. Virtual systems

In System › Virtual systems, create a vsys and assign interfaces to it. Each vsys has its own routing (VRF) and separate sessions, so the same networks can exist in different vsys. Cap sessions, bandwidth and policies with Resource classes.