SSQ.AISSQ.AI
English
help!

TLPT Threat & Scenario Analysis

From the threats aimed at you to the scenarios your TLPT will test

We build TLPT scenarios that meet the requirements, grounded in the threats that actually target your organisation and the weak points it shows from outside.

We connect our Exposure Intelligence to actual Threat-Led Penetration Testing (TLPT). This is the threat analysis stage of a TLPT. In a TLPT run by SAFE SQUARE it is the first stage; where a framework assigns analysis and testing to different providers, or another tester runs the test, this stage can be commissioned on its own.

Which attackers and scenarios should our TLPT be based on?

The scenarios and objectives, with the evidence behind each and where it came from, handed on to the testing stage of the TLPT.

Expert reviewed

SURFACE Attack surface EXPOSED Exposed information THREAT Relevant threats Unsupported guess Needs more evidence Your scenario TLPT Carried into the test
Where attack surface, leaked information and relevant threats overlap, the scenarios with evidence behind them are chosen and carried into the TLPT.

When it fits

  • A supervisor or parent company requires TLPT

    You need threat-led scenarios prepared under a set framework.

  • You want to test against the threats aimed at you

    If you are wondering whether you are ready for the groups said to target your sector, we prepare red teaming around their methods instead of a generic attack.

  • You want exposure findings carried into scenarios

    You want what attack surface, leak or impersonation analysis found to become the basis of scenarios that assume a real attack path.

  • Last round's scenarios need updating

    If your organisation or the relevant threats have changed since the last TLPT, the scenarios need bringing up to date too.

The SAFE SQUARE approach

Built on confirmed exposure

Scenarios are built on exposure actually found in your organisation by attack surface, leak and impersonation analysis.

Fitted to the framework

Where a supervisor or parent company has set a framework, we confirm its requirements first and carry out the analysis and scenarios to meet them.

Evidence that carries into testing

The evidence and objectives behind each scenario are recorded and handed on, so the analysis is used as it stands whether SAFE SQUARE runs the test or the framework assigns it to another provider.

What we look at

The evidence that matters differs by organisation and industry; below are things we often look at.

Attack surface

  • Services and admin screens open to the internet
  • Remote access points and connections with suppliers
  • Assets whose owner is not confirmed

Leaked information

  • Leaked staff accounts
  • Organisation structure and staff details visible from outside
  • Domains and brands that could be used to impersonate you

Relevant threats

  • Threat actors targeting your industry
  • The attack methods they have used
  • Published incidents in the same industry
  • Published threat reports and information shared within the industry

How it runs

  1. Scope and framework

    We agree the organisation and objectives in scope, whether a framework applies, and which part of it SAFE SQUARE takes on.

  2. Analyse threats and exposure

    We analyse your attack surface, leaked information and the relevant threats, recording where the evidence comes from and its limits.

  3. Draw up scenarios

    We combine the threats and exposure analysed into candidate attack scenarios that fit your environment, and set aside assumptions with weak evidence.

  4. Confirm and hand on

    We confirm the scenarios and objectives with you and hand them on to the testing stage of the TLPT.

This analysis is carried out for each TLPT; where attack surface, leak or impersonation analysis has already been done, it starts from those results.

What you receive

TLPT attack scenarios

Scenarios and objectives that fit your environment, with the attack path each one assumes.

The relevant threats

The threat actors and attack methods relevant to your organisation and industry, with the evidence used in the scenarios.

Sources and limits of the evidence

The source and timing of each piece of evidence, with confirmed facts kept apart from assumptions.

The exposure behind the scenarios

The attack surface and leaked information, set out so you can act on them ahead of the TLPT.

The testing and review that follow, and the TLPT as a whole, are set out under Threat-Led Penetration Testing (TLPT).

The principles every engagement follows, safe conduct and stop conditions, facts kept apart from assumptions, and how material is kept and destroyed, are set out under How we work.

A sample analysis resultFictional example
TLPT scenario

A route through an exposed course-management screen to the store of learner records

Organisation: a company running an online learning platform (fictional)

Exposure it starts from
The course-management screen for instructors is open to the internet, and job adverts and conference slides reveal the team structure and the email address format.
Relevant threats
In published cases targeting learner records of education services, tailored phishing of instructor accounts and weaknesses in management screens were used repeatedly.
Objective for the TLPT
Whether the store of learners' personal data can be reached, and whether this is detected and responded to before then.
Limits of the evidence
The methods come from published cases; no activity actually aimed at this organisation has been confirmed (assumption).
  1. Tell us what worries you, or what you want checked. A few lines are enough.

  2. We reply with a proposed scope, schedule and cost, and settle them with you.

  3. Once agreed, the work begins. Results and next steps come to you as it runs.