Red teaming

Red teaming services for businesses in Indonesia. We simulate a real attack on your whole organisation, to show whether you can detect it and respond.

Example

The question is not only whether we got in. It is whether anyone noticed.

This example follows an exercise from a phishing email to the finance system. It shows three moments where the attack could be caught, and how closing each gap means the same attack is detected early.

Red team exercise
Exercise runningFinance system reached unnoticed
  1. Phishing email
  2. Staff laptop
  3. File server
  4. Finance system
  • 1GapPhishing email was not reported
  • 2GapUnusual file access raised no alert
  • 3GapOdd finance sign-in went unseen

Illustrative example. Not client data.

What is a red team exercise?

A red team exercise is a simulated attack on your organisation, done with your permission. Our team plays the attacker, known as the red team. We are given one goal, such as reaching the finance system or customer records, and we try to reach it the way a real attacker would.

The exercise tests more than technology. It tests your people, your processes and your systems together. With your permission it can include phishing, which means fake emails that try to trick staff, and other social engineering, which means persuading people to give access.

This is different from a penetration test. A penetration test looks for as many weaknesses as possible in a system you choose. A red team exercise picks one goal and tests whether your organisation can detect and stop an attacker on the way to it. Most of your staff are not told, so the response we see is the real one.

When a red team exercise makes sense

  • You have already done penetration tests and fixed the main findings.
  • You have security monitoring or a response team, and you want to know if it works against a realistic attack.
  • Your leaders want evidence of how the organisation would handle a real attack.
  • You want to know whether staff spot phishing and report it.
  • You have invested in security tools and processes, and you want to see whether they work together.

What a red team exercise can include

We agree the goal, the rules and the limits with you before the exercise starts. These are the parts an exercise can cover.

  • 01

    A clear objective

    A target that matters to your business, such as the finance system, customer data or admin access.

  • 02

    Phishing

    Fake emails sent to staff, with your permission, to see who clicks and who reports.

  • 03

    Social engineering

    Phone calls or messages that try to persuade people to give access. Only with your approval.

  • 04

    Internet-facing systems

    Websites, remote access and cloud services that an attacker can reach from outside.

  • 05

    Movement inside the network

    Once inside, we try to move from one system to the next, towards the objective.

  • 06

    Detection and response

    We record what your team saw, when they saw it and what they did about it.

How a red team exercise works

An exercise is planned with care, so it is realistic and safe at the same time.

  1. 1

    Plan

    We agree the objective, the rules and what is off limits. A small group on your side approves it in writing.

  2. 2

    Research

    We study your organisation from the outside, the way an attacker would, to choose a way in.

  3. 3

    Attack

    We work towards the objective quietly, step by step, and keep a record of every action.

  4. 4

    Report

    You get the full story of the attack: what worked, what was detected and what was missed.

  5. 5

    Review

    We sit down with your security team, replay each step and agree how to close the gaps.

What you get

  • 01

    A summary for leaders

    A short account of what happened and what it means for the business, without jargon.

  • 02

    An attack timeline

    Every step we took, in order, with what your team detected and what went unseen.

  • 03

    Detection gaps and fixes

    Each gap explained, ranked by risk, with a practical way to close it.

  • 04

    A joint review session

    We walk your security team through the attack, so they can recognise it next time.

Questions

Questions and answers

What is the difference between red teaming and penetration testing?

A penetration test looks for as many weaknesses as possible in a system you choose, and your team usually knows it is happening. A red team exercise has one goal and tests the whole organisation, including whether your people and tools detect the attack. Penetration testing asks what is broken. Red teaming asks whether you would notice and respond.

Is our organisation ready for a red team exercise?

Red teaming is most useful when the basics are in place. If your systems have never been tested, start with penetration testing and security hardening. Once you have monitoring and a response process, a red team exercise shows how well they work.

Does a red team exercise include phishing?

It can. Phishing and other social engineering are included only if you approve them in the plan. The aim is to test your processes, not to catch out individual members of staff.

Who in our company knows about the exercise?

Only a small group that you choose. They approve the plan and are our contacts while the exercise runs. Other staff are not told, so the response we see is the real one.

Will a red team exercise disrupt our business?

We plan the exercise to avoid disruption. The rules and limits are agreed in writing first, and your contact group can pause or stop the exercise at any time. If we find something urgent, we tell them straight away.

What happens after a red team exercise?

We go through every gap with your team and agree how to close it. Our security hardening service can make the fixes, and our security monitoring service can add the missing alerts. You can also repeat the exercise later to confirm the gaps are closed.

Contact

Test your response, not just your systems.

Tell us what you most need to protect. We will reply with a plan for an exercise built around it.

We use these details only to reply to you. Privacy policy

  1. Tell us what you need.
  2. We reply with a clear scope and next steps.
  3. Nothing starts until you approve it.