What we commit to
- Findings enter the shared alert queue. There is no separate inbox to forget.
- Every asset is scanned or is a counted exclusion with a stated reason.
- Scanning rides the agent and appliance you already run.
See what an attacker sees
Coming soon. Your client’s exposure changes every week, and nobody is watching it between annual reviews. Scan the outside and the inside from the platform you already run, with findings in the same queue your team already works.
Alerts
Critical
Backup chain broken on FS-02
Cormorant Logistics • 12 downstream alerts suppressed because this explains them
Resolved
Chain repaired, verification passed
Closed automatically on product evidence, ticket synced to your PSA
Most scanners hand you a list
Most scanners hand you a PDF with hundreds of items, ranked by a score that means nothing to the client paying for it. The report gets filed, the exposure stays open, and the next scan produces the same list plus twelve more.
The three ways it goes wrong
A separate inbox to ignore
A scanner with its own portal is one more place your team forgets to look.
Findings with no owner
A finding without a ticket, an owner, and a lifecycle is a note. Notes sit.
Coverage nobody can state
If you cannot say what was scanned and what was skipped, you cannot answer the only question that matters.
Findings arrive as work
Outside and inside
External scanning of every address your client exposes to the internet, and internal scanning of the networks behind them. Two views of the same organization, in one product family.
Nothing new to install
Internal scanning is a capability of the universal agent and the appliance you already deployed, enabled per organization. No second rollout, no new credentials to store, no extra attack surface bolted on to look for attack surface.
One queue, grouped by root cause
Findings land in the same alert queue as backup exceptions, with severity, owner, and lifecycle. High-volume classes group into their root cause before they page anyone. Your operators keep one to-do list.
Straight into your PSA
Create or link a ticket on any finding, routed by type to the right board in ConnectWise or CommandIT. Same lifecycle as every other alert. Remediation is tracked where your business already tracks work.
Coverage you can defend
Every discovered asset is scanned or is a deliberate, counted exclusion with a stated reason. There is no silent gap between what exists on the network and what was checked.
Evidence-grade reporting
Results land in the same reports surface as backup evidence: customer-ready, consistent, and exportable for a security questionnaire.
Two scan surfaces, one operating model
| Scan surface | What it examines | How it runs |
|---|---|---|
| External attack surface |
| From outside the network, per exposed address, on your schedule |
| Internal networks |
| Through the universal agent and the appliance already deployed at the site |
| Canonical devices |
| One device, many products, one page in the console |
Findings arrive where your team already works
Same queue, same lifecycle, same ticketing as a failed backup. There is no second inbox.
Three steps to managed exposure
Enable
Turn scanning on per organization. External targets take an address; internal scanning uses the agent and appliance already there.
Triage
Findings group by root cause into the shared queue. Assign, ticket, and resolve with the same grammar as every other alert.
Report
Send the client a report that states coverage, findings, and what changed since last time, from the same surface as their backup evidence.
Exposure is a business risk you already carry
When a client is breached through something visible from the internet, the conversation is about whether their provider was watching. Scan inside the platform and you can show that you were, in the same report they already read every month.
Be first in line
Vulnerability Scanning is coming soon. Tell us what you expose and we will tell you when.