Threat Surface Probe — Template-Driven Vulnerability Checks
This runs a large, community-maintained library of detection templates against a target. Each template encodes a specific check — a particular CVE, an exposed administrative panel, a known misconfiguration, a default credential — and the library is updated continuously as new issues are published.
Why run it
Its strength is currency. When a widely exploited vulnerability is announced, a detection template usually exists within days, and the question every operator has at that moment is whether they are affected. Answering it by reading advisories and inventorying versions takes days you may not have; running the template answers it directly. The breadth matters too — templates cover things nobody thinks to check, like default credentials on a device that arrived preconfigured.
Why automate it
The template library changes daily and your infrastructure changes weekly, and either can turn a clean result into a finding. The value is in the gap between a vulnerability becoming public and it being exploited at scale, which is often measured in hours — automated scanning is what fits inside that window. Scheduled runs also catch the case where new infrastructure is deployed carrying an issue the rest of your estate was already patched against.
What it gives you
Fast answers to "are we affected by this" at the moment the question becomes urgent, and continuous coverage as the list of known issues grows. The currency of the template library is what distinguishes it from a static scanner.