A red team plays the attacker and a blue team plays the defender, inside the same organisation and with permission. The exercise tests whether your security holds up when someone tries to break in, which a green dashboard can't tell you.
Why attack yourself
Most security controls are set up once and then trusted. A firewall rule written two years ago, an alert nobody has seen fire, a patching policy that exists on paper: each one looks fine until someone tests it. Often the first test comes from an attacker, which is the worst time to find a gap.
A red team and blue team exercise moves that first test to a time you choose. A group of authorised people behave like an adversary, and the people who defend the systems every day try to catch them. Afterwards both sides compare notes. The result is a list of weak spots found by people on your side, before anyone else finds them.
What the red team does
The red team's job is to think and act like a likely attacker. They pick a goal, such as reading the customer database or taking over an admin account, and try to reach it by whatever route a real attacker would use.
They use the same ways in as attackers do:
- Phishing: emails that trick someone into clicking a link, opening an attachment or typing their password into a fake login page.
- Stolen or reused passwords: credentials leaked from another site, guessed, or captured by that phishing page.
- Unpatched software: a known vulnerability in a server, library or appliance that nobody has updated yet.
- Misconfiguration: a storage bucket left public, a test server still on its default password, an admin panel open to the internet.
Once inside, the red team tries to move further: from one laptop to a file server, from a normal account to an admin one. They record every step, because the write-up of how they got in matters more than the fact that they did. Each route they try is part of your attack surface, the set of places an attacker can get in.
Wondering how this was made? How we make these