EN · DE Request an offer
Services

Red Teaming

Realistic attack simulations within agreed rules of engagement: our analysts bypass your security mechanisms and move laterally through your infrastructure.

Overview

Realistic attack simulations within agreed rules of engagement

Emulating a determined attacker and using typical as well as unconventional methods, our analysts try to infiltrate your infrastructure as far as the agreed rules of engagement allow. The focus is on bypassing the security measures you have deployed.

The goal of red teaming is to verify your protective mechanisms and to identify missing measures. In addition, the reactions of your blue team to advanced persistent threats (APTs) are tested and trained.

Focus areas

  • Reconnaissance
  • Initial access
  • Command and control
  • Privilege escalation
  • Lateral movement
  • Persistence
  • Detection and response
  • Debriefing
Scope

What we test

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

Phases of a red teaming engagement

Reconnaissance

Extensive gathering of information about the organisation, including publicly available data, organisational structures, employee information, technologies in use and network details.

Initial Access

Attempts to gain unauthorised access to the organisation, for example through phishing and other social engineering techniques, attacks on systems and applications that can be reached from the internet, compromised credentials or, if agreed, physical access to premises.

Command and Control

Setting up controlled infrastructure for the remote control of compromised systems, which is operated securely for the duration of the engagement and removed afterwards.

Privilege Escalation

Attempts to escalate privileges on compromised systems and in directory services (e.g. Active Directory or Microsoft Entra ID) in order to take control of critical systems.

Lateral Movement

Spreading across the network and into cloud environments to compromise additional systems, exploiting both technical and human weaknesses.

Persistence

Testing how an attacker can maintain long-term access to critical systems and conceal their presence. After the engagement, Nullsecurity Labs removes all implants, persistence mechanisms and accounts it has created or documents them for removal by you.

Achieving Objectives

Demonstrating access to the agreed objectives and simulating the exfiltration of sensitive data using harmless test data in order to test the ability to detect data leaks.

Detection and Response

Evaluation of whether and when the activities are detected by security systems and the security team (e.g. EDR, SIEM or SOC) and how effective the response to security incidents is.

Debriefing

On request, joint review of the attack path with your security team after completion of the engagement in order to derive improvements for detection and defence.

Reporting

Upon completion of the engagement, a detailed report is provided covering the attack path including a timeline, all identified vulnerabilities and the recommended countermeasures.

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

Attack paths from our projects

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

Internal penetration test

From the office network to domain admin

Starting point: a test machine in the office network, without any credentials.

  1. Captured credentials

    Legacy name resolution (LLMNR) made machines send login hashes to the test machine.

  2. Weak password

    The hash of a service account could be cracked offline.

  3. Admin on many servers

    The service account was local administrator on numerous servers; one of them held the credentials of a domain admin in memory.

  4. Domain admin

    Full control over every system in the domain.

What helped: LLMNR and NBT-NS disabled, long random passwords for service accounts, admin tiering and LAPS for the local administrator passwords.

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
How does red teaming differ from a penetration test?

A penetration test examines the systems in an agreed scope for vulnerabilities and exploits them. Red teaming emulates a determined attacker: our analysts try to bypass your security measures and test how your blue team responds.

What is the goal of red teaming?

To verify the protective mechanisms you have deployed, to identify missing measures and to test and train the reactions of your blue team to advanced persistent threats (APTs).

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.