SSQ.AISSQ.AI
English
help!

Comprehensive Security Health Check

A review of overall security posture, key risks and improvement priorities within an agreed scope

We search like an attacker and check like a defender.

From external exposure to readiness to respond, we look at your organisation's hacking and security issues from five perspectives, and finish with what to fix first and the next steps.

Where do we stand overall?

We bring together confirmed risks and improvement priorities.

Reviewed

Agreed scope Your org Services Access Readiness Data & ops Exposure Fix first 1 2 3 Confirmed Needs a closer look Outside this scope
Five perspectives reviewed together, their results brought into one order of what to fix first.

Two views: attacker and defender

Where the two views disagree, where an attack gets through and the defence does not notice, is what to fix first.

EXPOSURE Exposure SERVICE Services ACCESS Access DATA Data & ops READINESS Readiness ATTACKER Attacker's view From outside in Finds Gets in Spreads Strikes Hides DEFENDER Defender's view Holding the line Known? Blocked? Contained? Protected? Noticed? Fix first The attack gets through; the defence does not see it Stopped or noticed Gets through unseen
The attacker's five moves and the defender's five questions. In this example, access and readiness are what to fix first.
ATTACKER

The attacker's view

Is there a way in, and how far does it reach?

Using the information and methods real attackers use, we work from outside in, all the way to what an intruder could take or stop.

DEFENDER

The defender's view

Can it be stopped, noticed and undone?

We check whether your safeguards, people and procedures do their part against that attack.

What sets it apart

CONCERN Comprehensive SecurityHealth Check TARGET Vulnerability Assessment &Penetration Testing (VAPT) HARM Risk-Focused Security Validation 1 2 3 Across the organisation, riskiest first A set target, against set checks From a feared harm, along the path to it
In the same organisation, where you start decides where you look.

You can start from one concern

Before you have picked a system to test or a harm to guard against, wanting to know where your security stands is enough to begin.

We find where to look first

We pinpoint where an attacker and a security expert would expect trouble and check those places in order, so however long the check runs, the most urgent problems surface first.

We weigh scattered issues together

Issues that sit apart in different teams and systems go on one scale and are ranked by what they mean for the organisation as a whole.

Each perspective is checked with the methods and technology of SAFE SQUARE's professional services.

What we check

For each of the five perspectives we ask the attacker's and the defender's question; what we actually examine follows your environment.

  • EXPOSUREExternal exposure and threats
    Attacker
    If they came for us, what would they look for first?
    Defender
    Is anything open or leaked that we don't know about?

    Example issues

    • Forgotten domains and test servers
    • Leaked staff credentials
    • Sites and apps impersonating you
  • SERVICEServices and infrastructure
    Attacker
    Where could they get in, and do known attacks work?
    Defender
    Do protections still hold after recent changes and in old setups?

    Example issues

    • Web, app and API vulnerabilities
    • Unpatched VPNs, servers and devices
    • Cloud misconfiguration
  • ACCESSAuthentication, permissions and boundaries
    Attacker
    With one account, how far could they spread?
    Defender
    Do permissions and boundaries block what they were designed to?

    Example issues

    • Leavers' and shared accounts
    • Excessive admin rights
    • Partner and contractor access
  • DATASensitive information and operations
    Attacker
    Where is the most valuable data, and how could it be taken or locked?
    Defender
    Do we know where sensitive data flows and who sees it, and could we restore it if lost?

    Example issues

    • Where customer data is stored and who can reach it
    • Backups that survive ransomware
    • Information sent to outside collaboration tools and AI services
  • READINESSReadiness to respond
    Attacker
    How long could they stay without being caught?
    Defender
    Could we notice, stop, recover and explain?

    Example issues

    • Collecting and keeping the logs needed to trace
    • Who is told and who decides in an incident
    • Readiness for phishing and other attacks on people

When it fits

  • You need a fresh look at where you stand

    Your last review was long ago or there has never been one, or a cloud move, a merger or acquisition, or a new person in charge has changed your environment.

  • When an incident hits close to home

    A company in your industry or one you work with has been breached, and you need to answer 'are we all right?' with evidence.

  • Someone is asking where you stand

    Your board, an investor's due diligence, a customer's security requirements or an audit needs your current security state explained with evidence.

  • You need evidence to set priorities

    With limited staff and funds, you need evidence to decide which risks to address first.

How it runs

The length follows what you want to know and your environment, anywhere from half a day to several months; the longer it runs, the wider it reaches.

Wherever something worth a closer look turns up, we dig deeper.

  1. Agree the concern and scope

    We hear what worries you and agree together on the scope and how long it runs.

  2. Map the current state

    From what you share and what can be seen from outside, we single out what an attacker would target and what must be protected.

  3. Check from both sides

    From the attacker's side we validate what actually works; from the defender's side we check whether it would be stopped and noticed. Anything that could affect a service is agreed with you before it runs.

  4. Report and explain

    We explain what we found to decision-makers and to the people doing the work.

When a particular system or risk needs testing to a defined scope and set criteria, professional services such as Vulnerability Assessment & Penetration Testing (VAPT), AI System Security Assessment & Penetration Testing or Privacy Risk Analysis can join the check in one project. Each runs at its full depth with its own deliverables, and its results are brought together with the check's into one overall picture of your risks.

A sample engagementA fictional example, written for illustration.
Request

Please look across our security risks for a month. Our payment API must also go through VAPT before it launches.

Target: the company as a whole, and a payment API about to launch

WorkWhat we doWhat you receive
Security Health CheckOver a month, the riskiest areas first across the five perspectives, with validation where it mattersThe main risks with their evidence, and improvement priorities
Vulnerability Assessment & Penetration Testing (VAPT)The payment API tested before launch, to the agreed scope and test criteriaA VAPT report with the findings, their real impact and reproducible evidence
Bringing it togetherThe two sets of results linked, showing where the payment API's problems sit among the company's risksA summary and overall risk picture for decision-makers, and recommended actions for the people doing the work

You can also go straight to a professional service, or have the check regularly as part of Cybersecurity Care.

What you receive

We state what we checked and under which conditions, and keep facts apart from signs.

SAMPLEWhat to fix first: an exampleA fictional example, written for illustration.
  1. A leaver's account still allows remote access from outside

    Attack path
    1. Leaked account
    2. Remote access (VPN)
    3. Internal file server
    Defence gap
    No multi-factor authentication and no alert on unusual logins
    Why first
    The path is short, and nothing would notice an intruder
  2. Backups can be deleted with the same admin rights as production

    Attack path
    1. Admin account taken over
    2. Backups deleted
    3. Ransomware launched
    Defence gap
    Backups are not separated, and there is no record of a recovery drill
    Why first
    Operations and the means to recover could be lost at once

Confirmed problems

Set down with the evidence and the conditions under which they occur.

Signs that need a closer look

Kept apart from facts, with what it would take to confirm them.

What to examine next

Areas outside this scope or left for later: the starting point for next time.

  • Where you standFor decision-makers

    Your current state across the five perspectives.

  • Findings and evidenceFor the people doing the work

    For each problem, the evidence, attack path, defence gap and direction for improvement.

  • What to fix firstFor both

    An order for what to fix first, set by business impact and evidence, with the reasons for it.

  • Next stepsFor decision-makers

    What needs a closer look or action, set out with the evidence, so you can decide what to do and how far to take it.