THE PROGRAMME
A serious course starts with a method.
Cybersecurity is not a sequence of impressive tools. It is the ability to understand a system, identify a risk, collect reliable evidence, choose a proportionate response and explain the result. This programme is organised around that sequence.
Training takes place through Discord with screen sharing and practical explanation, step by step. We work with each learner until the core concepts are usable, then move to a small group with a comparable level. That structure protects the quality of the discussion and gives each participant room to ask precise questions.
LEARNING METHODOLOGY
Learn the reasoning behind the action.
Our sessions follow a repeatable loop: understand the concept, observe a controlled demonstration, perform the task in the lab, record the evidence and review the result. This is slower than copying a command and much more useful after the lesson ends.
Assess the starting point
We begin with your current knowledge, not with a generic list of commands. We identify gaps in networking, operating systems, Linux, web concepts and basic security vocabulary, then set a sequence you can actually follow.
Explain, demonstrate, practise
Each subject is introduced in plain language, demonstrated through screen sharing, and repeated by the learner inside an isolated lab. The objective is understanding why a tool is used, what it changes and how to read its output.
Review the evidence
Progress is reviewed through notes, small practical assignments and short explanations from the learner. A correct result matters, but so do the reasoning, the evidence and the ability to communicate what happened.
Reach a working Semi-Pro foundation
Once the fundamentals are reliable, we place you with learners at a comparable level. The group is useful because participants can compare approaches, explain their reasoning and learn from one another without a large skill gap.
Build a documented next step
We finish each phase with a clear record of what you can do, what still needs work and which certification or specialism is sensible next. A certificate is a direction and a proof point; it is not a substitute for practical competence.
TOOLS & LAB PRACTICE
Tools are instruments. Context is the skill.
You will see the tools that appear in real security workflows, but each one is taught with its purpose, limits and consequences. Every exercise uses isolated virtual machines, assigned targets, test accounts and synthetic data. A public address, an exposed login or a request from another person is never a licence to test.
Linux & Kali Linux
The working environment for security analysis, files, permissions, processes and repeatable lab work.
- In the programme
- We learn the shell, file permissions, process inspection, package management and safe virtual-machine setup before using specialised tools.
- Boundary
- A Kali installation is not permission to touch an external system. Lab traffic stays inside the authorised environment.
Nmap
Maps hosts, ports and services so a defender can understand the visible attack surface of a lab.
- In the programme
- We read scan results, compare expected and observed services, and document what the evidence does and does not prove.
- Boundary
- Scanning an address because it is reachable is not authorisation. Targets must be supplied lab assets or covered by explicit written scope.
Wireshark & tcpdump
Shows how network conversations are structured and helps investigate traffic, failures and suspicious patterns.
- In the programme
- We work with supplied captures and synthetic lab traffic, then explain protocols, filters, timestamps and the limits of an observation.
- Boundary
- Captures can contain credentials and personal data. We use test data only and never capture private networks or communications.
Burp Suite
Helps understand HTTP requests, sessions, input handling and the difference between a browser action and a server decision.
- In the programme
- We proxy a deliberately vulnerable training application, inspect requests and write a reproducible observation before discussing a fix.
- Boundary
- Active testing can change data or affect a service. Training stays on the assigned application and test accounts.
Metasploit Framework
Connects a vulnerability hypothesis to a controlled demonstration, helping learners understand impact and remediation.
- In the programme
- We use intentionally vulnerable machines, record the preconditions and stop after the learning objective is demonstrated.
- Boundary
- Exploit capability is never a licence to test production. This course uses isolated, authorised virtual labs only.
SQLmap
Automates parts of SQL-injection verification so the learner can focus on evidence, impact and remediation.
- In the programme
- We use a local training application with known test data and compare automated findings with manual reasoning.
- Boundary
- Automation can expose or modify data quickly. No real database, login or public endpoint is used.
Hydra
Explains authentication risk, rate limiting, lockout and why password security is an operational issue.
- In the programme
- We use synthetic accounts and a deliberately bounded service to study logs, controls and defensive responses.
- Boundary
- Credential testing against another person or service is prohibited. The exercise never uses real credentials.
Aircrack-ng
Introduces wireless security concepts, captures and defensive configuration without touching nearby networks.
- In the programme
- We use simulations or supplied captures to discuss frames, authentication and configuration choices.
- Boundary
- No transmission, capture or testing is performed against home, workplace or nearby Wi-Fi.
CERTIFICATION PATH
Each certificate has a reason.
We do not promise a certificate, employment or a particular result. We prepare the learner to make an informed choice and to study from a practical base. The sequence below is a framework; your actual route follows your level, evidence, specialism and professional objective.
Google Cybersecurity Certificate
We use Google’s programme as a structured foundation for security work: Linux, SQL, Python, security operations, risks, vulnerabilities, detection and response. It gives the learner a vocabulary and a first analyst-oriented workflow.
What we are building: The target is not memorisation alone: read an event, form a hypothesis, collect evidence and explain a response.
CompTIA Security+
Security+ is treated as a broad security benchmark. We prepare the concepts behind the exam—threats, architecture, secure operations, identity, risk, governance and incident response—then connect them to the lab evidence the learner has produced.
What we are building: The learner should be able to discuss a security decision, its risk and its control—not just name a tool.
CEH · Certified Ethical Hacker
For the ethical-hacking direction, CEH is discussed after the learner has a reliable foundation. The emphasis is on methodology, scope, evidence, reporting and remediation in authorised labs—not on collecting attack commands.
What we are building: The decision to pursue CEH depends on your level, practical record and career direction; it is not a compulsory promise for every learner.
A specialisation chosen with evidence
After the core path, we help you choose a direction such as SOC and detection, penetration testing, cloud security, digital forensics or governance. The recommendation follows your ability, interests and professional objective.
What we are building: The result is a realistic next step with a study plan, lab practice and a clear reason for choosing it.
RESPONSIBLE PRACTICE
Bug Bounty comes after discipline.
In parallel with the course, a learner may explore Bug Bounty programmes that explicitly authorise security research. The work is not “try everything”; it is read the scope, understand the rules, test only what is permitted, preserve evidence and report clearly. A valid reward depends on the programme’s policy and acceptance of the report.
The course itself remains virtual-lab-only. Separate research requires the programme’s explicit scope and permission; “for learning” is not an exception.
TIME & COHORT
A fixed rhythm protects the work.
The programme contains 150 training hours. Sessions last two hours and take place every other day. Saturday is reserved for review; Sunday is a rest day. The group is limited to 10 people, with 6 places currently selected, so the instructor can follow the work closely.
Live screen sharing and guided practice on Discord.
Revisit notes, questions and practical evidence.
A deliberate pause in the weekly rhythm.
ENROLLMENT
Read the terms before you reserve a place.
The course is for people who are prepared to work consistently, ask questions, keep records and respect the ethical boundaries of security work. Read the course policy in full before confirming your agreement.
150 hours of personal guidance, practical labs and structured progression.
Discuss your level firstOther contact optionsInstant bank transfer
Transfer InstantIf the programme is a serious fit for you and you wish to reserve a place, use the following account details. Then read and accept the working policy below.
A shared commitment to responsible learning.
Read the course policies, confirm each commitment and sign your agreement in the next window.