Red Team

An exercise with an agreed objective, such as reaching a critical system or sensitive data, run like a real adversary: over the internet, through people and, if the scope allows, through the front door. You find out whether your defense notices and reacts, not just where the flaws are.

Area
Offensive Security
Scope areas
5
Phases
5
Reports
5

Scope

  • Exercise objectives

    We agree with you on what an adversary would go after: sensitive data, a critical system, control of the domain.

  • Open-source reconnaissance

    OSINT on the company, its systems and its people, without touching your systems.

  • Initial access

    Over the internet, through social engineering or by physical intrusion, according to the agreed rules.

  • Movement and persistence

    Privilege escalation and lateral movement with MITRE ATT&CK techniques.

  • Detection and response

    We record what your defense saw, when it saw it, and how it reacted at each stage.

How it works

  1. 01

    Objectives and rules of engagement

    We agree on the objective, the permitted paths, who knows about the exercise and who can stop it.

  2. 02

    Reconnaissance

    We gather what an adversary would learn about the company before acting.

  3. 03

    Execution

    From initial access to the objective, with every step documented and evidenced.

  4. 04

    Reports

    A weekly status during the exercise and, at the end, the technical, executive and financial risk reports.

  5. 05

    Debrief and retest

    We review with your defenders what was and was not detected, and retest the fixes.

What you get

  1. Weekly status

    during the test

    Every vulnerability found, with evidence and the fix, for the project team.

  2. Technical

    at the end

    Exploitation steps, evidence and recommendations, for the people who fix.

  3. Executive and financial risk

    at the end

    Business risks, financial impact and an action plan, for the board.

  4. Retest

    after the fixes

    We confirm what was fixed and what is still open.

See what the reports look like →

Leonnes / Executive report / Exemplo S.A.02 / Follow-up

From the first status to the retest

Open vulnerabilities, report by report

  • Found
  • Open

A peak of 9 open at the end of the test; 1 at the retest, of the 12 found.

Vulnerabilities per report
MomentFoundOpen
W1 (Weekly status)33
W2 (Weekly status)66
W3 (Weekly status)98
W4 (Technical and executive)129
W5 (Follow-up)126
W6 (Follow-up)123
Retest (Retest)121

ConfidentialFictitious data

A page of the Leonnes executive report, filled with fictitious data.

In practice

Insurance

Red Team and specialized assessments

Red Team exercises, social engineering, physical intrusion and penetration tests of web and mobile applications and APIs for one of the largest insurers in the global market, simulating real attack scenarios to find vulnerabilities, assess security controls and show the risks that matter to the organization.

See all case studies

Frequently asked questions

What is the difference between a Red Team and a pentest?

A pentest looks for as many flaws as possible within a defined scope. A Red Team pursues an objective by any path the rules allow, and also measures your team's detection and response.

Does the security team know about the exercise?

You decide. Usually only a small group knows, so the defense reacts for real. That group follows the exercise and can stop it at any time.

Does it include physical intrusion?

When it is part of the objective and the agreed rules, yes, with written authorization and defined emergency contacts.

How long does it take?

It depends on the objective and the authorized paths. The proposal sets the timeline after the scoping conversation.

See what an attacker would see first

We reply within one business day.