Security testing
Red Teaming
A penetration test asks what can be broken. A red team asks whether you would notice. We play a realistic attacker with an agreed goal, and only a few of your people know it is happening.
WHY IT MATTERS
Nobody has checked whether you would spot a real attack
The problem
Tools are not the same as detection
Security tools can be in place without anyone noticing a real attack, or knowing what to do.
- Alerts nobody follows up
- Gaps between teams
- Plans never tried under pressure
The solution
A realistic attacker under rules of engagement
We agree the goal, the limits and the people who know. A small group stays in touch with us throughout.
- Threat-based scenarios
- Written rules of engagement
- Stop conditions agreed
The outcome
Proof of what works
You see where the attack was caught and where it was not, and your defenders learn from it.
- A timeline of the attack and your response
- A joint replay
- A plan for detection and response
Does a requirement ask for it?
What asks for it in Belgium
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
What we check
What we test
For each requirement we review the evidence and check that the control works, so you know exactly where you stand.
Intelligence
Who would target you and how, and what is publicly known about your organisation.
Initial access
Phishing, exposed systems or physical access, as you agree in advance.
Moving towards the goal
From the first foothold to the systems or data named in the scenario.
Detection and response
What your team saw and did, and when.
Threat Detection
Attacker techniques run openly with your security team, to see which are logged, detected or blocked, and how to close the gaps in your monitoring.
HOW IT RUNS
From scope to verified fixes
The phases stay the same; their length follows your scope.
-
Before testing
Scoping
Targets, people, test windows and exclusions, with written authorisation and rules of engagement.
-
Phase 1
Intelligence
Threat scenarios and public information about your organisation.
-
Phase 2
Attack simulation
A realistic attack towards the agreed goal, with a small group informed.
-
After testing
Report
Findings with evidence, risk and a fix, a management summary and a walkthrough with your team.
-
On request
Retest
We check your fixes and update the report.
A guide, not a fixed promise: the length of each phase depends on your scope.
GET A PROPOSAL
Tell us what you want tested
Tell us the targets and any deadline. We send a written proposal with scope, dates and a fee.
THREAT-LED PENETRATION TESTING
DORA TLPT, TIBER and DNB ART
Financial entities identified by their competent authority run a threat-led penetration test at least every three years under DORA, on live critical or important functions and following a set procedure.
Support with the mandatory deliverables
We support your preparation of the deliverables, from the scope specification to the test summary report, in the formats your TLPT authority expects.
Through to the attestation
Support for your control team at every step, until your TLPT authority attests the test.
TIBER and DNB ART too
The same process under a national TIBER framework or DNB ART, where your authority uses it.
GRC+
- Scenarios grounded in threat intelligence
- Senior testers with red team experience
- Purple team sessions to improve detection
- Findings that cover people, process and technology
WORKING WITH US
What it takes from your side
A named contact, the access we agree and a little of your team's time.
Your trusted contact
One person who knows the test is happening, makes decisions and can reach the right people if something needs to stop.
Targets and exclusions
Addresses, accounts and documents for what is in scope, and clear limits on what is not. You inform any provider or third party affected.
Testing carries some risk
We agree windows and limits to keep it low. No test can promise to find every weakness; it shows what we found in the agreed scope and time.
What you receive
The red team report
Each finding with its evidence, risk, the steps to reproduce it and a fix.
A management summary
What was tested, the main risks and the decisions needed, without the technical detail.
In the report
A walkthrough
A session with your team to go through the findings and answer questions.
Video call
A retest on request
We check your fixes and update the report, so you can show the result to auditors and customers.
Updated report
Why organisations choose GRC+
Independent of your suppliers
We test what you have. We take no margin on a product we assess or recommend.
Findings tied to your requirements
Our team also works on NIS2, DORA, ISO 27001, PCI DSS and Swift CSP, so results can serve your audits too.
Risk rated for your business
We rate each finding by what it could cost you, not only by a scanner's score.
Written rules of engagement first
Scope, limits and contacts are agreed in writing before any test starts.
FAQ
Red Teaming: frequently asked questions
Something else? Ask us in a 30-minute call.
What is the difference between red teaming and penetration testing?
A penetration test looks for as many vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. as possible in a defined scope. A red team test pursues specific objectives, such as reaching a critical system, the way a real attacker would, and tests whether your organisation detects and responds.
Is a red team test safe for our production systems?
Tests run under agreed rules of engagement, with a control team on your side that can pause or stop the test at any time. Actions that carry risk are agreed in advance.
Can a red team test meet TIBER, DNB ART or DORA TLPT?
We run red team tests that follow TLPTThreat-Led Penetration Testing methods, and work alongside the TLPTThreat-Led Penetration Testing provider your authority accepts. The same holds for TIBERThreat Intelligence-Based Ethical Red Teaming and DNBDe Nederlandsche Bank ART, which set their own roles, phases and documents.
Are we ready for a red team?
If basic penetration test findings are still open, fix those first, because a red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. would simply find them again. An ATT&CK detection assessment can be a good step before it.
Who in our organisation knows about the exercise?
A small group, named in advance, who can stop it, confirm what is real and handle anything unexpected. Everyone else responds as they normally would.
Do you run real malware?
We use controlled test tools that behave like attackers, on machines you select, under rules of engagement you approve.
Show 10 More Questions
What does a red team exercise cost?
The fee follows your scope. You receive a written proposal with scope, dates and a fee before any work starts.
Do you subcontract the testing?
No. The team that plans and runs your red team test also writes the report and joins the debrief.
Who can use the DNB ART framework?
DNBDe Nederlandsche Bank designed ART for institutions in the Dutch financial sector, such as banks, payment institutionsPayment Institution, pension providers and insurers. Organisations in other critical sectors, such as healthcare, telecom and energy, can use it too.
Which financial entities must carry out a DORA TLPT?
Those identified by their competent authority on the basis of DORADigital Operational Resilience Act‘s criteria, such as their impact, systemic importance and ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. profile. In the Netherlands, DNBDe Nederlandsche Bank formally instructs the entities concerned.
Who takes part in a TIBER test?
Your control team, the only staff who know a test is underway; your blue teamThe people responsible for defending an organisation's systems against cyberattacks, including detecting suspicious activity and responding to it. In a TIBER-EU test, the blue team includes relevant staff and service providers outside the small control team and is initially unaware of the simulated attack. Afterwards, it records its observations and works with the simulated attackers to identify improvements. Hong Kong's iCAST framework also uses blue team requirements to assess detection, response and recovery., tested without advance notice; the threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. provider; the red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. testers; and the authority’s TIBERThreat Intelligence-Based Ethical Red Teaming cyber team, which oversees the test.
How does DNB ART relate to TIBER-NL and DORA TLPT?
ART can be used alongside a mandatory TLPTThreat-Led Penetration Testing or a voluntary TIBERThreat Intelligence-Based Ethical Red Teaming test, or on its own. DNBDe Nederlandsche Bank notes that running one scenario a year can, after three years, give test coverage comparable to a TLPTThreat-Led Penetration Testing or TIBERThreat Intelligence-Based Ethical Red Teaming test.
How often is a DORA TLPT required?
At least every three years. The authority can ask an entity to test more or less often, based on its risk profile.
Is a TIBER test mandatory?
No. TIBERThreat Intelligence-Based Ethical Red Teaming is voluntary, but where an entity must carry out a TLPTThreat-Led Penetration Testing under DORADigital Operational Resilience Act, the test follows the TIBER-EU process. In the Netherlands a voluntary TIBERThreat Intelligence-Based Ethical Red Teaming test is identical to a TLPTThreat-Led Penetration Testing apart from participation.
Can we fail a DNB ART test?
No. DNBDe Nederlandsche Bank states that institutions cannot pass or fail ART tests: the purpose is to learn where detection and response need to improve.
Can we use TIBER outside the financial sector?
DNBDe Nederlandsche Bank notes that organisations in other critical sectors can use TIBERThreat Intelligence-Based Ethical Red Teaming, or choose its modular ART framework instead.
Plan your red team exercise
In 30 minutes you learn what is in scope, how we would approach it and what drives the fee. A written proposal follows within two working days. sales@grc.plus +31 20 241 66 00
Related: Penetration Testing