Skip to main content

ShadowMap Research

Exposure Research · ShadowMap

Attack surface management · Dark web monitoring · Credential exposure · Brand protection · Threat intelligence

ShadowMap Research works from the collection side of the platform: stealer logs, exposed repositories, certificate transparency, actor marketplaces. It writes up what the data shows, not what the category expects. ShadowMap is built by Security Brigade, CERT-In empanelled since 2008.

Articles by ShadowMap Research

What a security rating does and does not tell you

A security rating compresses your external posture into a single letter. Four things the grade structurally cannot see, and how to use it as an index rather than an outcome.

ShadowMap

Source code leaks: what a public repository actually gives an attacker

The code is rarely the fastest thing in a leaked repository. What an attacker actually takes is the endpoints, the secrets and the architecture. Finding those in the noise is the whole job.

ShadowMap

Switching external exposure vendors: the first thirty days

Replacing a digital risk protection or attack surface vendor is a data-migration project, not a procurement one. What to export, what to insist on, and what will look like a regression in week one.

ShadowMap

Digital risk protection is being absorbed. What replaces it?

Search demand for digital risk protection is receding while the problem itself grows. What the category got right, what it never covered, and what replaces it.

ShadowMap

EASM, CAASM, vulnerability management, exposure management: which one do you actually need?

Four acronyms compete for the same budget line, and they are not interchangeable. The difference is architectural, and one question separates them: where does the data actually come from?

ShadowMap

Reconstructing a compromised device from seven artefacts

A password is one row; a device is a story. The seven artefact classes in a stealer log, what each one tells you that the password does not, and the response that follows from each.

ShadowMap

Continuous pentesting, BAS, autonomous pentesting and CART: what actually validates external exposure

Breach and attack simulation, autonomous pentesting, continuous penetration testing and CART all promise proof. What each one validates, and the part of the external surface it cannot see.

ShadowMap

Stealer logs are not combolists, and the difference decides your response

A credential-exposure report shows two identical-looking rows. One is a resold combolist entry worth almost nothing; the other is an infostealer capture from a live device, and an active incident.

ShadowMap

How to scope a fourteen-day external exposure proof of concept

External exposure POCs usually test features that were never in doubt. What fourteen days can settle is whether a platform's picture of your organisation is correct, and how to measure that.

ShadowMap

Prioritising external exposure you cannot patch this quarter

A leaked key, a typosquat, a vendor's weak posture, a credential in someone's browser: none of these has a CVE. Prioritising them needs a different method from vulnerability management.

ShadowMap

Forty thousand leaked credentials, or eight? The number that matters

Credential exposure is not a volume problem. What a stealer log actually contains, how a leaked credential gets tested, and why the handful that still authenticate are the only ones that matter.

ShadowMap

The external half of a CTEM programme

Every published treatment of continuous threat exposure management assumes agents and internal scope. Here is what the five stages look like from the outside, where an attacker actually starts.

ShadowMap