Skip to main content
Platform · Continuous threat exposure management

The CTEM platform that runs all five stages from outside your network.

ShadowMap runs the five CTEM stages against the estate an attacker reaches first, the part that faces the internet. Scoping starts from an apex domain. Discovery, prioritisation and validation run from outside with no agent and no credentials. Mobilisation ends in a ticket with an owner or a removal.

30–60%
More external assets than the internal inventory held, across first scans
8–15%
Of surfaced exposures validated as exploitable, where safe and authorised
86
Integrations available for mobilisation

Stage by stage

Which ShadowMap capability runs which CTEM stage

Eleven rows, five stages. Each capability links to the page that sets out how it works and where it stops.

CTEM stageShadowMap capabilityWhat it contributes to the stage
1. Scoping Attack Surface Management Scope is built from an apex domain and what the public registration, naming and certificate record places beneath it: subsidiaries, brands and acquired entities. No seed list and no asset inventory is needed.
Across first scans, outside-in discovery typically surfaces 30–60% more external assets than the internal inventory holds.
2. Discovery Data Exposure Monitoring Secrets in public repositories, exposed storage and indexed documents, each attributed to an owner.
2. Discovery Dark Web Monitoring Credentials, cookies and tokens from stealer logs, grouped by the infected machine and matched to the login surface they open.
2. Discovery Brand Protection Impersonation across domains, social platforms and app stores: the exposures that carry your name on infrastructure you do not own.
2. Discovery Third-Party Risk Management The same outside-in discovery run on your vendors, scored with the categories and bands used on your own estate.
3. Prioritisation AI Review Each finding receives one of four published verdicts: Confirmed Exposure, Needs AI Review, Likely False Positive or Benign. Nothing is deleted, and an analyst decision overrides the verdict.
3. Prioritisation Threat Intelligence Actor, malware, CVE and indicator data correlated against the technology discovered on your estate, so a new advisory is ranked by whether you run the thing it names.
3. Prioritisation Security Ratings A score from 0 to 100 with an A–F grade and the arithmetic published, for the board and for comparing a vendor against your own estate.
4. Validation Continuous Automated Red-Teaming Contextual, controlled, non-destructive testing of whether a finding can be used: whether an exposed key is live and what it opens, whether a leaked credential still authenticates.
In practice 8–15% of surfaced exposures validate as exploitable. Validation is bounded to inventory already attributed to you, and a finding that was not tested says so.
5. Mobilisation Integrations Findings route into the queue of the team that fixes them, with the evidence attached. 86 integrations are available, across ticketing, chat, SIEM and cloud.
5. Mobilisation Phishing and Domain Takedown For an exposure on infrastructure you do not own, the action is a removal. Notices are filed on your authorisation through 86 provider relationships across 12 provider types.

1. Scoping

ShadowMap capability
Attack Surface Management
What it contributes to the stage
Scope is built from an apex domain and what the public registration, naming and certificate record places beneath it: subsidiaries, brands and acquired entities. No seed list and no asset inventory is needed.

Across first scans, outside-in discovery typically surfaces 30–60% more external assets than the internal inventory holds.

2. Discovery

ShadowMap capability
Data Exposure Monitoring
What it contributes to the stage
Secrets in public repositories, exposed storage and indexed documents, each attributed to an owner.

2. Discovery

ShadowMap capability
Dark Web Monitoring
What it contributes to the stage
Credentials, cookies and tokens from stealer logs, grouped by the infected machine and matched to the login surface they open.

2. Discovery

ShadowMap capability
Brand Protection
What it contributes to the stage
Impersonation across domains, social platforms and app stores: the exposures that carry your name on infrastructure you do not own.

2. Discovery

ShadowMap capability
Third-Party Risk Management
What it contributes to the stage
The same outside-in discovery run on your vendors, scored with the categories and bands used on your own estate.

3. Prioritisation

ShadowMap capability
AI Review
What it contributes to the stage
Each finding receives one of four published verdicts: Confirmed Exposure, Needs AI Review, Likely False Positive or Benign. Nothing is deleted, and an analyst decision overrides the verdict.

3. Prioritisation

