threat-led penetration testing

Test against the attacks relevant to your organisation

Scope red teams and validation around the techniques, controls and at-risk products active against organisations like yours.

The Problem

Pen tests run from a standard playbook that drifts from what real adversaries do. You can pass a test that does not resemble the attack you will face.

Questions this page answers

Which techniques relevant to us are active now?

Which products of ours are most at risk?

Which attacker behaviours should we emulate?

Which controls should detect this activity?

Which groups are exploiting CVEs in our stack?

What evidence supports the test scenario?

How Lupovis helps you test what matters

Scope from relevant tradecraft.

Unlike a fixed methodology, the MITRE Timeline and TTP Browser scope the test from techniques active against organisations like yours.

Target your at-risk products.

Products at Risk ranks your stack by exploitation likelihood and names the groups exploiting CVEs in it, so testing hits the real exposure.

Emulate observed behaviour.

Each technique lists its method and the source IPs performing it, so testers reproduce real tradecraft.

Validate your controls.

Each technique names the controls expected to catch it, and the hunting rules let you confirm whether yours would have.

Data available

Category

Field

Why it matters

Action

Field

TTP protection controls

Why it matters

Shows the common controls that protect against this technique.

Action

Field

TTP exploit method

Why it matters

Shows how to check whether you are vulnerable to this technique.

Attribution

Field

Group Infrastructure links

Why it matters

Shows infrastructure linked to known threat groups.

Attribution

Field

Group name

Why it matters

Gives you a common name for each threat group.

Attribution

Field

Group country

Why it matters

Shows the country the group is linked to.

Attribution

Field

Motivation

Why it matters

Shows why the group has attacked organisations in the past.

Attribution

Field

Sectors observed

Why it matters

Shows which sectors the group is known to target.

Attribution

Field

Countries observed

Why it matters

Shows which countries the group is known to target.

Attribution

Field

TTP IDs linked to the group

Why it matters

Shows the techniques the group has used before, so you can see how it might attack you.

Behaviour

Field

TTP Description

Why it matters

Explains what a technique involves beyond its name or ID.

Behaviour

Field

Kill-chain stage

Why it matters

Shows which stage of an attack the technique is used in.

Behaviour

Field

MITRE ID

Why it matters

Gives you the standard ATT&CK reference for the technique.

Observed signal

Field

CVEs observed

Why it matters

Shows which CVEs this IP address has tried to exploit before.

Observed signal

Field

Behaviour and techniques identified

Why it matters

Shows which techniques this IP address has used before.

Threat detail

Field

Affected product

Why it matters

Shows which product the vulnerability affects.

Threat detail

Field

CPEs

Why it matters

Gives the official product and vendor string used across security tools.

Threat detail

Field

Published date

Why it matters

Shows when the CVE was announced.

Threat detail

Field

CVSS score and level

Why it matters

Shows how severe the vulnerability is on the standard scale.

Threat detail

Field

EPSS score

Why it matters

Shows how likely the vulnerability is to be exploited.

Threat detail

Field

KEV status and date

Why it matters

Shows whether the vulnerability has been exploited in the wild and since when.

Test what is actually coming for you.

Explore other use cases

Stop breaches before they happen

Get a 30-minute walkthrough with the Lupovis team. We'll show you activity already targeting organisations like yours.