Demo – made-up data. Northline, the sites and the numbers are invented. Notices 3.5 – work in progress
VANTAGENorthline
Collected✕7 sites need attention

Attack path

Public VIP and WAN forwards through the enabling policy · built Sun Nov 22 2026 04:16 PM
3 highest2 middle2 tight

For each public VIP or WAN-facing forward: the destination, the policy that enables it, how wide the source and service are, NAT and profiles. Bridges Exposure to the policy graph. This page does not change a site’s colour.

What is listed
From show firewall vip, show firewall policy and show vpn ssl settings. A forward counts when its external address is globally routable IPv4 or IPv6 – documentation ranges (for example 192.0.2.0/24 or 2001:db8::/32) are not public. Each public VIP is joined to the accept policy whose destination is that VIP (or a group that contains it). WAN-facing allows from a public interface that are not a VIP are listed as well. An enabled SSL VPN portal is listed (Tools-only), banded by source width when parseable. House- on a policy keeps the real Attack-path band (Rebuild still greys it). Bands on this page are Tools-only: any source plus a risky port is highest; a narrowed source without UTM is middle; tight source, logging and UTM is listed as tight. They do not change a site’s colour. Suggested CLI is for you to paste; Vantage never sends it. Closed headings show destination, ports, source width and policy name – not the full policy block.
Atlantaclean

No public VIP or WAN-facing forwards

Azure Eastclean

No public VIP or WAN-facing forwards

Azure Westclean

No public VIP or WAN-facing forwards

Bostonclean

No public VIP or WAN-facing forwards

Charlotteclean

No public VIP or WAN-facing forwards

Charlotte OTclean

No public VIP or WAN-facing forwards

Chicago3 services · 1 highest
web (203.0.113.11)tcp 8443 · any · Web-Portal-In
Fortinet Any source on a public forward

web 203.0.113.11 · tcp 8443 · policy Web-Portal-In (#12) · source any · VIP NAT → 10.1.30.20 · IPS Northline-Servers, AV default, SSL Northline-Inbound

Today: web 203.0.113.11 · tcp 8443 · policy Web-Portal-In (#12) · source any · VIP NAT → 10.1.30.20 · IPS Northline-Servers, AV default, SSL Northline-Inbound
Should be: Narrow the source; do not leave a public forward open to any.

config firewall policy
edit 12
    set srcaddr "<source-object>"
next
end

Open on Exposure · Open on Rebuild

IT-AdminSSL VPN · narrowed · IT-Admin
Fortinet SSL VPN portal enabled

SSL VPN portal 'IT-Admin' · status enable · source US-Only

Today: SSL VPN portal 'IT-Admin' · status enable · source US-Only
Should be: Review who may reach this portal; keep the source narrow.

show vpn ssl settings

Open on Exposure · Open on Rebuild

Portal-LB-In (198.51.100.11)HTTPS · narrowed · Portal-LB-In
Fortinet Tight source, logging and UTM

Portal-LB-In 198.51.100.11 · HTTPS · policy Portal-LB-In (#13) · source narrowed · no NAT · IPS Northline-Servers, AV default, SSL Northline-Inbound

Today: Portal-LB-In 198.51.100.11 · HTTPS · policy Portal-LB-In (#13) · source narrowed · no NAT · IPS Northline-Servers, AV default, SSL Northline-Inbound
Should be: Keep the source narrow, logging on, and UTM attached.

Open on Exposure · Open on Rebuild

Dallas1 service · 1 highest
Warehouse-VendorsSSL VPN · any · Warehouse-Vendors
Fortinet SSL VPN portal open to any source

SSL VPN portal 'Warehouse-Vendors' · status enable · source any

Today: SSL VPN portal 'Warehouse-Vendors' · status enable · source any
Should be: Narrow source-address / source-interface on SSL VPN settings.

show vpn ssl settings

Open on Exposure · Open on Rebuild

Denverclean

No public VIP or WAN-facing forwards

Detroitclean

No public VIP or WAN-facing forwards

Detroit OTclean

No public VIP or WAN-facing forwards

Houston2 services
Plant-EngineersSSL VPN · narrowed · Plant-Engineers
Fortinet SSL VPN portal enabled

SSL VPN portal 'Plant-Engineers' · status enable · source US-Only

Today: SSL VPN portal 'Plant-Engineers' · status enable · source US-Only
Should be: Review who may reach this portal; keep the source narrow.

show vpn ssl settings

Open on Exposure · Open on Rebuild

MES-Portal-In (203.0.113.12)HTTPS · narrowed · MES-Portal-In
Fortinet Tight source, logging and UTM

MES-Portal-In 203.0.113.12 · HTTPS · policy MES-Portal-In (#14) · source narrowed · no NAT · IPS Northline-Servers, AV default, SSL Northline-Inbound

Today: MES-Portal-In 203.0.113.12 · HTTPS · policy MES-Portal-In (#14) · source narrowed · no NAT · IPS Northline-Servers, AV default, SSL Northline-Inbound
Should be: Keep the source narrow, logging on, and UTM attached.

Open on Exposure · Open on Rebuild

Houston OTclean

No public VIP or WAN-facing forwards

Los Angelesclean

No public VIP or WAN-facing forwards

Miamiclean

No public VIP or WAN-facing forwards

Minneapolisclean

No public VIP or WAN-facing forwards

New Yorkclean

No public VIP or WAN-facing forwards

Philadelphiaclean

No public VIP or WAN-facing forwards

Phoenix1 service · 1 highest
rdp-jump (203.0.113.27)tcp 3389 · any · RDP-Jump-In
Fortinet Any source on a risky port

rdp-jump 203.0.113.27 · tcp 3389 · policy RDP-Jump-In (#12) · source any · VIP NAT → 10.17.30.40 · no UTM

Today: rdp-jump 203.0.113.27 · tcp 3389 · policy RDP-Jump-In (#12) · source any · VIP NAT → 10.17.30.40 · no UTM
Should be: Narrow the source; do not leave a public forward open to any.

config firewall policy
edit 12
    set srcaddr "<source-object>"
next
end

Open on Exposure · Open on Rebuild

Seattleclean

No public VIP or WAN-facing forwards

Backups

philadelphia: no backup for 2 days – the FortiGate did not answer (site unreachable). See Change → Backups.