Docs · Tools
Security Score
Not everyone reads a vulnerability table. Security Score distills your findings into one number from 0 to 100 — so a founder, a manager or a client can understand your posture at a glance, and watch it climb as you fix things.
- Category
- Analysis
- Powered by
weighted scoring model- Edition
- Free
- Where
- Desktop → Security Score tab
What it does
Security Score reads the results already in your Nexus history and blends them into a single posture number. It is computed from five factors, each contributing to the total:
- Network exposure — how many services are reachable, and how risky they are.
- Vulnerability — open CVEs and their severity.
- SSL / TLS — certificate and protocol/cipher health.
- Password policy — weak or default credential findings.
- Hardening — firewall, SSH and system-config posture.
How to use it
1
Gather findings first
Run the relevant tools — a port scan, an SSL audit, a vulnerability scan, a defense audit — so each factor has data to score.
2
Open Security Score
The module reads your latest results and shows the overall score plus a breakdown per factor.
3
Fix and re-check
Work the lowest factor first, re-run that tool, and watch the number move.
What you get
One headline number (0–100) and a per-factor breakdown so you know whereto spend effort next. The Fleet manager computes the same kind of posture across a whole fleet — see the dashboard's posture bar in /docs/dashboard.
Tips
- Treat the lowest factor as your next task — it moves the total the most.
- Use it alongside Scan Diff to prove the score improved after a change.
A number people act on. A 0–100 score is the simplest way to align a non-technical stakeholder with the security work that needs doing — and to celebrate progress as it climbs.