Attack surface and vulnerability management

Every attack surface.
Proven, not presumed.

RECON maps what is exposed to the internet, what runs inside your network and Active Directory, and how your cloud accounts are configured. External and internal findings are tested against the target before they reach your list, so your team works on what is real.

  • 3 free scans included
  • No credit card required
  • Reports in English, Italian and Spanish
recon.orizon.one

How it works: discover, verify, act

The same three steps on every surface, from the first scan to the fix.

  1. Discover

    RECON finds every asset on the surface you choose: domains and services from outside, hosts and identities through the probe inside, resources and permissions through the cloud connectors.

  2. Verify

    External and internal findings are tested against the target, with evidence. Each one ends up Proven, To verify or Closed, so false positives drop out before anyone opens a ticket.

  3. Act

    The Risk Score sets the priority, the executive brief turns it into a 7/30/90-day plan, and tickets and alerts land in Jira, ServiceNow, Slack or your SIEM.

Verified, not just detected

Matching software versions to CVEs produces long lists. RECON adds a verification step after discovery and tells you which findings are real.

  • Proven

    Confirmed on the target from the scan’s own isolated server, with the evidence of every check attached.

  • To verify

    The test could not decide either way. It stays open and is flagged for a person to check by hand.

  • Closed

    A false positive the test disproved, or a finding excluded from the count. It no longer weighs on the Risk Score.

A Risk Score built on what was proven

The Risk Score counts what verification proved, plus what the verification found in addition. Every scan gets one, even when it only has low or informational findings, and the score before verification stays on screen so you can see how much noise was removed.

  • Tests run from the scan’s own isolated server and keep the evidence of every test
  • Sensitive checks run last and stop at the server’s first reaction
  • Revalidate, Re-check and Verify fix are queued for the next scan
  • Proven vulnerabilities appear on the scan timeline, with the change from the previous scan
recon.orizon.one
Risk Assessment
Medium Risk

How it is calculated · Verification details

Critical1provenof 2 possible
High2provenof 3 possible
Medium4provenof 5 possible
Low2provenof 2 possible

Also 1 proven header-hygiene issues, counted apart from vulnerabilities.

Exploitability · among the proven vulnerabilities
0Exploitable nowreproduced with a minimal, harmless proof
1Actively exploitedCISA KEV catalog
2Attack likely≥ 50% chance of attack within 30 days (EPSS)
1Used by ransomwareCISA KEV catalog, ransomware use

Reports for the team, the board and the auditor

Every report uses the verified results and the same Risk Score you see in the app.

Interactive HTML report
The technical report with the same overview, charts, maps, attack paths and detail drawers as the app, in English, Italian or Spanish.
Executive brief
For management: the decisions to take, the main business risks, how an attacker would get in, a 7/30/90-day plan with residual risk, and NIS2.
Full PDF
A complete PDF for the file. Internal scans add an Active Directory section and a summary page of verified results.
CSV export
A ZIP with one CSV per data set and a guide to every column, ready for a spreadsheet or your BI tool.
Signed and verifiable
HTML reports carry a digital signature. Anyone can check a copy on the public verification page; the file is hashed in the browser and never uploaded.
Share links that expire
Send a report as a link that expires after the days you choose and can be revoked at any time. Every open is logged.

NIS2 Article 21, across all three surfaces

No scanner proves compliance on its own. RECON gives you technical evidence for the Article 21 measures each surface can actually observe, and says clearly where it cannot.

  • Does NIS2 apply, and what shows from outside

    Classifies your company as an Essential Entity, an Important Entity or not applicable and shows the criteria behind it. What the scan finds on email authentication, TLS, exposed services and proven vulnerabilities is technical evidence for the Article 21 measures.

    Evidence from

    • SPF, DKIM, DMARC
    • TLS and certificates
    • Exposed services
    • Proven vulnerabilities
  • 25 Article 21 controls inside the network

    Evaluates 25 controls from what the probe observes. Each one is marked Pass, Warn, Fail or Not assessed, with the affected assets listed.

    Evidence from

    • Asset inventory coverage
    • End-of-life systems
    • SMB signing, RDP NLA
    • LDAP encryption
    • Segmentation
    • MFA and backup indicators
  • Cloud findings mapped to Article 21(2)

    Projects cloud findings onto the ten Article 21(2) measures, (a) to (j), alongside the other frameworks you report against.

    Also mapped to

    • ISO 27001:2022
    • SOC 2
    • CIS Controls v8
    • CSA CCM v4
    • HIPAA
    • FedRAMP Moderate

What no scan can cover

Incident handling procedures, business continuity plans and staff training are governance measures. They need your own policies and records; RECON marks them as not assessed instead of guessing.

Into the tools your team already uses

