1. METHODOLOGY — Ethical Hacking
1.1 What is Ethical Hacking Methodology?
Methodology is the structured process an ethical hacker follows to identify, validate, and report security weaknesses.
A professional pentester doesn't simply run:
nmap target
and start attacking.
Instead, the mindset is:
Understand → Discover → Analyze → Validate → Exploit Carefully → Escalate → Document → Report → Remediate → Retest
A simplified practical workflow is:
TARGET │ ▼ ┌──────────────────┐ │ 1. PRE-ENGAGEMENT│ │ Scope & Rules │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 2. RECON │ │ Information │ │ Gathering │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 3. SCANNING │ │ Ports & Services │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 4. VULNERABILITY │ │ ASSESSMENT │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 5. VALIDATION / │ │ EXPLOITATION │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 6. PRIVILEGE │ │ ESCALATION │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 7. POST-EXPLOIT │ │ Impact Analysis │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 8. REPORTING │ └────────┬─────────┘ ▼ ┌──────────────────┐ │ 9. REMEDIATION & │ │ RETEST │ └──────────────────┘
1.2 Phase 0 — Pre-Engagement
This is one of the most important professional skills.
Before touching a target, you need authorization and a clearly defined scope.
Suppose a company tells you:
"Test our website."
That is not enough information.
You need to know:
Scope
For example:
Target: example.com Allowed: example.com api.example.com 10.10.10.20 Not Allowed: admin.example.com third-party payment provider employee systems
Testing window
For example:
Date: 10 October 2026 Time: 10:00 – 18:00
Allowed techniques
For example:
✔ Port scanning ✔ Web vulnerability testing ✔ Authentication testing ✔ API testing ✘ DoS testing ✘ Destructive exploitation ✘ Data deletion
Why this matters
A professional hacker doesn't ask:
"Can I hack this?"
They ask:
"What am I authorized to test, and how far am I authorized to go?"
1.3 Rules of Engagement — RoE
A professional penetration test normally has Rules of Engagement.
It defines:
- target
- scope
- testing period
- allowed techniques
- prohibited techniques
- emergency contacts
- data handling
- evidence collection
- reporting procedure
Example:
TARGET └── 10.10.10.20 ALLOWED ├── Nmap ├── Nikto ├── Burp Suite ├── Web testing └── Authentication testing NOT ALLOWED ├── DoS ├── Data destruction ├── Social engineering └── Third-party systems
This is what separates professional penetration testing from random hacking.
1.4 Phase 1 — Reconnaissance
After authorization, you start gathering information.
Reconnaissance means:
Learning as much as possible about the target before attempting exploitation.
There are two major types.
Passive Reconnaissance
You gather information without directly interacting with the target infrastructure in a meaningful way.
Examples:
- search engines
- public documentation
- DNS information
- certificate transparency
- public code repositories
- public breach disclosures
- technology information
- organization information
Tools you will eventually learn:
Google WHOIS dig nslookup Amass Subfinder theHarvester crt.sh Shodan Censys
Active Reconnaissance
You directly interact with the authorized target.
Examples:
DNS queries Port scanning Service enumeration HTTP requests Directory discovery
Tools:
Nmap Masscan httpx Gobuster ffuf
You will study Reconnaissance as a separate major topic later.
1.5 Phase 2 — Scanning
Now you determine what is actually exposed.
For example:
Target: 10.10.10.20
You might discover:
22/tcp SSH 80/tcp HTTP 443/tcp HTTPS 3306/tcp MySQL
Now your thinking changes.
Instead of:
"There are four ports."
You think:
22 → SSH → What version? 80 → HTTP → What web application? 443 → HTTPS → What technology? 3306 → MySQL → Why is database exposed?
This is enumeration mindset.
Nmap example
In your own lab:
nmap -sV 10.10.10.20
This attempts to identify services and versions.
You might get:
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 80/tcp open http Apache 443/tcp open https nginx
Now you have a much better attack surface map.
1.6 Build an Attack Surface
A good ethical hacker keeps notes.
For example:
TARGET │ ├── 22 SSH │ └── OpenSSH │ ├── 80 HTTP │ └── Apache │ └── /login │ └── /admin │ └── /uploads │ ├── 443 HTTPS │ └── Web Application │ └── 3306 MySQL └── Database
This is called attack-surface mapping.
You're trying to understand:
"Where could security weaknesses exist?"
1.7 Phase 3 — Vulnerability Assessment
Now you look for weaknesses.
Examples:
Outdated software Weak authentication SQL Injection XSS Broken access control Security misconfiguration Exposed services Insecure file upload Default credentials Information disclosure
Tools can help:
Nmap Nuclei OpenVAS Nessus Burp Suite Nikto WPScan
But remember:
A scanner finding is not automatically a vulnerability.
For example, a scanner might say:
Apache version appears vulnerable.
You need to investigate.
1.8 False Positives
This is extremely important.
Suppose a scanner reports:
CRITICAL: Possible SQL Injection
You shouldn't immediately report:
"SQL Injection confirmed."
You investigate manually.
For example, you may discover:
Scanner: Possible SQLi Manual verification: Not exploitable Result: False positive
Professional pentesting requires validation, not blindly trusting scanners.
1.9 Phase 4 — Vulnerability Validation
Now you ask:
Can I actually reproduce the vulnerability?
Suppose you discover a login endpoint:
POST /login
You investigate:
username password session authentication authorization rate limiting
You may discover an authorization problem where:
User A ↓ /account/1001
can improperly access:
/account/1002
That is potentially a Broken Access Control / IDOR-style issue.
The important professional process is:
Discovery ↓ Hypothesis ↓ Safe verification ↓ Evidence ↓ Impact assessment
1.10 Phase 5 — Exploitation
Only after identifying and validating a vulnerability do you consider exploitation.
The purpose of exploitation in ethical hacking is not destruction.
The goal is to demonstrate:
"This vulnerability is real, and here is its security impact."
For example:
Vulnerability ↓ Can execute unauthorized action ↓ Proof of concept ↓ Determine impact
A professional tester tries to use the minimum necessary impact to prove the issue.
For example, don't destroy a database simply to prove that unauthorized database access exists.
1.11 Phase 6 — Privilege Escalation
Suppose your authorized lab gives you:
low-privilege user
Your next question becomes:
"Can this account gain higher privileges?"
Linux:
User ↓ www-data ↓ root
Windows:
Normal User ↓ Administrator ↓ SYSTEM
Common areas you'll investigate later:
Linux
SUID sudo permissions cron jobs writable files services PATH issues credentials kernel/software weaknesses
Windows
Services Scheduled Tasks Permissions Credentials Registry Unquoted service paths Token privileges
Privilege escalation will be a separate major topic.
1.12 Phase 7 — Post-Exploitation
Once you have authorized access, you determine the real impact.
Questions include:
What can this account access? What information is exposed? Can other systems be reached? Can privileges be increased? What security controls prevented further access? How much of the environment is affected?
You should avoid unnecessary data access.
For example:
❌ Downloading an entire customer database.
Instead:
✅ Demonstrate access using a minimal, authorized proof.
1.13 Lateral Movement
In larger environments, one compromised machine may not be the final target.
For example:
Internet ↓ Web Server ↓ Internal Server ↓ Database ↓ Domain Controller
An attacker may attempt to move between systems.
In an authorized assessment, you investigate whether security boundaries actually work.
This becomes particularly important when we reach:
Active Directory.
1.14 Phase 8 — Analysis
A professional hacker doesn't just collect vulnerabilities.
They connect them.
For example:
Weak password + Exposed SSH ↓ Unauthorized access ↓ Local privilege escalation ↓ Sensitive configuration file ↓ Database credentials ↓ Database access
Individually, each finding may look moderate.
Together, they may create a critical attack chain.
This is one of the biggest differences between:
Tool user
and
Security researcher / penetration tester.
1.15 Attack Chain Thinking
Train your brain to think like this:
ENTRY POINT ↓ INITIAL ACCESS ↓ PERSISTENCE?* ↓ PRIVILEGE ESCALATION ↓ CREDENTIAL DISCOVERY ↓ LATERAL MOVEMENT ↓ SENSITIVE DATA ↓ BUSINESS IMPACT
* Persistence should only be tested when explicitly authorized because it can create operational risk.
1.16 Phase 9 — Reporting
This is where many beginners become weak.
A professional pentester must communicate findings clearly.
A vulnerability report normally contains:
Title Severity Description Affected Asset Technical Details Steps to Reproduce Evidence Impact Remediation References
Example:
Finding
Broken Access Control
Severity
High
Affected Endpoint
/account/{id}
Impact
An authenticated user may access another user's account information.
Evidence
User A → /account/1001 User A → /account/1002 Unauthorized information returned.
Remediation
Implement server-side authorization checks for every requested resource.
That's a professional finding.
1.17 Phase 10 — Remediation
A good ethical hacker doesn't only say:
"Your website is vulnerable."
They explain:
"Here's how to fix it."
For example:
Problem: Broken authorization Fix: Perform server-side authorization checks for every object/resource. Do not rely only on: - hidden fields - frontend restrictions - URL obscurity
1.18 Phase 11 — Retesting
After the organization fixes the vulnerability:
Original Finding ↓ Fix Applied ↓ Retest ↓ Vulnerability Fixed? ↓ YES → Close NO → Reopen
This is a very important professional workflow.
🧠 The Mindset You Need
Don't become:
"I know 50 hacking tools."
Become:
"I understand why a vulnerability exists, how to validate it safely, what impact it has, and how to fix it."
For example, don't memorize:
nmap -sV
Understand:
Why am I scanning? ↓ What am I looking for? ↓ What does the result mean? ↓ What should I enumerate next? ↓ Does the service create an attack path?
🛠️ Your Practical Methodology Lab
For learning, build your own isolated lab.
A good beginner environment:
YOUR COMPUTER │ ├── Kali Linux │ ├── Nmap │ ├── Burp Suite │ ├── Gobuster │ ├── ffuf │ ├── Nuclei │ └── Wireshark │ └── Vulnerable Lab ├── OWASP Juice Shop ├── DVWA ├── Metasploitable └── TryHackMe / Hack The Box
Then practice:
1. Define scope ↓ 2. Recon ↓ 3. Scan ↓ 4. Enumerate ↓ 5. Identify vulnerabilities ↓ 6. Validate ↓ 7. Exploit safely ↓ 8. Escalate privileges ↓ 9. Analyze impact ↓ 10. Write report ↓ 11. Remediate ↓ 12. Retest
🎯 Methodology Skills You Should Master
Before moving to Reconnaissance, you should be comfortable with:
| Skill | Goal |
|---|---|
| Scope | Know what you're allowed to test |
| Attack Surface | Map possible entry points |
| Recon | Gather useful information |
| Enumeration | Identify services and technologies |
| Vulnerability Validation | Separate real issues from false positives |
| Exploitation | Safely prove vulnerabilities |
| Privilege Escalation | Understand privilege boundaries |
| Attack Chains | Connect multiple weaknesses |
| Impact Analysis | Determine real-world consequences |
| Reporting | Explain findings professionally |
| Remediation | Explain how to fix them |
| Retesting | Verify the fix |
The Golden Rule
Remember this throughout the entire ethical-hacking course:
Reconnaissance tells you what exists.
Scanning tells you what is exposed.
Enumeration tells you what is running.
Vulnerability assessment tells you what may be weak.
Exploitation proves whether it is actually vulnerable.
Privilege escalation tells you how far access can go.
Post-exploitation tells you the impact.
Reporting tells the organization how to fix it.