Cyber Security · Intermediate
Ethical Hacking
Learn how systems are actually broken — reconnaissance, scanning, exploitation of real weaknesses — under written authorization, and how to report it so the client can fix it.

Cyber Security program
- Lessons
- 4
- Study time
- 40m
- Level
- Intermediate
- Program
- Cyber Security
Sign in to open the lessons
4 lessons
Lessons, files and narration open after you sign in and buy the program. One payment opens every course in it.
Sign in to open a lesson. Buying the program opens every course and lesson in it, permanently.
About this course
A penetration test is a professional service with a contract, a scope and a report, not a folder of screenshots. This course teaches the work in that order: getting written authorisation first, mapping what an outsider can see, then exploiting only what is in scope and writing it up so the client can actually fix it.
You will meet the weakness classes behind most real breaches — injection, broken authentication and session handling, broken access control, exposed storage and unpatched components — against a lab target rather than somebody's live website. Each technique is paired with the control that defeats it, so you learn the attack and the defence in the same lesson.
The course ends with the deliverable clients pay for: findings ordered by risk, evidence a technical reader can reproduce, business impact a manager understands, and a retest that proves the fix worked. Law, consent and ethics are the first lesson, not a closing disclaimer.
Who this is for
- You already understand networks, operating systems and the shell, and want to test systems rather than only defend them.
- You are IT staff or a developer asked to find your own organisation's weaknesses before somebody else does.
- You are aiming at junior penetration testing, security analyst or consulting work in Ghana or remotely.
Before you start
- Comfortable in a Linux shell and with IP addressing and DNS — Cyber Security Foundations or Computer Networking covers the ground.
- A machine that can run a virtual lab: 8 GB of RAM is comfortable, 4 GB works with care.
- A written-authorisation habit: every exercise targets a lab you own, never a system you do not have permission to touch.
Where it leads
- Cloud Security covers the cloud misconfigurations that dominate modern breach reports.
- Computer Networks & Architecture explains the protocol behaviour underneath every technique here.
- Junior penetration testing and security analyst roles exist in Ghanaian banks, fintechs and consultancies, and remote contract testing is a growing market.
Tools you will use
What you will build
- 1An attack surface map of a target built from public sources only
- 2A scanning and enumeration report with the services found and what each one exposes
- 3A documented exploitation chain against an authorised lab target
- 4A client-ready penetration test report with risk ratings and fixes
- 5A retest checklist that confirms each fix held
Curriculum
2 modules · 4 lessons · 40m
Sign in to open each lesson
01 · Mindset and reconnaissance
Authorization, attacker thinking, and finding out what is exposed before touching anything.
1. Ethical hacking, authorization and the law
The difference between a penetration tester and a criminal is a document. This lesson covers what ethical hacking is and is not, the authorization and scope that must exist in writing before any test, the phases of a penetration test, the professional codes and reporting standards, and the legal position in Ghana under the Cybersecurity Act and the Data Protection Act — because a tester who cannot state their authority is a liability to their client.
2. Reconnaissance and mapping the attack surface
Before a single packet is sent, most of a system's weaknesses are already visible in public data: DNS records, certificate logs, cloud pointers, exposed metadata and job adverts that name every technology in the stack. This lesson covers passive reconnaissance, mapping an attack surface from the outside, service and directory enumeration on an authorised target, and how to organise findings so that the exploitation phase — and the report — has something to stand on.
02 · Exploitation and reporting
Systematic testing of the weaknesses that actually get exploited — then the report that makes it count.
1. Exploitation: how weaknesses become access
This lesson covers the vulnerability classes that dominate real-world breaches — injection, broken authentication and session handling, broken access control, misconfiguration and outdated components — how each is tested methodically with the OWASP Web Security Testing Guide as the checklist, how exploitation is documented as evidence rather than loot, and where a test stops at proof of impact instead of going further.
2. Reporting, defence and the security career
A penetration test that produces a folder of screenshots has failed. This lesson covers the report that clients actually act on — findings, risk ratings in business terms, reproduction steps, remediation, prioritisation — plus the defensive habits that follow from everything you have learned (patching, least privilege, logging, backups), responsible disclosure of a bug you find outside an engagement, and the routes into security work from where you are now.
4 lessons, including the a client-ready penetration test report on an authorised lab target, with evidence and verified fixes project. Sign in and buy the program to open them. Create an account to track progress and earn the certificate.
Taught by a working engineer
codemasterghana Team — Course team. Every lesson is written to be used, not just watched.
A verifiable certificate
Complete every lesson and you get a certificate with a code and QR that an employer can check in seconds.
Practice in the Code Lab
Write and run code in the browser while you learn, with your work saved to your own account.
Still have a question?
Email hello@codemasterghana.com or send a message from the contact page — we answer within two working days, in English or Twi.