Scan Lab
The Scan Lab provides granular control over professional security scanning tools. Unlike the free CyberDoc health check (which runs automated breach, social, and browser checks), the Scan Lab lets you pick individual tools, target specific hosts, and generate detailed reports.
Available Tools
The Scan Lab offers all 17 server-side scanning tools as individually selectable options:
| # | Tool | Description | Typical Duration |
|---|---|---|---|
| 1 | nmap | Port scanning and service detection | 30-120s |
| 2 | nuclei | Template-based vulnerability scanning | 60-180s |
| 3 | nikto | Web server misconfiguration scanning | 30-90s |
| 4 | testssl | TLS/SSL configuration analysis | 20-60s |
| 5 | httpx | HTTP probing and tech detection | 5-15s |
| 6 | ffuf | Directory and file fuzzing | 30-120s |
| 7 | dig | DNS record enumeration | 5-10s |
| 8 | subfinder | Subdomain discovery | 10-30s |
| 9 | whois | Domain registration lookup | 3-8s |
| 10 | origin-bypass | Origin IP detection behind CDN/WAF | 15-45s |
| 11 | headers-check | Security headers verification | 3-8s |
| 12 | tech-detect | Technology stack fingerprinting | 5-15s |
| 13 | waf | WAF detection (14 vendors) and bypass testing (10 techniques) | 20-60s |
| 14 | webapp | Web app vulnerabilities (14 OWASP checks) | 30-90s |
| 15 | owasp | OWASP extended (CORS, SSRF, subdomain takeover, rate limiting) | 20-60s |
| 16 | api | API security (OWASP API Top 10) | 15-45s |
| 17 | ai | AI/LLM security (OWASP LLM Top 10) | 15-45s |
How to Use
Step 1: Enter Target
Type or paste the target domain or IP address. The input accepts:
- Domain names:
example.com - Subdomains:
staging.example.com - IP addresses:
203.0.113.42 - URLs (domain is extracted):
https://example.com/path
Step 2: Select Tools
Check the tools you want to run. Quick-select buttons are provided:
- All — Select all 17 tools
- Quick — Select fast tools only (httpx, dig, whois, headers-check, tech-detect)
- Recon — Select reconnaissance tools (dig, subfinder, whois, httpx, tech-detect)
- Vuln — Select vulnerability scanners (nmap, nuclei, nikto, testssl, waf, webapp, owasp)
- AppSec — Select application security tools (webapp, owasp, api, ai, waf)
- None — Deselect all
Step 3: Run Scan
Click "Run Scan" to dispatch the selected tools to the AWS scanner. Each tool runs and returns results independently. The UI shows real-time progress:
- Tool name with status indicator (pending, running, complete, error)
- Duration counter for the running tool
- Results appear inline as each tool completes
- Overall progress bar
Step 4: Review Results
Results are displayed in collapsible panels, one per tool. Each panel shows:
- Tool name and execution time
- Severity-rated findings (parsed from raw output)
- Raw output (expandable, syntax-highlighted)
- Finding count by severity
Step 5: Save & Act
After reviewing results, you can:
- Save to Lab History — Persists results in the
LAB_SCANSKV namespace (90-day TTL) - Create Ticket — Create a support ticket from any specific finding
- Export — Download results as JSON
- Re-run — Run the same tools again (useful after remediation)
Origin Testing
A key Scan Lab workflow is testing exposed origin servers. When a standard deep scan discovers an origin IP behind a CDN or WAF:
- The scan detail page flags the origin IP discovery as a finding
- Click "Run Targeted Scan" which opens the Scan Lab with the origin IP pre-filled
- The "Vuln" quick-select button is pre-checked (nmap, nuclei, nikto, testssl)
- Results show what is exposed on the unprotected origin — often significantly more than what the CDN reveals
Lab History
The Lab History section shows all saved scan lab runs. Each entry displays:
| Field | Description |
|---|---|
| Lab Scan ID | Unique identifier for the lab run |
| Target | Domain or IP that was scanned |
| Tools Used | List of tools that were executed |
| Findings | Count by severity (e.g., 2 critical, 5 high, 3 medium) |
| Duration | Total scan duration |
| Timestamp | When the scan was initiated |
| Linked Scan | Link to the originating CyberDoc scan (if applicable) |
Lab history supports searching by target domain/IP and filtering by date range.
See the API Reference for endpoint documentation and the Pricing page for plan details.