Send results where work happens, or build on RECON through the public API.

  • JiraTicketing

    Creates an issue in the project you choose when a critical event fires.

  • ServiceNowTicketing

    Opens an incident in the ServiceNow table you configure.

  • SplunkSIEM

    Sends structured events to your HTTP Event Collector.

  • Microsoft SentinelSIEM

    Writes events to your Log Analytics workspace.

  • SlackChat

    Posts scan results to a channel through an incoming webhook.

  • Email digestEmail

    A compact one-screen summary sent to the address you choose.

  • WebhookAny endpoint

    JSON signed with HMAC-SHA256, with a rotatable secret and redelivery.

  • REST APIVersion 1, OpenAPI

    Scans, findings, assets and technologies, plus report download and share links.

RECON and Fireline: continuous and in depth

RECON shows continuously what is exposed and proven. Fireline goes deep on a fixed scope. Together they cover both, instead of a patchwork of separate tools.

What you needOrizon RECON (continuous)Orizon Fireline (autonomous pentest)Separate tools and spreadsheets
The question it answersWhat is exposed and proven, all the timeHow far an attacker gets on the authorised external scopeA different answer per tool
When it runsOn a schedule, daily to quarterlyOn demand, one test at a timeWhenever someone runs it
ScopeExternal, internal and cloud surfacesThe external targets imported from a RECON scanOne surface per tool
DepthEach finding verified against the target, with evidenceAn engine chains weaknesses and proves impact; an independent validator re-checks every findingLists of detections to triage by hand
Compliance mappingNIS2 Article 21 on every surfaceNIS2, DORA, ISO 27001, NIST CSF 2.0, OWASP Top 10 and PCI DSS 4.0, without claiming complianceMapped by hand
ReportsSigned HTML report, executive brief, PDF, CSVTechnical, executive, remediation-plan and compliance reports, in six languagesExports in different formats
Change over timeChanges since the previous scanRetest of selected findings from an earlier runCompared by hand

Start with RECON to see and verify your exposure, then book Fireline for depth where it matters. See Fireline

Questions about RECON

Attack surface management, verification, the probe, the cloud connectors and NIS2.

RECON is an attack surface and vulnerability management platform. It covers three surfaces in one account: what is exposed to the internet (External), what lives inside your network and Active Directory (Internal, through an on-prem probe) and how your cloud and SaaS accounts are configured (Cloud). Results come with a Risk Score, reports and integrations.
EASM is the continuous discovery and assessment of everything an organisation exposes to the internet: domains, subdomains, IP addresses, open ports, web applications and the software versions behind them. The goal is to see your perimeter the way an attacker does, including assets you forgot, and to fix the weaknesses that matter before someone uses them.
They answer different questions. RECON runs on a schedule, from daily to quarterly, across every surface you connect, and verifies its findings automatically, so you always know what is exposed and proven. Fireline, Orizon’s autonomous external penetration test, starts from a RECON external scan, chains weaknesses on the authorised scope to prove impact, has an independent validator re-check every finding and maps them to NIS2, DORA, ISO 27001, NIST CSF 2.0, OWASP Top 10 and PCI DSS 4.0. Use RECON continuously and Fireline when you need impact proven.
After discovery, RECON tests each external and internal finding against the target and keeps the evidence of every test. A finding ends up Proven (confirmed on the target, with the evidence), To verify (the test could not decide, so a person checks it) or Closed (a false positive or an excluded item). Your list then holds what is real, not every version match.
The Risk Score is a 0 to 10 figure for a scan. On verified scans it counts what verification proved, plus what verification found in addition, so it reflects real exposure rather than raw detections. The score before verification stays visible next to it. Every scan gets one, including scans with only low or informational findings.
No. The Scout probe is a Linux service that you install with one command. It connects out to RECON, sends a heartbeat and asks for scan commands, so you do not open inbound ports. It runs on x86_64 and arm64, and several probes can work together on one scan.
Through read-only access that you grant and can revoke: for example a read-only role with an external ID on AWS, read-only Microsoft Graph permissions for Microsoft 365, or a read-only kubeconfig for Kubernetes. RECON reads configuration; it does not change your resources.
RECON is built to avoid it. The most sensitive checks run last and stop at the first reaction from the server, scans leave from fresh egress IP addresses, and a server that stops answering is reported instead of being retried for hours. When a WAF or bot challenge answers, RECON detects it and flags it in the results.
No tool can do that on its own. RECON gives you technical evidence for the Article 21 measures each surface can observe, tells you whether NIS2 is likely to apply to your company, and marks what it cannot assess. Governance measures such as incident handling, business continuity and training still need your own policies and records.
The HTML technical report, the executive brief and the NIS2 analysis are available in English, Italian and Spanish.

See what an attacker sees

Run your first external scans free, with no credit card. For the internal probe and the cloud connectors, book a demo and we will walk you through the setup.