Kenzer already tracks 195 governments live, passive and permission-free, in the National Threat Intelligence Database.
Deployed privately for your own ministries and agencies, it gives a CERT or defense & cyber intelligence agency continuous whole-of-government visibility — with active, in-depth verification available only where you choose to turn it on.
Kenzer's ideal deployment isn't a single company — it's the agency responsible for a nation's exposure as a whole: a CERT/CSIRT coordinating disclosure and incident response, a national cybersecurity agency setting baseline requirements across ministries, or a defense and cyber intelligence agency tracking adversary-facing infrastructure.
The National Threat Intelligence Database is a public, no-login view of the exact same engine — every government entity discovered, scanned, and graded, continuously.
Every ministry, agency, and state-owned enterprise nested as its own sub-organization under the national entity.
One continuously-recomputed sovereign score, drilling down to exactly which agency is dragging it.
Energy, water, telecom, healthcare, financial-sector infrastructure — tracked through continuous passive reconnaissance.
Active, in-depth verification (port/service enumeration, vulnerability scanning) available once authorized.
Findings ranked by real exploit maturity — EPSS, VEDAS, CISA KEV cross-referencing from ARPSyndicate's own Exploit Observer dataset.
A CERT triage queue surfaces what's actually being weaponized, not just what's high-CVSS.
The same discovery engine behind ARPSyndicate's Subdomain Center.
Built specifically to find infrastructure a ministry didn't know it was running — where most government-sector exposure actually lives.
Log a shared-provider incident once.
Every ministry or agency with a detected dependency on that provider (a cloud host, a CDN, an identity provider) is flagged automatically — no waiting for each one to self-report.
Grant each ministry's own IT/security team a scoped login into only their own sub-organization.
They triage and fix their own findings, and the national rollup score improves automatically as they do.
A one-click PDF per ministry, or a whole-of-government report in one pull, for briefing an oversight body or a minister directly.
No.
Everything in the public National Threat Intelligence Database — including every government listed — is built entirely from passive, non-intrusive reconnaissance: the same kind of publicly observable information any researcher (or adversary) could already gather.
We never run active or intrusive scanning against any government's infrastructure without that government's own explicit authorization first.
The National Threat Intelligence Database is a public demonstration on our own initiative.
A government's own private deployment — its own ministries, its own findings, its own remediation workflow — is access-controlled and not published anywhere.
No. Kenzer observes from the outside — no agent install, no VPN, no inside access required to get started.
Anything beyond passive observation is opt-in and authorized by you first.
Yes — see how remediation access works on the Third-Party Risk Management page.
The same scoped-access mechanism used for third-party vendors works identically for internal agencies.
Every score comes from real reconnaissance of the target's live infrastructure — not a self-reported questionnaire response.
Passive by default, with port and service enumeration or vulnerability scanning performed only once we have that government's explicit authorization.
The National Threat Intelligence Database shows what's public. A private deployment shows everything — every ministry, every agency, every finding.