A second opinion
Validate your assumptions and uncover what existing processes may overlook.
For security teams
Get an independent view of your external exposure, validate what matters, and uncover what existing processes may be missing.
External review only · Nothing to install · No active testing without your approval
Outdated software with flaws attackers already use, so you patch those first.
A known flaw in a VPN server, flagged as used by attackers, with the deadline to fix it
| CVE | Product | Asset | Ports | CVSS | Sev | Tier | Published |
|---|---|---|---|---|---|---|---|
| KEV | fortios7.2.5 | vpn.example.com | 443 | 9.8 | C | T2 | 9 Feb 2024 |
| KEV | jenkins2.426.1 | ci.example.com | 443 | 9.8 | C | T2 | 24 Jan 2024 |
| KEV | tomcat9.0.65 | api.example.com | 443 | 9.8 | C | T2 | 10 Mar 2025 |
| fortios7.2.5 | vpn.example.com | 443 | 9.8 | C | T2 | 12 Mar 2024 | |
| php8.3.24 | www.example.com | 80443 | 9.8 | C | T2 | 21 Oct 2026 | |
| php8.3.24 | www.example.com | 80443 | 8.1 | H | T2 | 21 Oct 2026 | |
| http_server2.4.54 | www.example.com | 80443 | 9.8 | C | T2 | 1 Jul 2024 | |
| http_server2.4.54 | www.example.com | 80443 | 9.8 | C | T2 | 7 Mar 2023 | |
| openssh8.9p1 | www.example.com | 22 | 8.1 | H | T2 | 1 Jul 2024 | |
| openssh9.2p1 | 192.0.2.25 | 22 | 8.1 | H | T2 | 1 Jul 2024 |
CVE-2024-21762CWE-787
vpn.example.com
vpn.example.com
Product and asset
External sources
NVD · CVE-2024-21762
CISA KEV ransomware
Used in ransomware campaigns. Active exploitation — must be resolved as soon as possible.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
An issue: priority P1, critical severity, a deadline, a technical description and a fix recommendation
| Prio. | Finding | Asset | EPSS | CVSS | Sev | Confidence | CVE | Checked |
|---|---|---|---|---|---|---|---|---|
| P1 | www.example.com | — | 9.8 | C | T2 | CVE-2026-109618 | 8 Nov 2026 | |
| P1 | lk.example.com | — | 9.8 | C | T1✓ | — | 8 Nov 2026 | |
| P1 | 192.0.2.25 | — | — | C | T1 | — | 8 Nov 2026 | |
| P2 | example.com | — | — | C | T2 | — | 8 Nov 2026 | |
| P2 | www.example.com | — | — | H | T1 | — | 8 Nov 2026 | |
| P1 | vpn.example.com | 83.4% | 9.8 | C | T2 | CVE-2024-21762 | 8 Nov 2026 | |
| P2 | 192.0.2.25 | — | — | H | T3 | — | 8 Nov 2026 | |
| P2 | cdn.example.com | — | 8.1 | H | T2 | — | 8 Nov 2026 | |
| P2 | www.example.com | — | 7.5 | H | T1 | — | 8 Nov 2026 | |
| P2 | shop.example.com | — | 7.5 | H | T1✓ | — | 8 Nov 2026 | |
| P2 | www.example.com | — | 7.5 | H | T1 | — | 8 Nov 2026 | |
| P2 | 192.0.2.25 | — | — | H | T2 | — | 8 Nov 2026 | |
| P2 | 192.0.2.21 | — | — | H | T2 | — | 8 Nov 2026 | |
| P3 | 192.0.2.21:9090 | — | — | M | T2 | — | 8 Nov 2026 | |
| P3 | example.com | — | — | M | T1 | — | 8 Nov 2026 |
Dangerous exposure catalogSW-EXT-EXPOSURE-11
Dangerous exposure: MySQL database (3306)
192.0.2.25
192.0.2.25
Description
The MySQL server answers on port 3306 from the internet. Anyone can try passwords against it, and any flaw in the server is reachable directly.
Recommendations
Close port 3306 on the perimeter. If remote access is needed, allow it only from known addresses or through the VPN.
A server card: risk score, open ports, linked domains and the first thing to fix
| Asset | Risk | Issues | Ports | Technologies | OS | |
|---|---|---|---|---|---|---|
| 9.6 | 11 | 443 | FortiOS | FortiOS 7.2.5 | ||
| 9.4 | 1 | — | — | — | ||
| 9.3 | 22 | 223306920010250 | MySQLElasticsearchOpenSSH+1 | Debian 12 | ||
| 9.1 | 13 | — | — | — | ||
| 8.9 | 2412 | 2280443 | Apache HTTP ServernginxOpenSSH+6 | Ubuntu Linux 22.04 | ||
| lk.example.com | ||||||
| shop.example.com | ||||||
| www.example.com | ||||||
| 8.8 | 1 | — | — | — | ||
| 8.4 | 21 | 2244390901567227017 | Apache TomcatJenkinsGitLab+6 | Ubuntu Linux 22.04 | ||
| 7.9 | 11 | — | — | — | ||
| 7.8 | 1 | 25443587993 | PostfixDovecotnginx+1 | Ubuntu Linux 20.04 | ||
| 7.6 | 1 | — | — | — | ||
| 7.5 | 1 | — | — | — | ||
| No risk | — | — | — | — | ||
| No risk | — | — | — | — | ||
| No risk | — | — | — | — | ||
| No risk | — | — | — | — | ||
| No risk | — | — | — | — | ||
| 21 | 80443 | — | — | |||
192.0.2.20 IPv4 Available Confirmed
www.example.com
What to close first Ports
Web login forms Elevated importance 80443
Public login forms — enable brute-force protection and MFA.
Domains 3
SeguriScan dashboard: assets, open services, findings by severity, data leaks and the threat level for each category
Dashboard
What needs attention now and how the calculated threat level is distributed across categories.
Threat level by category
compared with 2 Nov 2026Lower is better
Current cycle since 8 Novas of 9 Nov 2026
Needs attention 4 of 40
The reports list: one report per check, downloadable as Word or Excel
Ready perimeter reports — one per check. Each can be downloaded as DOCX or XLSX.
| Report | Check period | Status | |
|---|---|---|---|
| Perimeter report of 8 Nov 2026 | from 8 Nov 2026 | In progress | |
| Perimeter report of 2 Nov 2026For the period · built 2 Nov 2026 · DOCX, XLSX | 1 Nov 2026 — 2 Nov 2026 | Completed | |
| Perimeter report of 26 Oct 2026For the period · built 26 Oct 2026 · DOCX, XLSX | 25 Oct 2026 — 26 Oct 2026 | Completed |
Data leaks: leaked accounts of staff and customers, whether a password leaked too, and where it turned up
Data Leaks 17
access by grant| Account | Password | Source | Sev | Fields | Found |
|---|---|---|---|---|---|
| a.m*****@example.comStealer log · 8 Nov 2026 | yes | Stealer log | C | emailpasswordURL | 8 Nov 2026 |
| j.r****@example.comStealer log · 8 Nov 2026 | yes | Stealer log | C | emailpasswordURL | 8 Nov 2026 |
| s.p*****@example.comCombolist 2026-08 · 31 Oct 2026 | yes | Combolist 2026-08 | H | emailpassword | 31 Oct 2026 |
| d.l****@example.comStealer log · 24 Oct 2026 | yes | Stealer log | H | emailpasswordURL | 24 Oct 2026 |
| it-support@example.com✓travelbook.example breach · 10 Oct 2026 | yes | travelbook.example breach | H | emailpassword hash | 10 Oct 2026 |
| m.g*****@example.comStealer log · 26 Sep 2026 | yes | Stealer log | H | emailpasswordURL | 26 Sep 2026 |
Passwords and hashes are shown masked. Access to full values is enabled for the organization on request.
The real challenge
For most security teams, the hard part is everything that comes after.
“I already know about it — but no one fixes it.”
“IT says it’s not important.”
“They’re afraid to break something in production.”
“I don’t have the arguments to push it through.”
Discovery isn’t the bottleneck. Turning findings into action is.
Why teams choose IntruForce
You also need to explain why they matter, prioritize what deserves attention, and help operational teams move without fear of breaking production.
Validate your assumptions and uncover what existing processes may overlook.
Technology finds the signals. Experts help you interpret them.
Use evidence and context to align IT teams and leadership.
Not every finding deserves immediate attention. We help you separate signal from noise.
How SeguriScan sets priority →Recommendations are practical and designed to minimize operational risk.
Get your time back
Less time proving the problem. More time resolving it.
Why IntruForce
Most organizations don’t struggle because they lack security tools. They struggle because translating findings into decisions requires time, coordination, and expertise.
IntruForce helps teams uncover external risks, prioritize what matters, and drive action across the organization — because security programs succeed when insight turns into action.
What makes IntruForce different
How it works
What you get
Outcomes, not just output — findings you can validate, explain, and act on. The exact scope and what you receive are agreed with you before anything starts.
Unknown assets, exposed services, and unmanaged risks that require attention.
Employee credentials and publicly exposed data linked to your organization.
Evidence to validate severity and explain why specific issues deserve action.
Support interpreting results and discussing remediation options, within the scope agreed with you.
Recommendations your teams can realistically implement without unnecessary disruption.
Clear summaries to support discussions with leadership and operational stakeholders.
The IntruForce difference
We uncover blind spots, validate what matters, help communicate risk, and support turning findings into action — combining an independent view, automation, and expert judgment.
Questions, answered
Because tools are only part of the picture. We help validate assumptions, identify blind spots, and provide an independent perspective on your external exposure.
No. SeguriScan doesn't replace your vulnerability scanner; it works alongside it, adding what is actually reachable, what changed, which new CVEs apply, leaked passwords and fake websites imitating your brand, ranked by what to fix first.
Beyond discovering what is exposed, we add context and help your team turn findings into action.
No. We also identify unknown assets, exposed services, data from leaks, including logs of password-stealing malware, and unmanaged risks.
SeguriScan checks your systems from the outside, during the pilot and afterwards. Any active testing is agreed with you before it runs.
We provide evidence, prioritization, and guidance that help you explain why specific actions matter — and reduce concerns about unnecessary change.
We'll contact you by email to discuss the pilot and agree on the next steps. No obligation to proceed. No active testing without your approval.
That’s exactly why prioritization matters. We help your team focus on what deserves attention first.
Further reading
Get started
Send your domain, work email and an optional asset list to the IntruForce team to request a free pilot.