Security Dashboard
Real-time monitoring and security analytics
Breach sources: 4 of 5 answered. This is a partial view.
One source could not be reached, so an empty result below does not mean clean.
- haveibeenpwned answered 3 records
- dehashed answered 0 records
- leakcheck answered 1 record
- intelx failed timed out after 10s
- breachdirectory answered 0 records
Recent Scans
3 CompleteActive Alerts
12 ActiveThreat Distribution
Security score: 87 of 100
How the score is made up, worst first.
- Patch compliance72 / 100
- Access control81 / 100
- Network security88 / 100
- Data protection93 / 100
- Incident response95 / 100
In the full version each line opens the findings behind it, with the fix ranked by how much it moves the score.
12 active threats
Grouped by what they affect.
- Exposed services3
- Outdated certificates2
- Weak credentials4
- Unpatched software2
- Suspicious logins1
In the full version this is your live list, and each threat opens the evidence and the steps to close it.
Tools online: 8 of 9
What is collecting data right now.
- Nmap scanneronline
- Nuclei templatesonline
- Breach databasesonline
- Log collectoronline
- Dark web monitoroffline since 09:14
One collector is down, so results below may be incomplete. The full version alerts you when a source stops answering.
Last scan: 2 minutes ago
What the most recent run covered.
- Hosts checked42
- Ports checked1,024
- New findings3
- Duration4m 12s
- Next scheduled runin 58 minutes
In the full version you set the schedule, and every run keeps its own record so you can compare.
Full network scan
Completed 2 minutes ago.
- Hosts scanned42
- Open ports found18
- New findings3
- ToolNmap
In the full version this opens the host-by-host results and lets you export them.
Vulnerability assessment
Completed 15 minutes ago.
- Templates run1,842
- Findings11
- Critical1
- ToolNuclei
In the full version each finding links to the CVE, the affected asset, and the fix.
SSL certificate check
Running now.
- Certificates checked6 of 9
- Expiring within 30 days1
- Already expired0
In the full version you get a warning before a certificate expires, not after.
Critical: exposed SSH port
192.168.1.45, port 22, open to the internet.
- First seen2 minutes ago
- Assetbuild-server-01
- Exposurepublic
- Suggested fixRestrict to VPN
In the full version you can close this from here, or send it to whoever manages the asset.
High: outdated SSL certificate
api.example.com is serving an expired certificate.
- Expired6 days ago
- IssuerLet's Encrypt
- AffectsAPI clients
- Suggested fixRenew and automate
In the full version renewal reminders go out 30, 14 and 7 days ahead.
Medium: weak password policy
Active Directory allows 8 character passwords with no lockout.
- Accounts affected64
- Admin accounts4
- Lockoutnot set
- Suggested fix14 characters, lockout after 5 tries
In the full version this is checked every day and tells you when it drifts back.
Vulnerability Scan Results
Last scan: today at 2:30 PM
Vulnerability Details
| CVE ID | Severity | Affected Host | Description | Status |
|---|---|---|---|---|
CVE-2024-1234 | Critical | 192.168.1.45 | Remote Code Execution in OpenSSH | Open |
CVE-2024-5678 | Critical | 192.168.1.100 | SQL Injection in Web Application | In Progress |
CVE-2024-9012 | High | api.example.com | SSL/TLS Certificate Expired | Open |
CVE-2024-3456 | High | 192.168.1.50 | Directory Traversal Vulnerability | Resolved |
CVE-2024-7890 | Medium | mail.example.com | Information Disclosure via Headers | Open |
47 findings
Everything the last run turned up, worst first.
- Critical3
- High12
- Medium21
- Low11
In the full version each count opens its list, and closing one updates the score straight away.
3 critical findings
The ones worth stopping to fix.
- Exposed SSHbuild-server-01
- Outdated OpenSSHtwo hosts
- Database reachabledb-01 on port 3306
Critical here means reachable from the internet and known to be exploited, not just a high score.
12 high findings
Fix these next, in this order.
- Missing patches5
- Weak TLS settings3
- Default credentials2
- Open management ports2
The full version ranks these by how much each fix moves your score.
156 hosts checked
What the scan covered.
- Servers38
- Workstations96
- Network devices14
- Cloud instances8
- Unreachable0
Anything the scanner could not reach is listed too, so a gap never looks like a clean result.
24 subdomains found
Names pointing at your systems, including ones you may have forgotten.
- In use18
- Parked or idle4
- Pointing nowhere2
- Found this week1
Forgotten subdomains are a common way in. The full version tells you when a new one appears.
156 open ports
What answers when the internet knocks.
- Expected139
- Unexpected14
- Newly opened3
Expected means you told us it should be open. Everything else is worth a look.
8 exposed services
Software answering from the open internet.
- Web servers4
- Mail1
- Remote access2
- Database1
A database answering the internet is almost never intended. That one is flagged critical.
3 critical findings
From the attack surface, not the credentialed scan.
- SSH open to the worldport 22
- MySQL reachableport 3306
- FTP still runningport 21
These are visible to anyone scanning the internet, which is why they rank above internal issues.
api.example.com
In use, and the busiest name you own.
- Points toyour API server
- Certificatevalid, 46 days left
- Open ports443 only
- Last change3 weeks ago
This one is configured the way we would want them all to be.
mail.example.com
In use.
- Points toyour mail provider
- SPFset
- DKIMset
- DMARCmissing
DMARC missing means someone can send email that looks like it came from you.
dev.example.com
Reachable from the internet, which it probably should not be.
- Points toa development box
- Login pagepublic
- Last deploy4 months ago
- Suggested fixrestrict to VPN
Old development sites are a favourite way in, because nobody patches them.
staging.example.com
Reachable, and a copy of production.
- Points toa staging copy
- Datamay mirror live
- Accesspublic
- Suggested fixpassword or VPN
If staging holds a copy of real data, it deserves the same protection as production.
SSH on port 22
Open to the whole internet.
- Seen onbuild-server-01
- VersionOpenSSH, outdated
- Login attempts today1,400
- Suggested fixrestrict to VPN
Those login attempts are automated. They are why this ranks first.
MySQL on port 3306
A database answering the internet.
- Seen ondb-01
- Accesspassword only
- Encryptionnot enforced
- Suggested fixclose the port
Databases should be reachable from your own systems, not from anywhere.
HTTPS on port 443
Expected, and configured correctly.
- Certificatevalid
- Expiresin 46 days
- Protocolmodern only
- Renewalautomatic
Shown so the list reflects what is right as well as what is wrong.
FTP on port 21
Still running, and sending passwords in the clear.
- Seen onlegacy-01
- Encryptionnone
- Last usedunknown
- Suggested fixswitch to SFTP or turn it off
FTP predates the modern internet. If nothing needs it, turning it off is the fix.
Network security
How this part of the score is made up.
- Open to the internet8 services
- Segmentedpartly
- Firewall rules reviewed4 months ago
- Score88 of 100
The full version links each line to the findings behind it.
Vulnerability management
How quickly known problems get fixed.
- Findings open47
- Older than 30 days9
- Average time to fix11 days
- Score72 of 100
This is the weakest part of the score, which is why patching leads the recommendations.
Access control
Who can get in, and how.
- Admin accounts4
- Without two-factor1
- Dormant accounts3
- Score81 of 100
One admin without two-factor is worth more attention than most of the patching.
Encryption
What is protected in transit and at rest.
- Sites on HTTPSall
- Certificates validall
- Database encryptionnot enforced
- Score93 of 100
The gap here is the database, which ties back to the exposed port.
Restrict SSH access
The first thing we would do.
- Effortabout an hour
- Downtimenone
- Closes1 critical finding
- Score changeplus 6
In the full version this becomes a ticket with the exact firewall change written out.
Upgrade OpenSSH
Second, once access is restricted.
- Hosts affected2
- Effortabout two hours
- Downtimea short restart
- Score changeplus 3
Doing this after the firewall change means you are not exposed while you work.
Segment the database
Third, and the one that needs planning.
- Changedatabase reachable only from the app
- Efforthalf a day
- Downtimea short window
- Score changeplus 5
This is the fix most often put off, and the one an attacker most often uses.
Renew the SSL certificate
Fourth, and it has a deadline.
- Expiresin 46 days
- Effortminutes
- Downtimenone
- If missedbrowsers warn every visitor
The full version reminds you at 30, 14 and 7 days rather than on the day.
Critical: SSH exposure
Why this was raised.
- Seenport 22 open to the internet
- Attempts today1,400
- Softwareoutdated
- Confidencehigh
Raised from what the scan saw, not from a guess about your setup.
Pattern: lateral movement risk
Why this was raised.
- Shared credentialsacross 3 hosts
- Network segmentationpartial
- If one host fallsothers are reachable
- Confidencemedium
A pattern across findings, not a single alert. Verify before acting on it.
Compliance: certificate expiry
Why this was raised.
- Certificateapi.example.com
- Expiresin 46 days
- Renewalmanual today
- Confidencehigh
Dated facts like this are the easiest to act on and the easiest to forget.
Attack Surface Analysis
External asset discovery and reconnaissance
Discovered Subdomains
Exposed Services
AI Security Analysis
Claude-powered threat correlation and recommendations