On this page
Side by side
- Question answered
- Pentest: what is weak? Red team: could a real attacker reach our goal, and would we notice?
- Scope
- Pentest: defined assets. Red team: goal-based, may include people and physical access.
- Who knows
- Pentest: usually the IT team. Red team: only a few people.
- Duration
- Pentest: days. Red team: weeks.
- Output
- Pentest: findings and fixes. Red team: attack path, detection gaps and response lessons.
Which one fits
- Need evidence for an audit or customer: penetration test
- Launching a product or API: penetration test
- Mature controls and a security operations team: red team
- Testing phishing resilience: phishing simulations
- Board asks “could we survive a real attack?”: red team
Read about the red team operations service, and types of penetration testing. For report quality, see what makes a VAPT report worth paying for.
Not sure where to start?
Tell us your goal and we will recommend the right test. Request a quote.
Frequently asked questions
What is the difference between red teaming and penetration testing?
A penetration test looks for as many weaknesses as possible in a defined scope and proves their impact. A red team operation pursues a goal, such as reaching sensitive data, while testing whether your people and tools detect and respond.
Do I need a red team or a pentest first?
Most organisations should run penetration tests first and fix the findings. Red teaming is most useful once you have basic controls and a monitoring capability to test.
How long does a red team operation take?
Typically weeks, because the aim is stealth and persistence rather than speed.
Is a red team report accepted for compliance?
It can support some programmes, but audits that ask for a penetration test usually want a scoped test report. A red team adds assurance beyond it.
