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

Knowledge base

Where the documents are · built Sun Nov 22 2026 04:16 PM
Vantage keeps pointers, not copies: every entry opens the document where it lives (SharePoint or the shared drive), so it is always the current version and SharePoint decides who may read it.
Floor plans and building drawings on file – 21 for 21 sites

Vulnerability and threat feeds: how Vantage gets and uses them

Built into Vantage (not a link to SharePoint). The sections below follow Settings → View as.

A. Overview for leadershipwhat it is, what it guarantees, where the data comes from

Today: vulnerability list built 2026-11-18: 55 Fortinet vulnerabilities, 1 of them known to be exploited; known-bad address list built 2026-11-18: 153 addresses; last update run 2026-11-18: 7 of 7 sources updated.

What it is for

Vantage compares the firmware our FortiGates, FortiSwitches and FortiAPs run with public lists of known vulnerabilities, and the addresses in each FortiGate's configuration with a public list of compromised hosts. It also checks that each FortiGate uses the threat data our FortiGuard subscription already pays for to block known-bad addresses. The results are on the Firmware page, on Security → Known-bad addresses and on each site's page.

What it guarantees

  • Nothing about our network leaves the building. The update only downloads public lists; all matching happens on the collector.
  • It contacts 7 public web sites and no others, over HTTPS. The list is fixed in the code and in the firewall rule for the collector.
  • Vantage only reads. It never changes a FortiGate. Suggested commands are text for an engineer to review.
  • Every source was checked for commercial use. Lists whose terms were unclear or need a paid licence were left out.
  • Bad or partial downloads are refused, and a source that fails keeps its last good copy – the pages never show "nothing found" because a download failed.

Where the data comes from

  • NIST National Vulnerability Database (NVD), CVE API 2.0 – CVE records for FortiOS, FortiSwitch and FortiAP (with affected versions) and for the bundled CPython and OpenSSL.
  • CISA Known Exploited Vulnerabilities catalog – Which CVEs attackers are known to use ('exploited in the wild').
  • CISA industrial control system (ICS) advisories – Advisories for industrial and IoT equipment; matched to the makers Vantage sees in Inventory (by MAC vendor).
  • Fortinet PSIRT advisories (FortiGuard RSS) – New Fortinet advisories (FG-IR numbers), often before NVD has the version data.
  • CVE Program records (CVE Services API) – Fortinet's own CVE record, with affected versions, for advisories NVD has not analysed yet.
  • FIRST Exploit Prediction Scoring System (EPSS) – For each CVE: the probability it is exploited in the next 30 days, and its percentile.
  • OSV.dev open source vulnerability database – Advisories for the Python packages that ship inside Vantage.
  • Emerging Threats (Proofpoint) compromised hosts – Addresses of known compromised or hostile hosts (rule numbers 2000000-2799999 only).

Turned down: abuse.ch, Spamhaus, Team Cymru, Tor, DShield, FireHOL, blocklist.de, the account-based services, ENISA EUVD and the Microsoft MSRC API – for licence terms, logins or noise (section C has the reasons).

What the labels mean

  • Exploited in the wild – CISA lists the vulnerability as used by attackers somewhere. It does not mean we were attacked. These come first.
  • EPSS – the chance (from FIRST) that a vulnerability is exploited in the next 30 days, and how it ranks against all others. A planning aid, not a verdict.
  • New Fortinet advisory – versions not yet confirmed – Fortinet has published it but the version data is not out yet. An engineer checks it by hand.
  • Known-bad address – an address in our configuration is on the Emerging Threats compromised-host list. A list is not proof; an engineer checks who uses it today.
  • Best Practices notes (grey) do not change a site's colour.

What it costs and what it does not do

The sources are free. It does not block traffic – that is the FortiGate's job, and the Best Practices note says how. It does not know the model or patch level of Windows servers, printers or IoT devices yet: Windows per-server patch data waits for the SentinelOne vulnerability module, and printer/IoT polling (SNMPv3) is planned for 3.0.

How Vantage was built

Vantage was developed with the help of Claude Code, an AI coding assistant, working from published Fortinet and CISA guidance and the public sources listed in this article. Every change is reviewed by the Vantage owner and tested in a lab on a Windows Server against several FortiGates before it is released.

For every site3 documents

Vantage guides · how Vantage works, for each kind of reader · each guide folds by chapter

Each guide is also a file in the release, under C:\netmap\docs\guides\ – the page and the file are the same text.

By site21 sites
SiteFloor planOther documentsEquipment rows filled inSite factsCircuit contractsNetworks described
Atlanta✓ 1022126
Azure East✓ 101120
Azure West✓ 101120
Boston✓ 104126
Charlotte OT✓ 107106
Charlotte✓ 107126
Chicago✓ 1019146
Dallas✓ 1027126
Denver✓ 1019126
Detroit OT✓ 107106
Detroit✓ 107126
nothing on file yet
Houston OT✓ 107106
Houston✓ 107126
Los Angeles✓ 104126
Miami✓ 104126
Minneapolis✓ 103126
New York✓ 104126
Philadelphia✓ 104126
Phoenix✓ 104126
Seattle✓ 1014126

Each site's own documents, equipment register, contracts and IP plan are on its page, under Library.