Penetration testing mimics a real attack to find how vulnerabilities could be chained together to breach a system, using the same tools attackers use. It differs from a vulnerability scan in one key way: a scan flags possible issues, a penetration test proves what an attacker could actually do by exploiting them. It is a largely manual craft, and it supports frameworks from the ISM to ISO 27001 and PCI DSS.
A vulnerability scan reveals what might be wrong, while a penetration test reveals what an attacker could actually do about it. That difference is the whole point, and it is worth understanding before commissioning either.
What is penetration testing?
Penetration testing is security testing in which assessors mimic real-world attacks to identify ways around the security features of an application, system or network. As the US standard NIST SP 800-115 puts it, it often involves launching real attacks on real systems using the tools and techniques that attackers use.
What distinguishes a penetration test from other security testing is that it looks for combinations. Most tests, in NIST’s words, involve looking for combinations of vulnerabilities on one or more systems that can be used to gain more access than could be achieved through a single vulnerability. A lone medium severity flaw might be unremarkable on its own, but chained with two others it can lead to full compromise, and that chaining is what a penetration test reveals. Beyond finding the path in, a test also shows how well a system tolerates real attack patterns, how much sophistication an attacker would need, and how well the organisation’s defenders detect and respond. It answers not just what is vulnerable, but what an attacker could achieve.
How is penetration testing different from a vulnerability scan?
This is the distinction that matters most, and the two are often confused. A vulnerability scan is automated: it identifies systems and matches them against a database of known vulnerability signatures to report what might be present. It is fast, and it is good at quantifying an organisation’s exposure to surface vulnerabilities, weaknesses that exist in isolation.
A penetration test goes further in two ways. First, it confirms. As NIST notes, while a scanner checks only for the possible existence of a vulnerability, the attack phase of a penetration test exploits the vulnerability to confirm its existence. That removes the false positives scanners are prone to. Second, it finds what scanners cannot: risks that only appear as the result of chaining several weaknesses together, which a signature based scanner has no way to detect. The plainest way to put it is that a scan produces a list of possible issues, while a penetration test produces evidence of what an attacker could actually do. Both have a place, but they answer different questions, which is explored further in penetration testing vs a vulnerability assessment.
What are the phases of a penetration test?
A penetration test typically moves through four phases: planning, discovery, attack and reporting. Each builds on the last, and together they mirror how a real attacker would operate against the target.
Planning sets the scope, the rules of engagement and the goals, for example whether the test targets a specific application or the whole network. Discovery gathers information about the target and identifies potential vulnerabilities, the reconnaissance an attacker would do. The attack phase is the core: it verifies the potential vulnerabilities by attempting to exploit them, and where an exploit succeeds, it attempts to gain further access, escalating and moving through the environment as an attacker would. Reporting then documents what was found, with risk ratings and remediation guidance. Importantly, reporting is not only a final step, testers keep written logs throughout and raise serious findings with management as they are discovered, so a critical issue is not held back until the end. This structure is common across the recognised methodologies, including PTES and NIST SP 800-115.
Why does penetration testing need manual expertise?
Penetration testing is a largely manual craft supported by tools, not an automated scan. Automated scanners are fast, but they have real limits: they depend on signatures that must be constantly updated, they produce false positives, and they cannot understand context or judge the true risk to a particular organisation.
The things a scanner cannot do are exactly what a skilled tester provides. Manual analysis finds new or obscure vulnerabilities that automated scanners miss. A tester verifies real risk by exploiting a flaw rather than reporting a theoretical one. And importantly, a tester can find business logic vulnerabilities, flaws in how a process is meant to work, that tools cannot detect. As OWASP puts it, automated tools find it hard to understand context, so testing whether a user can circumvent a business process, predict resource names or escalate privileges remains a manual art relying on the tester’s skill and knowledge of the business rules. NIST similarly stresses that penetration testing requires extensive networking and operating system knowledge and advanced knowledge of vulnerabilities and exploits. This is why the quality of a penetration test depends heavily on the tester, not just the tools.
How does penetration testing fit Australian and other frameworks?
Penetration testing is a recognised way to evidence that security controls actually work, and it supports several frameworks, though what each requires differs. The ASD Information Security Manual distinguishes between vulnerability scans, vulnerability assessments and penetration tests, and recommends regular testing of critical systems, applications and infrastructure, including those managed by third parties, with follow up testing to verify fixes.
Elsewhere, ISO 27001 expects an organisation to manage technical vulnerabilities and test its controls, and penetration testing is a common way to do that. SOC 2 auditors frequently expect penetration testing as evidence for the relevant criteria. And PCI DSS is the most prescriptive, requiring penetration testing based on an industry accepted methodology at least once every 12 months and after any significant change. The Essential Eight does not mandate penetration testing as one of its eight strategies, but a test is a good way to confirm that Essential Eight controls are actually effective. So penetration testing is rarely the compliance requirement itself, but it is one of the most credible ways to prove that controls hold up. For an organisation that needs a penetration test to meet a framework or a client requirement, Cybernion offers penetration testing.
Frequently asked questions
What is penetration testing?
Penetration testing is security testing in which assessors mimic real-world attacks to find ways around the security of an application, system or network. It uses the same tools and techniques attackers use, and its distinguishing feature is looking for combinations of vulnerabilities that can be chained together to gain more access than any single flaw would allow. A test also shows how well a system withstands attack and how well defenders detect and respond.
How is penetration testing different from a vulnerability scan?
A vulnerability scan is automated and checks whether known vulnerabilities might exist by matching systems against a database of signatures. A penetration test goes further and confirms vulnerabilities by actually exploiting them, and it finds risks that only appear when several weaknesses are chained together, which a scanner cannot see. In short, a scan flags possible issues, a penetration test proves what an attacker could actually do.
What are the phases of a penetration test?
A penetration test typically runs through planning, discovery, attack and reporting. Planning sets the scope and rules. Discovery gathers information and identifies potential vulnerabilities. The attack phase verifies those vulnerabilities by exploiting them and then attempts to gain further access. Reporting documents the findings with risk ratings and remediation guidance. Reporting also runs throughout, with logs kept and serious issues raised as they are found.
Why does penetration testing need manual expertise?
Automated scanners are fast but limited. They rely on signatures, produce false positives, and cannot understand context or chain vulnerabilities together. A skilled tester finds new or obscure flaws a scanner misses, verifies real risk rather than theoretical risk, and can exploit business logic weaknesses that tools cannot detect because they require understanding how a process is meant to work. Penetration testing is therefore a largely manual craft supported by tools.
How does penetration testing fit Australian frameworks?
Penetration testing supports several frameworks. The ASD Information Security Manual distinguishes vulnerability scans, vulnerability assessments and penetration tests, and recommends regular testing of critical systems. ISO 27001 expects technical vulnerabilities to be managed and tested. PCI DSS requires penetration testing at least annually and after significant change. So while the exact requirement varies, penetration testing is a recognised way to evidence that controls actually work.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, National Institute of Standards and Technology, September 2008
- Web Security Testing Guide, OWASP, 2026
- The Penetration Testing Execution Standard, PTES, 2026
- Cyber security guidelines (ISM), Australian Signals Directorate, 2026
Last updated: 30 August, 2026
