EN · DE Request an offer
Services

Scenario Based Audits

Security tests based on a scenario developed together with you.

Overview

Attacks along a scenario defined with you

At the beginning of a scenario based audit, we define the attack procedure together with you. Our analysts then carry out the planned attacks.

The analyses performed during a scenario based audit are not limited to technical methods; they can also include tests of physical access controls or social engineering campaigns. The goal depends on the defined scenario, for example raising the security awareness of your employees or verifying the security measures in place.

Focus areas

  • Phishing and spear phishing
  • Vishing and smishing
  • Pretexting
  • Help desk processes
  • Physical access
  • Reporting behaviour
Scope

What we test

Depending on your environment and the agreed scope, we examine in particular:

Social engineering and physical access

Information Gathering

Collection of publicly available information about your company and its employees (e.g. websites, social networks, job advertisements) in order to develop credible scenarios.

Phishing

Sending emails that appear legitimate and encourage the recipient to click on links, open attachments or disclose confidential information.

Spear Phishing

Targeted phishing attacks on specific employees or departments, based on detailed information about the target.

Credential Harvesting and MFA Bypass

Collecting credentials via fake login pages and testing whether multi-factor authentication can be bypassed, for example through real-time phishing proxies or repeated push requests (MFA fatigue).

Malicious Attachments and Downloads

Testing whether harmless test payloads in email attachments or downloads are executed and whether technical safeguards detect them.

Vishing and Smishing

Phone calls and text messages in which the attacker pretends to be a trusted person or institution, for example IT support staff, in order to obtain credentials or other sensitive information.

Help Desk Processes

Testing whether passwords can be reset or MFA devices registered without the help desk sufficiently verifying the identity of the caller.

Pretexting

Creating a credible pretext to gain the trust of employees and acquire sensitive information or system access.

Baiting

Offering enticing incentives, such as prepared USB storage devices, free downloads, QR codes or discounts, to lure users into executing files or visiting malicious websites.

Physical Access

Attempts to gain access to protected premises, for example through tailgating (following employees unnoticed through secure entry points), by posing as visitors or service providers or by copying access cards.

Surveys and Prize Draws

Using fake online surveys, quizzes or prize draws to gather information from employees that can later be used for attacks.

Reporting Behaviour

Evaluation of whether employees recognise and report attacks and how quickly reported incidents are handled.

Approach

How it works

  1. 1
    Scoping

    Objectives, rules of engagement and time frame, agreed in writing.

  2. 2
    Testing

    Hands-on testing by experienced analysts, supported by tools.

  3. 3
    Reporting

    Management summary, reproducible findings and remediation advice.

  4. 4
    Retest

    On request, we verify your fixes and update the report.

Results

What you receive

  • Management summary, understandable without prior technical knowledge
  • Overview of all findings with their risk rating
  • Technical details for each vulnerability: affected systems, evidence and specific remediation advice
  • Description of the procedure, the tools used and the rating scheme
  • Report in English or German
  • On request a retest of your fixes and an updated report
From the field

An attack path from our projects

Anonymised attack paths from our projects, step by step, and what helped against them.

Scenario based audit

From a phone call to remote access

Starting point: an agreed scenario, only public information.

  1. Research

    Names, roles and phone numbers from public sources such as the company website and career portals.

  2. Call to the help desk

    The analysts posed as an employee with a new phone and asked for a password and MFA reset.

  3. Reset without checks

    The help desk reset both without reliably verifying the caller.

  4. Remote access

    Login to VPN and email with the employee’s account.

What helped: mandatory call-back to a registered number, approval of MFA resets by a manager and training for the help desk.

FAQ

Frequently asked questions

Questions we often hear about this service.

All questions
What can a scenario include?

Besides technical attacks, for example tests of physical access controls or social engineering campaigns such as phishing.

What is the goal of a scenario based audit?

That depends on the scenario, for example raising the security awareness of your employees or verifying the security measures in place.

Not sure where to start?

Tell us about your environment, and we will propose a scope that fits.

Talk to us
@nullseclabs

Follow us on X for more information and current topics.