Reading your report
The scan report has several sections. Here is how to read them.
Security health score
A score from 0 to 100 that summarizes the overall security posture of the machine:
- 80-100 (green) — Healthy
- 50-79 (amber) — Needs attention
- Below 50 (red) — Critical
The score is compared to the previous scan when available, showing improvement or regression.
Posture strip
A quick summary bar at the top showing:
| Metric | What it means |
|---|---|
| OS | Distribution and version |
| EOL date | When the OS reaches end of life |
| Support status | Maintained or deprecated |
| Firewall | Active or inactive |
| Security updates | Number of pending patches |
| Backup | Last detected backup timestamp |
What to fix first (prioritized risks)
The most important section. Risks are sorted by priority:
- P0 — Fix immediately (critical security gap)
- P1 — Fix soon (high-risk exposure)
- P2 — Plan to fix (medium risk)
- P3 — Informational (low risk, optional hardening)
Each risk includes an estimated remediation time and a summary of the issue.
System audit
Detailed findings grouped by security domain (SSH, firewall, packages, disk, etc.). Each section includes:
- Severity level (critical, warning, suggestion, ok)
- Finding description
- Remediation commands you can copy-paste
- Verification commands to confirm the fix
Services audit
Per-service analysis for detected infrastructure software (PostgreSQL, MySQL, Nginx, Apache, Docker, Postfix). Each service card shows:
- Version and running state
- Issue count by severity
- Specific issues with copy-paste fixes
Network exposure
A table of all listening ports with:
- Bind scope (localhost, LAN, WAN)
- Firewall rule status
- WAN probe results (is the port actually reachable from the internet?)
Hosted apps
Container workloads detected on the host:
- Docker containers with image age, restart count, and security flags
- Kubernetes pods (when kubelet is present)