Scope and authorization
/01
Problem >
Scans that start before anyone signed off
What Vanguard does >
Allow-list, signed authorization, kill-switch
Result >
0 Jobs outside the allow-list
Capabilities
See it in the workbench
Scope and authorization, the recon and scan pipeline, explainable priority, ATT&CK coverage, retest and reports.
0-100 Point priority scale, every point explained
See all capabilities Vanguard capabilities
Problem >
Scans that start before anyone signed off
What Vanguard does >
Allow-list, signed authorization, kill-switch
Result >
0 Jobs outside the allow-list
Problem >
Every tool, its own output
What Vanguard does >
Open-source engines in ephemeral, hardened containers
Result >
1 Normalized findings model
Problem >
A CVSS list with no order of work
What Vanguard does >
Severity, CVSS, EPSS, KEV and exposure in one score
Result >
0-100 Every point accounted for
Problem >
Findings read one by one
What Vanguard does >
A deterministic technique map for every finding
Result >
1 Heatmap per engagement, no AI needed
Problem >
A fix nobody checked
What Vanguard does >
One-click targeted retest, with audit trail
Result >
4 Report formats: HTML, Markdown, JSON, SARIF
Recon and scan pipeline
/02 Problem >
Every tool, its own output
What Vanguard does >
Open-source engines in ephemeral, hardened containers
Result >
1 Normalized findings model
Explainable priority
/03 Problem >
A CVSS list with no order of work
What Vanguard does >
Severity, CVSS, EPSS, KEV and exposure in one score
Result >
0-100 Every point accounted for
ATT&CK coverage
/04 Problem >
Findings read one by one
What Vanguard does >
A deterministic technique map for every finding
Result >
1 Heatmap per engagement, no AI needed
Retest and reports
/05 Problem >
A fix nobody checked
What Vanguard does >
One-click targeted retest, with audit trail
Result >
4 Report formats: HTML, Markdown, JSON, SARIF
Access
Quoted on scope
Engagement models
For one system, one release, one deadline
Assessment
On request
- Scoped engagement with signed RoE
- Recon, scan and manual triage
- Prioritized report
- Retest of fixed findings
For teams that ship every week
Continuous
On request
- Recurring scheduled scans
- KEV and EPSS watch on your findings
- Webhook alerts to your chat
- Retest cycles on every fix
For security teams, on invitation
Workbench
On request
- Access to your engagements, on invitation
- Findings, evidence and reports in one place
- REST and MCP for your tools and agents
- Org-scoped tokens and audit log
Help
FAQ
Do you scan anything without written authorization?
No. Every engagement carries a scope allow-list and a signed authorization. A job aimed outside the scope is refused before it starts, a kill-switch stops what is running, and every action lands in an append-only audit log.
Where do findings and evidence live?
On Altovar infrastructure in the EU. The AI assistance is optional, and in our deployment it runs only through Altovar’s own gateway: no finding reaches a third-party model service.
Which engines run the scans?
Established open-source engines for discovery, crawling, dynamic testing, TLS, secrets and code analysis, among them nmap, nuclei, httpx and trivy. Each runs in an ephemeral, hardened container, and public engine images are pinned by digest.
How is a finding prioritized?
With the Vanguard Priority Score: severity, CVSS, the probability of exploitation (EPSS), presence in the known-exploited catalog (KEV) and internet exposure add up to a 0-100 score. Every point is shown next to the reason it was given.
Can our tools or AI agents drive it?
Yes. A REST API described in OpenAPI and an MCP server expose the same operations, with tokens scoped to your organization. Stress testing is deliberately out of reach for agents.
Do you run denial-of-service tests?
Resilience testing is its own authorized, audited workflow with a kill-switch, run through an external legal provider you approve. Vanguard never generates flood traffic itself: no botnets, no amplification.