Learning Path Cybersecurity
A route through security where every tool is open source and runs on your own machines. No SaaS, no trial licenses, no data leaving your network.
Learn it in this order: build a lab, defend it, attack it, then make both sides work together. Each tool below is the one I would pick first; once you know it, the alternatives are easy.
Only attack systems you own or have written permission to test.
0. Foundations
- learn Linux well: processes, permissions, systemd, logs in
/var/logandjournalctl - learn networking: TCP/IP, DNS, HTTP, TLS, and read packets with Wireshark
- learn the attacker playbook as a map: MITRE ATT&CK tactics and techniques
- learn the Cyber Kill Chain and the Pyramid of Pain
- learn the OWASP Top 10 for web applications
1. Build the lab
Everything else runs here. Break it, snapshot it, rebuild it.
- run a hypervisor with Proxmox VE
- put a firewall in front of the lab with OPNsense
- add an Active Directory to attack and defend with GOAD, Game of Active Directory
- add vulnerable targets: OWASP Juice Shop, DVWA and Metasploitable
- keep an attacker box with Kali Linux
- host your own challenges for the team with CTFd
2. Blue team: see everything
You cannot defend what you cannot see. Collect first, detect second.
- deploy Wazuh as SIEM and XDR: agents on every host, file integrity, vulnerability detection, compliance
- write your own Wazuh rules and decoders
- add Sysmon for Linux for richer process telemetry
- centralize logs with Graylog or OpenSearch, shipped by Fluent Bit
- watch the network with Suricata for IDS and Zeek for network metadata
- keep full packet capture with Arkime
- or get Suricata, Zeek, Arkime and a SIEM in one install with Security Onion
- query every endpoint like a database with osquery managed by Fleet
- block brute force and bad IPs with CrowdSec or Fail2ban
3. Blue team: detect and respond
- write detections once, run them anywhere with Sigma and pySigma
- write file and memory signatures with YARA
- automate triage with Shuffle as SOAR: Wazuh alert in, enrichment, ticket out
- manage incidents and cases with DFIR-IRIS
- enrich observables with Cortex analyzers
- hunt and collect forensic artifacts from any host with Velociraptor
- analyze memory with Volatility 3 and disks with Autopsy
- build timelines with Plaso and Timesketch
- catch intruders early with honeypots: OpenCanary and T-Pot
4. Blue team: reduce the attack surface
- scan the network for vulnerabilities with OpenVAS, Greenbone Community Edition
- scan containers, IaC and dependencies with Trivy
- track every finding to closed in DefectDojo
- own identity: SSO and MFA with Keycloak or authentik
- keep secrets out of code with OpenBao and find leaked ones with Gitleaks
- reach internal services without exposing them with Headscale or WireGuard
5. Threat intelligence
Know who attacks companies like yours, and how, before they reach you.
- share and consume indicators with MISP
- subscribe to free feeds: CIRCL OSINT, abuse.ch, AlienVault OTX
- model actors, campaigns and TTPs as a knowledge graph with OpenCTI
- connect MISP, ATT&CK and your feeds as OpenCTI connectors
- push OpenCTI indicators into Wazuh, so intel becomes alerts
- run your own OSINT on your company with SpiderFoot
6. Red team: recon and initial access
Think like the attacker, inside the lab or a signed scope.
- map hosts and ports with Nmap and Masscan
- find subdomains and live services with Amass, subfinder and httpx
- scan for known issues at scale with Nuclei templates
- test web apps with ZAP, ffuf and sqlmap
- run authorized phishing simulations with Gophish
7. Red team: exploit, move, persist
- exploit known vulnerabilities with Metasploit Framework
- run command and control with Sliver or Mythic
- attack Active Directory paths with BloodHound CE
- crack the hashes you collect with Hashcat and John the Ripper
- write the report the client will read with SysReptor or Ghostwriter
8. Purple team: close the loop
Red finds the gap, blue closes it, and you measure both.
- pick the techniques to test from your threat intel in OpenCTI, not from what is fun
- run single techniques with Atomic Red Team and Invoke-AtomicRedTeam
- emulate a full adversary with MITRE Caldera
- emulate cloud attacks with Stratus Red Team
- for each technique, check Wazuh: alerted, logged only, or missed
- turn every miss into a Sigma rule or Wazuh rule, then run the test again
- track every exercise and its outcome with VECTR
- map your detection coverage on ATT&CK Navigator with DeTT&CT
9. Capstone: a SOC in a box
- one compose file or Proxmox template with Wazuh, Suricata, Zeek, Shuffle, DFIR-IRIS, MISP and OpenCTI wired together
- an attack from Caldera that flows into an alert, a Shuffle playbook, an IRIS case and an ATT&CK coverage update
- write what you learned, and share it
How the pieces connect
MISP feeds ──► OpenCTI ──► indicators ──┐
▼
agents, Suricata, Zeek, osquery ──► Wazuh ──► Shuffle ──► DFIR-IRIS case
▲ │
Caldera, Atomic Red Team ── attacks ────┘ Velociraptor ◄─┘ hunt
│
└──► VECTR + ATT&CK Navigator: what we caught, what we missedShares tags with
- Learning Path AI EngineerAn AI engineer builds products on top of models, they do not train them. The hard part is not calling the API, it is knowing if the answer is good. Learn it in this order:…
- Learning Path AWS Lambdalearn how to bundle backend using webpack in a single bundle (check this learn how to automate lamdba deploys using serveless or aws cdk (github actions) learn how to configure…
- Learning Path Backendlearn about basic database modelling, use excalidraw learn about database concepts. Read Database Internals learn to answer these questions learn how to connect to a database and…
- Learning Path DevOpslearn about docker learn about kubernetes practice with minikube learn about CI/CD practice with github actions practice with sadservers practice with labs.iximiuz practice with…
- Learning Path Dockerlearn why we need docker learn how to define a Dockerfile learn how to build a docker learn how to list images learn how to run docker with port forward learn how to go inside…
Sign in with GitHub to reply.
Select any passage to quote it.
Comments