Pentesting, Security, Privacy and CTF/Bug Bounty¶
A structured path from absolute beginner to practitioner-level expertise in ethical hacking, penetration testing, CTF competitions, and bug bounty programs.
[!IMPORTANT] Ethics and Legal Disclaimer
All techniques, tools, and methodologies covered in this topic are intended exclusively for: - Authorized penetration testing with written permission from the asset owner - CTF (Capture The Flag) competitions on designated platforms - Bug bounty programs within the defined scope of the program - Defensive security research and understanding attacker techniques to build better defenses
Performing any security testing without explicit written authorization is illegal under laws including the Computer Fraud and Abuse Act (CFAA) in the United States, the Computer Misuse Act in the United Kingdom, the Lei nº 12.737/2012 (Lei Carolina Dieckmann) and Marco Civil da Internet in Brazil, and equivalent legislation worldwide. Unauthorized access, even for "educational" purposes, can result in criminal prosecution, civil liability, and permanent damage to your career.
Every module in this topic will reinforce the ethical and legal requirements. If you are ever uncertain whether an action is authorized, stop and ask first.
[!NOTE] Topic Overview This topic teaches the theory, tools, and methodologies used by security professionals to find and responsibly disclose vulnerabilities. You will learn to think like an attacker so you can defend like an expert. The curriculum progresses from foundational security concepts through web application exploitation, network reconnaissance, CTF strategy, and professional bug bounty reporting.
This topic is organized into 12 progressive modules. Work through them in order — the concepts build on each other in a carefully designed arc from beginner to expert.
Table of Contents¶
- Overview
- Historical Context
- Real-World Applications
- Learning Objectives
- Difficulty and Time Estimate
- Prerequisites
- Learning Modules
- Progress
- Milestones
- Test Scores
- Projects
- Resources
- Related Topics
- Learning Journal
- AI Metadata
Overview¶
Ethical hacking — also called penetration testing, red teaming, or security research — is the practice of probing systems, networks, and applications for vulnerabilities with the explicit authorization of the asset owner. It is one of the most in-demand disciplines in the technology industry, and for good reason: the only way to know whether a system is secure is to try to break it under controlled conditions before a malicious actor does.
The distinction between an ethical hacker and a malicious attacker is not the knowledge or the tools — it is authorization and intent. Both may use the same techniques; what separates them is written permission, defined scope, responsible disclosure, and the goal of improving security rather than exploiting it.
Why It Matters¶
Security vulnerabilities are not theoretical. In 2017, the Equifax breach exposed the personal data of 147 million Americans because of an unpatched Apache Struts vulnerability. In 2020, the SolarWinds supply chain attack compromised thousands of organizations worldwide, including multiple US government agencies. In 2021, the Log4Shell vulnerability (CVE-2021-44228) in the ubiquitous Log4j library sent security teams scrambling across every major industry. Each of these could have been discovered and mitigated earlier by skilled security researchers working within an authorized framework.
Understanding security is valuable because:
- It is a prerequisite for building software that handles sensitive user data responsibly
- It develops the adversarial mindset needed to anticipate how systems can fail under attack
- Proficiency in it is expected in roles including Penetration Tester, Security Engineer, Red Team Analyst, Application Security Engineer, and Bug Bounty Hunter
Key Features of This Topic¶
- Ethical foundation first — every offensive technique is taught alongside its defensive countermeasure and its legal/ethical context
- Hands-on with legal platforms — all practical exercises use CTF platforms (HackTheBox, TryHackMe), intentionally vulnerable VMs (DVWA, Metasploitable), or simulated environments
- Professional workflow — you will learn how professional pentesters document findings, write reports, and communicate with clients
- Bug bounty ready — the curriculum ends with the skills needed to participate in real bug bounty programs on HackerOne, Bugcrowd, and Intigriti
Historical Context¶
Security research as a discipline emerged from the hacker culture of the 1960s at MIT's Tech Model Railroad Club and AI Laboratory, where "hacker" meant someone who found creative solutions to technical challenges — a deeply positive term. The culture spread to early universities and research institutions, emphasizing curiosity, openness, and building.
Timeline¶
| Year | Event |
|---|---|
| 1960s | MIT AI Lab hacker culture forms; "hacking" means creative problem-solving |
| 1971 | John Draper ("Captain Crunch") discovers 2600 Hz tone enables free phone calls, launching the phreaking era |
| 1983 | The movie WarGames brings public awareness to computer intrusion; Reagan signs NCSC directive |
| 1986 | Computer Fraud and Abuse Act (CFAA) enacted in the US — first major computer crime law |
| 1988 | Morris Worm — first widely deployed internet worm; demonstrates real internet-scale risk |
| 1993 | First DEF CON conference in Las Vegas; becomes the world's largest hacking conference |
| 1995 | First Black Hat Briefings; professional security research culture begins to formalize |
| 1998 | L0pht hackers testify before US Senate, warning they could take down the internet in 30 minutes |
| 1999 | CVE (Common Vulnerabilities and Exposures) system launched by MITRE |
| 2002 | CVSS (Common Vulnerability Scoring System) introduced to standardize severity ratings |
| 2010 | Stuxnet discovered — first nation-state cyberweapon targeting industrial infrastructure |
| 2011 | HackerOne founded; begins formalizing bug bounty programs |
| 2012 | Bugcrowd founded; bug bounty industry begins rapid growth |
| 2013 | Google Project Zero announced — elite internal team finding zero-days in widely used software |
| 2017 | WannaCry ransomware uses NSA-leaked EternalBlue exploit; Equifax breach affects 147M people |
| 2021 | Log4Shell (CVE-2021-44228) — one of the most critical vulnerabilities ever in widely deployed software |
| Today | Bug bounty programs pay millions annually; OSCP/CEH certifications are standard job requirements |
Real-World Applications¶
Security research and penetration testing are actively used across every industry:
- Financial Services — Banks and payment processors run continuous bug bounty programs; PCI-DSS compliance requires annual penetration testing
- Government and Defense — The US DoD HackerOne program was the first federal bug bounty; red teams probe critical infrastructure for vulnerabilities
- Healthcare — HIPAA-regulated systems undergo penetration testing to protect patient data; medical device security is an emerging specialization
- Technology Companies — Google, Microsoft, Apple, Meta, and virtually every major tech company run bug bounty programs paying $300 to $1,000,000+ per vulnerability
- CTF Competitions — DEF CON CTF, Google CTF, picoCTF, HackTheBox, and hundreds of others provide legal, structured environments for skill development and competition
- Security Consulting — Firms like Mandiant, CrowdStrike, NCC Group, and independent consultants perform authorized penetration tests for organizations of all sizes
Learning Objectives¶
By completing this topic in full, you will be able to:
- Explain the ethical and legal framework for security research, including the difference between authorized testing and illegal intrusion
- Perform reconnaissance using passive (OSINT) and active techniques within an authorized scope
- Identify and exploit common web application vulnerabilities (OWASP Top 10) in CTF and intentionally vulnerable environments
- Use industry-standard tools including Burp Suite, nmap, Metasploit, and Nikto in authorized contexts
- Conduct a structured penetration test following the reconnaissance → scanning → exploitation → post-exploitation → reporting methodology
- Participate effectively in CTF competitions across the major categories (web, pwn, crypto, forensics, reversing)
- Write professional-quality vulnerability reports including CVSS scoring, reproduction steps, impact assessment, and remediation recommendations
- Apply defensive countermeasures for each offensive technique covered, understanding both sides of every vulnerability class
Difficulty and Time Estimate¶
| Attribute | Value |
|---|---|
| Difficulty | Beginner → Expert |
| Estimated Total Hours | 80–120 hours |
| Prerequisites | Basic networking, basic programming, Linux CLI |
| Recommended Pace | 5–8 hours/week |
| Topic Type | Practical / Mixed (heavy hands-on component) |
| Suitable For | Software developers, sysadmins, CS students, career changers into security |
Prerequisites¶
Before starting this topic, you should have a working understanding of:
- [[networks]] — specifically: IP addressing, TCP/UDP, HTTP/HTTPS, DNS, how packets travel
- Basic Linux command line — specifically: navigating the filesystem, running commands, piping output
- Basic programming (Python preferred) — specifically: reading and writing scripts, loops, functions
[!TIP] Not sure if you're ready? If you can SSH into a server, run
nmap --help, and read a Python script without being completely lost, you are ready for Module 01. Start and let gaps surface naturally — they will become clear as you work through the exercises.
Learning Modules¶
| # | Module | Difficulty | Status |
|---|---|---|---|
| 01 | Introduction to Ethical Hacking | Beginner | [ ] |
| 02 | Networking for Security | Beginner | [ ] |
| 03 | Web Application Security | Intermediate | [ ] |
| 04 | SQL Injection | Intermediate | [ ] |
| 05 | XSS and Client-Side Attacks | Intermediate | [ ] |
| 06 | Broken Access Control | Intermediate | [ ] |
| 07 | Reconnaissance and OSINT | Advanced | [ ] |
| 08 | Exploitation Basics | Advanced | [ ] |
| 09 | Post-Exploitation | Advanced | [ ] |
| 10 | CTF Methodology | Advanced | [ ] |
| 11 | Bug Bounty Programs | Expert | [ ] |
| 12 | Capstone: Full Penetration Test Report | Expert | [ ] |
Status key: Not started · ~ In progress · x Complete
Progress¶
Overall Progress¶
Update this bar as you complete modules. Each block = 5% of total modules.
Legend: ░ = not started ▒ = in progress █ = complete
Example: [███████▒░░░░░░░░░░░░] 7.5 / 12 modules (62%)
Point Tracker¶
| Category | Earned | Possible | Percentage |
|---|---|---|---|
| Module Tests | 0 | 444 | 0% |
| Exercises | 0 | 120 | 0% |
| Projects | 0 | 60 | 0% |
| Bonus | 0 | — | — |
| Total | 0 | 624 | 0% |
Milestones¶
- First Step — Complete Module 01 (Introduction and Ethics)
- Foundation Built — Complete Modules 01–03 with at least 70% on each test
- Halfway There — Complete 6 of 12 modules
- Web Security Mastery — Complete Modules 03–06 with at least 80% on each test
- First CTF Flag — Capture your first flag on HackTheBox or TryHackMe
- First Bug Report — Submit your first vulnerability report in a bug bounty program
- Topic Complete — All 12 modules finished
- Professional Pentester — Complete the capstone with a full professional-quality report
Test Scores¶
Append a row after each test attempt. Do not overwrite previous attempts.
| Module | Date | Score | Grade | Notes |
|---|---|---|---|---|
| — | — | —/— | — | Not started |
Grade scale: A ≥ 90% · B ≥ 80% · C ≥ 70% · D ≥ 60% · F < 60%
Projects¶
See PROJECTS.md for project ideas ranging from beginner to expert.
My Projects:
| Project Name | Difficulty | Started | Status | Link |
|---|---|---|---|---|
| — | — | — | — | — |
Resources¶
See RESOURCES.md for a curated list of books, courses, platforms, and tools.
Top picks so far (fill in as you study):
- To be filled in
- To be filled in
- To be filled in
Related Topics¶
Topics that complement, extend, or are required for this topic:
- [[networks]] — foundational networking knowledge that underpins nearly every security technique
- [[devops-platform-engineering]] — cloud infrastructure and containers are common attack surfaces
- [[python]] — the dominant scripting language for exploit development and security tooling
- [[javascript-typescript-react]] — understanding web development is essential for web security
See also the ROADMAP.md for how this topic fits into broader learning paths.
Learning Journal¶
Date-stamp each entry. Write honestly — confusion documented now becomes insight later. Newest entries at the top.
2026-06-09 — Started Topic¶
What I did today: - Read the topic overview and ROADMAP.md - Reviewed the ethics and legal disclaimer carefully - Set up HackTheBox and/or TryHackMe accounts for legal practice
What clicked: - Write one thing that made sense immediately
What's still unclear: - Write your first open question — then add it to QUESTIONS.md
How I feel about this topic: - Honest assessment: excited / intimidated / curious / confused / etc.
Add new journal entries above this line, newest first.
AI Metadata¶
# Maintained by LEAPS tooling — manual edits will be overwritten on next sync
last_ai_expansion: "2026-06-09"
topic_slug: "pentesting-security"
topic_name: "Pentesting, Security, Privacy and CTF/Bug Bounty"
module_count: 12
modules_complete: 0
total_points_earned: 0
total_points_possible: 624
completion_percentage: 0
difficulty: "Beginner to Expert"
estimated_hours: 100
prerequisites:
- "networks"
- "linux-cli"
- "python"
related_topics:
- "networks"
- "devops-platform-engineering"
- "python"
- "javascript-typescript-react"
tags:
- "security"
- "penetration-testing"
- "ctf"
- "bug-bounty"
- "ethical-hacking"
- "web-security"
creator: "leaps-curriculum-agent"
year_created: "2026"