Penetration Testing for Cyber Securitys
Penetration testing is authorised simulated attack on a system to find exploitable weaknesses before real attackers do. A test follows a methodology of scoping, reconnaissance, scanning, exploitation, post-exploitation and reporting, using tools such as Nmap, Burp Suite and Metasploit, always within written rules of engagement.
Stage: Offensive Security · Part of the Cyber Security roadmap · Last reviewed 19 November 2026
What to learn in Penetration Testing
- Define scope and rules of engagement before any testing starts
- Scan a lab host with Nmap and interpret open ports and services
- Identify a vulnerable service version and research a matching exploit
- Document each finding with evidence, impact and a remediation
- Explain the difference between a vulnerability scan and a penetration test
Penetration Testing interview questions
What is the difference between a vulnerability scan and a penetration test?
A vulnerability scan is automated and lists potential weaknesses without exploiting them. A penetration test adds manual testing and exploitation to prove what is actually exploitable and what an attacker could reach, then reports business impact.
Why do penetration tests need written authorisation?
Testing systems without permission is illegal, and even authorised tests can disrupt services. A signed scope document defines targets, timing, methods and contacts, which protects both the tester and the client.
Where Penetration Testing fits in the Cyber Security roadmap
Penetration Testing belongs to the Offensive Security stage (beginner level), which takes about 5 hours. Think like an attacker.
Other units in this stage
Back to the full Cyber Security roadmap