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
Three surfaces, one view of your risk
Start with the surface you need and add the others when you are ready. Each has its own scans and reports, all in the same RECON account.
How it works: discover, verify, act
The same three steps on every surface, from the first scan to the fix.
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.
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.
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
How it is calculated · Verification details
Also 1 proven header-hygiene issues, counted apart from vulnerabilities.
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 need | Orizon RECON (continuous) | Orizon Fireline (autonomous pentest) | Separate tools and spreadsheets |
|---|---|---|---|
| The question it answers | What is exposed and proven, all the time | How far an attacker gets on the authorised external scope | A different answer per tool |
| When it runs | On a schedule, daily to quarterly | On demand, one test at a time | Whenever someone runs it |
| Scope | External, internal and cloud surfaces | The external targets imported from a RECON scan | One surface per tool |
| Depth | Each finding verified against the target, with evidence | An engine chains weaknesses and proves impact; an independent validator re-checks every finding | Lists of detections to triage by hand |
| Compliance mapping | NIS2 Article 21 on every surface | NIS2, DORA, ISO 27001, NIST CSF 2.0, OWASP Top 10 and PCI DSS 4.0, without claiming compliance | Mapped by hand |
| Reports | Signed HTML report, executive brief, PDF, CSV | Technical, executive, remediation-plan and compliance reports, in six languages | Exports in different formats |
| Change over time | Changes since the previous scan | Retest of selected findings from an earlier run | Compared 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.
Go deeper
The solutions RECON powers, and the documents behind it.
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.