ShadowMap capability
Threat Intelligence
What it contributes to the stage
Actor, malware, CVE and indicator data correlated against the technology discovered on your estate, so a new advisory is ranked by whether you run the thing it names.

3. Prioritisation

ShadowMap capability
Security Ratings
What it contributes to the stage
A score from 0 to 100 with an A–F grade and the arithmetic published, for the board and for comparing a vendor against your own estate.

4. Validation

ShadowMap capability
Continuous Automated Red-Teaming
What it contributes to the stage
Contextual, controlled, non-destructive testing of whether a finding can be used: whether an exposed key is live and what it opens, whether a leaked credential still authenticates.

In practice 8–15% of surfaced exposures validate as exploitable. Validation is bounded to inventory already attributed to you, and a finding that was not tested says so.

5. Mobilisation

ShadowMap capability
Integrations
What it contributes to the stage
Findings route into the queue of the team that fixes them, with the evidence attached. 86 integrations are available, across ticketing, chat, SIEM and cloud.

5. Mobilisation

ShadowMap capability
Phishing and Domain Takedown
What it contributes to the stage
For an exposure on infrastructure you do not own, the action is a removal. Notices are filed on your authorisation through 86 provider relationships across 12 provider types.

One finding, five stages

An exposed key, from scope to closed

An illustration of the path, built from how the capabilities hand over to each other. It is not a customer record.

Scope

The external half, run as one platform

CTEM is a programme with two halves. This is the platform for the one that starts outside your network.

Continuous threat exposure management is the five-stage programme framework Gartner introduced in 2022, and it spans internal and external scope. The internal half runs on instrumentation: agents, credentialed scanners and directory data, pointed at an estate the organisation already lists. The external half starts from the position an attacker without a foothold occupies. ShadowMap is built for that half. It runs every stage from outside, on the estate the inventory does not hold as well as the estate it does, and validation is part of the same licence. A buyer assembling a CTEM stack needs both halves to meet in one prioritisation queue. ShadowMap’s findings reach that queue through its integrations and its API, with the verdict, the score and the validation state attached, so an external exposure and an internal one can be ranked against each other.

Sourcing

Where the figures on this page come from

The two percentages and the integration count As of November 2026
  • The 30–60% discovery difference is an aggregate observed across first scans: external assets found by outside-in discovery beyond what the internal inventory listed.
  • The 8–15% validation figure is an aggregate: the share of surfaced exposures that safe, authorised validation confirmed as exploitable.
  • The integration count is read from the published integration catalogue when this page is built, so it is the same number the integrations page shows.
  • The five-stage reading follows the framework as Gartner published it: scope, discover, prioritise, validate, mobilise.

Deliberately excluded

  • No accuracy or false-positive figure.
  • No takedown completion time. Removal depends on the registrar, host or platform that receives the notice.
  • Neither percentage describes a named customer, and neither is a promise about your estate.

Questions buyers ask

Before you shortlist a CTEM platform

Is ShadowMap a CTEM platform?

ShadowMap is the platform for the external half of a CTEM programme. It runs scoping, discovery, prioritisation, validation and mobilisation from outside your network, against the estate that faces the internet. CTEM as a whole also covers internal ground, which runs on agents and credentialed tooling, and the two halves meet in one prioritisation queue.

Which CTEM stage do most programmes lack?

Validation. A discovery tool lists exposures and a scoring tool ranks them, and neither establishes whether one can be used. Continuous Automated Red-Teaming is the ShadowMap capability that tests findings where it is safe and authorised, and full validation is included in the entry licence.

What does ShadowMap need from us to start?

One apex domain. Discovery and enumeration run first. Validation is enabled gradually during onboarding, with the authorisation scope set in the contract and the onboarding configuration. An analyst is assigned for the first 30 days.

How do findings reach the teams that fix them?

Through 86 available integrations, including Slack, Microsoft Teams, PagerDuty, Jira Service Management, ServiceNow and Splunk, and through the API. A finding arrives with its evidence, its verdict and its validation state. An exposure on infrastructure you do not own goes for removal on your authorisation.

See the five stages run against your own domain

Thirty minutes, one apex domain: what scoping returns, what discovery adds to your inventory, and which findings validation would test first.