Security intelligence platform

Three services. One security platform.

Find what you expose, read the code behind it, and close every finding with evidence a rescan confirms.

Sample data, for illustration.
6
Recon engines orchestrated per scan
4
Compliance frameworks mapped live
100%
Tenant-scoped data and queries
<30 min
From first scan to prioritised findings

One platform that finds what you expose, reads the code behind it, decides what matters, and proves the fix held.

Not a scanner that hands you a list. A loop that starts outside your network, ends at a verified remediation, and leaves an audit trail at every step.

Your perimeter is not where you drew it.

None of this is a failure of the security team. It is what happens when an organisation moves faster than its asset register.

Attackers do not need an inventory. They only need the one asset you forgot.

  • Infrastructure

    Hosts nobody owns

    A subdomain from a campaign that ended. Still resolving, still reachable, still yours in the eyes of an attacker.

  • Identity

    Credentials already traded

    Staff addresses and passwords sitting in breach collections, long before anyone inside notices a login that should not work.

  • Supply chain

    Code you never wrote

    Most of what ships is a dependency of a dependency. Its flaws become yours the moment you build.

One platform, three dedicated services.

EASM
External Attack Surface Management

Continuously discover every internet-facing asset, detect exposures and leaked data, and turn findings into governed, repeatable remediation.

  • Asset discovery and risk grading
  • Exposure and data-leak monitoring
  • Prioritised findings and remediation
  • Attack graph and compliance mapping
Explore EASM
VI
Vulnerability Intelligence

One live feed of every CVE disclosure, ranked by real-world exploitation likelihood, so you know which threats can actually hurt you.

Explore VI
CODE
Secure Code Review

Several analysis engines merged into one corroborated list, with a suggested change written against your file and a way to prove it worked.

Explore CODE
How it works

Four stages, running continuously.

Every service runs the same loop. It starts outside your network and ends at a remediation that has been proven, not promised.

  1. 01

    Discover

    Map every host, certificate, header and exposed service that carries your name, from the public internet, with nothing installed on your estate.

  2. 02

    Analyse

    Read the source and the supply chain behind each asset, and check every component against the public advisory record.

  3. 03

    Prioritise

    Separate the reachable from the theoretical, corroborate across independent engines, and rank by what an attacker can actually use.

  4. 04

    Verify

    Rescan after the change and close the item only when the evidence says it is gone. Nothing is marked fixed by assertion.

Stage four is the one most programmes never reach, and the only one that produces evidence. A finding carries an owner, a deadline and a history. It closes because a later scan can no longer find it, and if it comes back it reopens itself.

Six capability groups, one console.

Every service writes into the same asset model, worklist and audit trail. A certificate, a leaked credential and a vulnerable dependency are all findings against an owner.

Discovery and exposure

EASM

Automated discovery of domains, subdomains, hosts, IPs, ports and cloud footprint, with change detection and a risk grade that trends over time.

  • Subdomain and asset discovery from a domain alone
  • Live service and port enumeration
  • SSL/TLS inventory: issuer, expiry, protocol and grade
  • Security-header scoring with missing-header detail
  • Web reconnaissance of panels, directories and endpoints
  • Risk grade with historical trend and change detection

Leak and identity intelligence

EASM

Exposed secrets, leaked credentials and dark-web mentions tied to your domains, prioritised by real business risk.

  • Corporate identity footprint across public sources
  • Breach exposure matched against known collections
  • Domain-level leak detection, attributed to an owner
  • Access-controlled sensitive values, never shown by default
  • Every view audited, so disclosure is accountable

Vulnerability intelligence

VI

One live feed of every CVE disclosure, merged and de-duplicated, and ranked by exploitation likelihood rather than severity alone.

  • Unified CVE feed, deduplicated across sources
  • Known-exploited catalogue tracking
  • Exploitation-first ranking rather than score alone
  • Proof-of-concept availability, read at request time
  • Ransomware and threat-activity landscape
  • Scheduled digests enriched for your estate

Source code analysis

CODE

Several independent engines merged into one corroborated list, with the data-flow path from input to flaw.

  • Nine risk categories across ten languages and config formats
  • Data-flow analysis: the path from input to the flaw
  • Several engines merged into one corroborated list
  • Run-to-run deltas: new, carried over, no longer raised
  • Paste or drop a file for review without a repository
  • Read-only: nothing is ever written to your code

Supply chain

CODE

Every component, direct and inherited, matched against the public advisory record before a fixed version is recommended.

  • Full dependency graph, direct and inherited
  • Advisory matching per component and version
  • Fixed version confirmed before it is recommended
  • Unpinned dependencies surfaced as their own risk
  • Interactive maps of the estate and of each repository

Governance and reporting

Platform

Board-ready dashboards, an append-only audit trail and control mapping across ISO 27001, NIST CSF, DORA and GDPR, with live evidence from platform activity.

  • Remediation lifecycle from detected to verified
  • Owner assignment by email, accepted from a single-use link
  • Executive and technical reports, plus PDF, CSV and Excel exports
  • Multi-tenant isolation and role-based access
  • Full audit trail of who saw and changed what
  • Self-hosted: your code and findings never leave

A finding is not closed because someone said so.

Every item carries an owner, a deadline and a history. It moves only when the evidence moves it, and if it comes back, it reopens itself.

  1. Detected

    Raised with its location, its severity and why it matters.

  2. Assigned

    Offered to an owner, who accepts it from a single-use link.

  3. Fixing

    Tracked while the change is made, with the clock running.

  4. Rescanned

    The asset is read again at the new commit, not asked about.

  5. Verified

    Closed only because a scan can no longer find it.

Evidence

Reporting an auditor accepts.

The same run produces the board summary and the engineer’s worklist from one dataset, so the two can never disagree.

Point in time

What was true at a given commit, on a given date, with the scope recorded. What was not looked at is stated plainly, because a report that cannot say that is not evidence.

  • Executive report: posture, trend and top risks
  • Technical report: every finding, with its evidence
  • Machine-readable exports for your own pipeline

Change over time

What is new since the last run, what is gone, and what could not be rechecked. They are kept apart because they are three different claims, and only one of them is good news.

  • New, carried over and no longer raised, counted separately
  • Corroboration recorded where engines agree
  • A full audit trail of who saw and changed what

Three commitments.

  1. 01

    Outside-in, always

    The starting point is a domain, not an asset list. The things missing from your inventory are exactly the things it finds first.

  2. 02

    Corroborated, not counted

    Independent engines are merged into one list. Agreement between them raises confidence; volume alone never does.

  3. 03

    Proven, not asserted

    Nothing is closed on a promise. The loop ends at a scan that can no longer find the problem.

Deployed in your environment. Your code and your findings stay inside it.

Questions, answered.

What is External Attack Surface Management?

EASM continuously discovers and monitors every internet-facing asset your organisation exposes (domains, subdomains, IPs, services, cloud footprint) and surfaces the exposures an attacker could exploit, before they do.

How is tenant data kept separate?

Every target list, exposure metric and query is filtered by the current tenant. Data from one client organisation is never visible from another, and that is enforced on every page of the platform.

Which compliance frameworks are supported?

ISO/IEC 27001, NIST CSF 2.0, DORA and GDPR out of the box, with control coverage mapped live to your platform activity and exportable as an evidence report.

How fast can we get value?

Launch a scan and you get a prioritised findings view in minutes. There is no long onboarding and no agent to deploy on external assets.

See the platform on a scenario close to yours.

A 30-minute walkthrough with an attack-surface expert.