1. Prove ownership
Before any scan, add each target and prove you own it or are authorized to scan it. Scopes only accept verified targets.
- Domains: add a DNS TXT record, or place a verification file on the web server.
- IP addresses and ranges: confirm in the app that you own or are authorized to scan them.
2. Create a scope
A scope is the set of verified targets a scan covers. In the scope you can also add:
- Credentials, for a credentialed scan. They are used to read, not to change.
- Checkout pages, to turn on checkout page script watch.
- Systems that should be unreachable from the internet, to turn on internet exposure checks.
3. What each scan checks
- External assessment of the internet-facing hosts and services in scope.
- Credentialed assessment of the same scope, when credentials are set.
- Attack-surface discovery on verified domains: subdomains, DNS and email settings, and dangling DNS records.
- Website checks: security headers, cookie flags, risky HTTP methods and exposed sensitive files. Safe checks only: no attack payloads and no requests that change data.
- TLS checks: certificate expiry, legacy protocol versions and HSTS.
- Checkout page script watch: each scan reads the scripts on the pages you listed, checks integrity and content security policy settings, and raises a finding when a script changes or a new one appears.
- Internet exposure checks: a plain connection attempt from our cloud scanner to each listed system. A pass shows the system is unreachable from the internet. It does not test isolation inside your network.
4. How findings are confirmed
Confirmation checks are read-only. We connect, read what your services already show (such as a service banner or the negotiated TLS version), and compare it with what the scan found. No attack payloads, no credential guessing, and no changes.
5. Threat ranking and trends
Each finding is ranked with public threat data: whether the weakness is known to be used in attacks, how likely it is to be used, and whether public attack code exists. Trends show whether your risk is going up or down from scan to scan.
6. Finding workflow
- Dispute: say a finding is wrong and why.
- Accept: record a documented risk. Owners and admins only.
- False positive: mark a finding that does not apply.
- Remediate, then verify: mark it fixed, run a new scan, and close it once the fix is confirmed. Owners and admins verify.
- Reopen: bring a finding back if it returns.
Every decision is kept in the finding's history: who did what, and when.
7. Reports
Each scan produces a written PDF report with scope, findings, PCI DSS 11.3 mapping and advice, plus the ASV-readiness check: ready / not ready. It is a readiness check, not an official ASV attestation.
8. Alerts
- Email: choose which alerts you get in notification settings.
- Webhooks: add a webhook URL, send a test event, or remove it.
9. Team and sign-in
- Roles: owner, admin and member. Seats depend on your plan.
- Two-factor authentication: turn it on in your account settings, then confirm with a code at each sign-in.
Something unclear? Tell us.