Ethical Hacking
Certified Ethical Hacking Practitioner
Learn to find, prove and report real vulnerabilities the way a professional penetration tester does: recon, scanning, exploitation, web testing and professional reporting, with the ethics and scope that make it legal.
What an ethical hacker actually is
An ethical hacker is a penetration tester who has decided in advance **where they may go and
when they must stop**, and then works inside that box with the client's written permission. The
skill is identical to an attacker's; the difference is the paperwork.
This course is built around the actual deliverable of a penetration test: a report that a
developer can act on. Attackers rarely fail because they found nothing — they fail because
nobody told them what to fix. Every module here ends in something you would hand to an
engineer.
What you will be able to do
- Run a scoped engagement: build a rules of engagement, work inside it, and stop cleanly
- Perform passive and active reconnaissance and turn it into an attackable surface
- Scan, enumerate and fingerprint hosts, services and versions without wasting the window
- Build and execute a repeatable exploit workflow, and prove impact rather than assume it
- Test web applications for injection, access control, session and client-side flaws
- Write findings a developer can fix, with a reproduction path and a real severity argument
Rules you must not break
- Never test a system you have no written authorisation to test
- Never go beyond the agreed scope, even if you find something critical
- Never exfiltrate real personal data to "prove" access; demonstrate with the minimum
that works
- Never run destructive actions, DoS, or persistence without an explicit written exemption
If a client asks for something that crosses a legal line, decline and say why.
Syllabus
-
1
Ethics, law and rules of engagement
The difference between a legal test and a crime, and the document that decides which one you are.
Locked -
2
Passive and active reconnaissance
Building the target map from public data, then from the target's own responses.
Locked -
3
Scanning, enumeration and fingerprinting
Which hosts are alive, what is listening, what version, and what that implies.
Locked -
4
Exploitation workflow and proving impact
Turning a version fingerprint into a working, reproducible, reversible proof.
Locked -
5
Web application penetration testing
The OWASP Top 10 as a test plan, plus the authorisation bugs that never appear in a scanner.
Locked -
6
Reporting, remediation and retesting
Turning test evidence into changes developers actually make.
Locked
Final exam
Locked. Enrol in the course to unlock the final exam.