Quick answer
A penetration test finds and proves as many exploitable vulnerabilities as possible in a defined scope, such as an application or network, usually with defenders aware. A red team engagement pursues a specific objective covertly, using any realistic path, to test whether the organisation detects and responds. Penetration tests measure weaknesses; red teams measure resilience against a real attacker.
On this page
The Short Version
A penetration test asks "what is wrong with this system, and how bad is it?" A red team engagement asks "could a realistic attacker reach our crown jewels, and would we notice?" Both are offensive security, both are run by skilled testers, and both produce findings, but they answer different questions for different audiences.
Side by Side
| Penetration test | Red team engagement | |
|---|---|---|
| Question answered | What vulnerabilities exist in this scope? | Can an attacker achieve this objective, and would we detect it? |
| Scope | Defined systems, applications or networks | The whole organisation: people, process and technology |
| Approach | Broad and thorough within scope | Narrow and goal-driven, taking the quietest path |
| Stealth | Usually not covert; defenders often informed | Covert; only a small control group knows |
| Typical duration | Days to a few weeks | Several weeks to months |
| Social engineering | Only if scoped in | Commonly included |
| Main output | Prioritised vulnerability findings with fixes | Attack narrative, detection timeline and resilience findings |
| Primary audience | Engineering and IT teams | Security leadership, executives and the board |
When to Choose a Penetration Test
Choose a penetration test when you need assurance on specific systems: a new application before release, an internet-facing perimeter, a cloud environment, or an internal network after major change. It is the right starting point for most organisations, it satisfies most compliance testing requirements, and it gives engineering teams concrete issues to fix. An assumed-breach internal test is a useful middle ground that shows how far a compromised account could go.
When to Choose a Red Team
Choose a red team when you already test regularly, fix what you find, and have a detection and response capability (in-house or managed) that you want to test under realistic pressure. A red team is wasted on an organisation whose basics are still failing, because it will mostly confirm what a penetration test would have found in more detail. Rules of engagement matter more in red teaming because testing is covert and often touches production systems and people.
How They Fit Together
Most mature programs use both: penetration tests to keep individual systems sound, purple teaming to build detection collaboratively, and periodic red team or threat-led engagements to test the whole organisation end to end. For the difference between the attacking and defending sides of an exercise, see red team vs blue team.
Regulatory and Framework Context
In Australia, penetration testing is commonly expected under ISO 27001, PCI DSS, the Information Security Manual and APRA CPS 234, which requires systematic testing of information security controls. Intelligence-led red teaming is set out for financial institutions in the Council of Financial Regulators' CORIE framework and is increasingly expected of critical infrastructure operators under the SOCI Act.
Latest intel on this topic
- Barracuda links cloud breach to ARTEX AI-powered cyberattackBleepingComputer · 16 November 2026
- FBI warns ARTEX AI hacking tool is powering global cyberattacksBleepingComputer · 15 November 2026
- ARTEX and AI-Powered Red Teaming Tools: What Defenders Need to KnowUnit 42 · 11 November 2026
- AntiFox AI Pentesting Platform Linked to Attacks That Accessed AWS Production SecretsThe Hacker News · 11 November 2026
- Chinese-linked hackers compromise ConnectWise, target hundreds in global attack, Microsoft saysAI Incident Database · 24 October 2026
Updated hourly from the daily briefing.
Common questions
Is a red team just a bigger penetration test?
No. It has a different goal. A red team is not trying to find every vulnerability; it is testing whether an attacker can reach an objective without being detected and stopped.
Which should we do first?
Penetration testing. Red teaming delivers most value once regular testing and a working detection capability are in place.
Does a red team satisfy penetration testing requirements?
Usually not on its own. Compliance frameworks typically expect defined-scope testing of specific systems, which a red team does not guarantee.
Change log
- 13 November 2026First published.