Reconnaissance Fundamentals
Table of Contents
- Introduction to Reconnaissance
- Key Concepts and Terminology
- Passive vs Active Reconnaissance
- Reconnaissance Decision Flow
- Information Gathering vs Enumeration
- Legal and Ethical Considerations
- Reconnaissance in the OSCP Exam
- When to Stop Recon and Start Exploiting
- Documentation Best Practices
- Attack Chain Position
- OSCP Exam Tips
Introduction to Reconnaissance
Reconnaissance is the first and most critical phase of any penetration test or security assessment. It is the process of gathering information about a target system, network, or organization before attempting any exploitation. The quality and depth of your reconnaissance directly determines the success of your entire engagement.
Core Principle: “The more you know about your target before you attack, the more likely you are to succeed.”
In the context of the OSCP exam, reconnaissance is your primary weapon for identifying attack vectors. The exam machines are deliberately designed with discoverable information that leads to initial foothold. Missing key recon steps is one of the most common reasons candidates fail to gain access within the allotted time.
Why Reconnaissance Matters
- Identifies Attack Surface: Every open port, service, and piece of information is a potential entry point
- Reduces Guesswork: Informed attacks are faster and more effective than blind attempts
- Reveals Misconfigurations: Many vulnerabilities stem from poor configuration rather than software bugs
- Builds Attack Path: Recon data helps you map out the most efficient route to your objectives
- Saves Time: Targeted exploitation based on recon is far more efficient than spraying exploits
Key Concepts and Terminology
Understanding the vocabulary of reconnaissance is essential for clear communication and structured thinking during assessments.
Footprinting
Footprinting is the process of gathering as much information as possible about a target organization or system. It is the broadest form of reconnaissance and focuses on building a comprehensive profile of the target.
Key characteristics of footprinting:
- Typically passive in nature
- Focuses on organizational-level information
- Aims to build a complete picture of the target’s digital presence
- Includes domain information, network ranges, employee details, technology stack, and public-facing infrastructure
Common footprinting activities:
- Domain registration lookups (WHOIS)
- DNS record enumeration
- Search engine reconnaissance
- Social media profiling
- Public record searches
- Job posting analysis
- Technology stack identification
Reconnaissance
Reconnaissance (often shortened to “recon”) is the broader term encompassing all information-gathering activities. It includes both passive and active techniques and spans from high-level organizational profiling down to specific service and vulnerability identification.
Reconnaissance phases:
- Passive Recon: Gathering information without directly interacting with the target
- Active Recon: Directly interacting with the target to gather information
- Enumeration: Systematically extracting specific details from the target
Enumeration
Enumeration is the systematic extraction of specific information from a target system. It is more targeted and technical than general reconnaissance, focusing on extracting structured data such as:
- Usernames and group names
- Network shares and resources
- SNMP community strings
- SNMP MIB values
- DNS zone information
- NTP information
- SMTP user information
- SNMP routing tables
- NetBIOS names
Key Distinction: Reconnaissance is about gathering information; enumeration is about extracting specific, structured data from live systems.
OSINT (Open Source Intelligence)
OSINT refers to intelligence gathered from publicly available sources. It is a subset of passive reconnaissance that relies entirely on information that has been made publicly accessible.
OSINT sources include:
- Search engines (Google, Bing, DuckDuckGo)
- Social media platforms
- Public government records
- DNS records
- Code repositories (GitHub, GitLab)
- Forums and blogs
- News articles and press releases
- Job postings
- Certificate transparency logs
- Archive services (Wayback Machine)
Attack Surface
The attack surface is the sum of all points where an attacker could potentially enter or extract data from a system. It includes:
| Category | Examples |
|---|---|
| Network | Open ports, services, protocols, exposed APIs |
| Application | Web applications, mobile apps, software interfaces |
| Human | Employees, contractors, social engineering targets |
| Physical | Server rooms, office buildings, hardware devices |
| Cloud | Cloud storage buckets, misconfigured services, IAM roles |
Reducing attack surface is a defensive goal; mapping attack surface is an offensive recon goal.
Passive vs Active Reconnaissance
Understanding the distinction between passive and active reconnaissance is fundamental to planning your approach and managing detection risk.
Detailed Comparison
| Aspect | Passive Reconnaissance | Active Reconnaissance |
|---|---|---|
| Definition | Gathering information without directly interacting with the target | Directly interacting with the target systems to gather information |
| Detection Risk | Very low to none | Moderate to high |
| Information Depth | Surface-level, publicly available | Deep, specific, and technical |
| Speed | Can be slow (depends on source availability) | Generally faster for specific targets |
| Tools | Search engines, WHOIS, DNS lookups, social media, OSINT tools | Nmap, Nikto, Gobuster, enum4linux, SNMP enumeration |
| Network Traffic | No traffic generated to target | Generates network traffic to target |
| Logging | Target is unaware; no logs generated | Target may log the activity |
| IDS/IPS Trigger | No | Possible |
| Legal Risk | Lower (public data only) | Higher (direct interaction) |
| Accuracy | May be outdated or incomplete | Current and verified |
| Examples | Google dorking, WHOIS lookup, social media research | Port scanning, service banner grabbing, directory brute-forcing |
Passive Reconnaissance Techniques
1. Search Engine Reconnaissance
Using search engines to discover information about the target:
# Google Dorking examples
site:target.com filetype:pdf
site:target.com inurl:admin
site:target.com intitle:"index of"
site:target.com ext:php intext:"error"
site:target.com "password"
site:target.com "confidential"
cache:target.com
2. WHOIS and DNS Research
# WHOIS lookup
whois target.com
# DNS record lookups (passive - querying public resolvers)
dig target.com ANY +short
nslookup target.com
3. Social Media and Public Records
- LinkedIn employee profiling
- Twitter/X company accounts
- GitHub organization repositories
- Public government filings
- Business registration databases
4. Archive and Historical Data
# Wayback Machine API
# Access via: https://web.archive.org/web/2/http://target.com
# Using the Wayback Machine API
curl -s "http://web.archive.org/cdx/search/cdx?url=target.com/*&output=json&fl=timestamp,original,statuscode,mimetype"
Active Reconnaissance Techniques
1. Network Scanning
# Basic TCP SYN scan
nmap -sS -p- target.com
# Service version detection
nmap -sV -p 22,80,443,8080 target.com
# OS detection
nmap -O target.com
# Aggressive scan (version detection, OS detection, scripts, traceroute)
nmap -A target.com
2. Service Enumeration
# HTTP enumeration
nikto -h http://target.com
gobuster dir -u http://target.com -w /usr/share/wordlists/dirb/common.txt
# SMB enumeration
enum4linux -a target.com
# SNMP enumeration
onesixtyone -c /usr/share/doc/snmp/mibs/EXAMPLES target.com
3. Banner Grabbing
# Using nc
nc -v target.com 22
nc -v target.com 80
# Using curl
curl -I http://target.com
# Using nmap
nmap -sV --script=banner target.com
Choosing Between Passive and Active
The choice depends on several factors:
| Factor | Favors Passive | Favors Active |
|---|---|---|
| Detection Concern | High sensitivity, strict rules of engagement | Low sensitivity, authorized full assessment |
| Time Available | Limited time for broad overview | Time available for deep analysis |
| Target Size | Large organizations, broad scope | Specific systems, narrow scope |
| Information Needed | Organizational context, high-level overview | Technical details, specific vulnerabilities |
| Exam Context | Initial phase, broad target list | Focused on specific exam machines |
Best Practice: Always start with passive reconnaissance before moving to active techniques. Passive recon provides context and helps you focus your active efforts on the most promising targets.
Reconnaissance Decision Flow
The following diagram illustrates the decision-making process during reconnaissance:
flowchart TD
A[Start Reconnaissance] --> B{Scope Defined?}
B -->|No| C[Clarify Scope and Rules of Engagement]
C --> B
B -->|Yes| D[Passive Reconnaissance]
D --> D1[WHOIS Lookup]
D --> D2[DNS Enumeration]
D --> D3[Search Engine Recon]
D --> D4[Social Media Research]
D --> D5[OSINT Gathering]
D1 --> E{Passive Intel Sufficient?}
D2 --> E
D3 --> E
D4 --> E
D5 --> E
E -->|Yes - Found Vuln| F[Document Findings]
E -->|No| G[Active Reconnaissance]
G --> G1[Network Scanning]
G --> G2[Port Scanning]
G --> G3[Service Detection]
G --> G4[OS Detection]
G1 --> H{Services Identified?}
G2 --> H
G3 --> H
G4 --> H
H -->|Yes| I[Service Enumeration]
H -->|No| J[Reassess Approach]
I --> I1[Web App Enumeration]
I --> I2[SMB Enumeration]
I --> I3[FTP Enumeration]
I --> I4[SNMP Enumeration]
I --> I5[DNS Enumeration]
I1 --> K{Vulnerabilities Found?}
I2 --> K
I3 --> K
I4 --> K
I5 --> K
K -->|Yes| L[Document and Prepare Exploitation]
K -->|No| M{Time Remaining?}
M -->|Yes| N[Deepen Enumeration]
M -->|No| O[Pivot to Known Vectors]
N --> I
O --> L
J --> D
L --> P[Transition to Exploitation Phase]
F --> P
Decision Flow Explanation
-
Scope Definition: Always begin by confirming the scope and rules of engagement. In the OSCP exam, this is provided in the exam instructions.
-
Passive Reconnaissance Phase: Gather all publicly available information without touching the target directly. This includes WHOIS, DNS, search engines, and OSINT.
-
Evaluation Point: After passive recon, assess whether you have enough information to proceed. If you’ve found exploitable information (e.g., exposed credentials, known vulnerable software versions), you may skip to exploitation.
-
Active Reconnaissance Phase: If passive recon is insufficient, begin active scanning. Start broad (network/port scanning) and narrow down (service detection, OS detection).
-
Service Enumeration: Once services are identified, enumerate each one for specific information, configurations, and potential vulnerabilities.
-
Vulnerability Assessment: Evaluate findings for exploitable conditions. If found, document and prepare for exploitation.
-
Time Management: If no vulnerabilities are found and time is running low, pivot to known common vectors (default credentials, common misconfigurations, well-known exploits).
Information Gathering vs Enumeration
While often used interchangeably, these terms have distinct meanings in the penetration testing methodology.
Information Gathering
Information gathering is the broad process of collecting any and all data about a target. It is the umbrella term that encompasses both passive and active reconnaissance.
Characteristics:
- Broad and exploratory
- May not have specific targets in mind
- Focuses on quantity and breadth of information
- Includes both passive and active techniques
- Goal: Build a comprehensive picture of the target
Examples:
- Searching for the target on Google
- Looking up domain registration information
- Scanning for open ports
- Identifying technologies in use
Enumeration
Enumeration is the systematic extraction of specific, structured information from a target system or service. It is more targeted and technical than general information gathering.
Characteristics:
- Targeted and specific
- Focuses on extracting structured data
- Requires direct interaction with the target
- Goal: Extract actionable, specific information
Examples:
- Extracting usernames from an SMB server
- Enumerating SNMP community strings
- Extracting DNS zone records
- Listing shares on a Windows server
- Enumerating user accounts via LDAP
Comparison Table
| Aspect | Information Gathering | Enumeration |
|---|---|---|
| Scope | Broad, exploratory | Narrow, targeted |
| Interaction | Passive or active | Active (direct interaction) |
| Output | General information | Structured, specific data |
| Timing | Early phase | After initial recon identifies targets |
| Examples | Port scanning, WHOIS, Google dorking | User enumeration, share listing, SNMP queries |
| Tools | Nmap, WHOIS, search engines | enum4linux, nmap scripts, SNMP tools |
| Risk | Low to moderate | Moderate to high |
The Relationship
Information gathering and enumeration work together in a cycle:
flowchart LR
A[Information Gathering] --> B[Identify Services]
B --> C[Enumeration]
C --> D[Extract Specific Data]
D --> E{New Targets Found?}
E -->|Yes| A
E -->|No| F[Exploitation Planning]
Legal and Ethical Considerations
Reconnaissance activities must always be conducted within legal and ethical boundaries. Understanding these boundaries is critical for professional penetration testers and OSCP candidates.
Legal Framework
Authorized vs Unauthorized Access
| Activity | Authorized | Unauthorized |
|---|---|---|
| Passive Recon on Public Data | Generally legal | N/A (public data) |
| Active Scanning | Legal with written authorization | Illegal (Computer Fraud and Abuse Act, CFAA) |
| Exploitation | Legal with written authorization | Illegal (CFAA, various state/federal laws) |
| Data Collection | Legal within scope | Illegal if outside scope |
Key Legal Considerations
-
Scope Definition: Never perform reconnaissance outside the defined scope. The scope document is your legal protection.
-
Rules of Engagement (RoE): Follow the RoE strictly. Some techniques may be prohibited even within scope.
-
Data Handling: Collected data must be handled according to the engagement agreement and applicable privacy laws.
-
Jurisdiction: Be aware of the legal jurisdiction of the target. Different countries have different laws regarding reconnaissance.
Relevant Laws (US Context)
- Computer Fraud and Abuse Act (CFAA): Prohibits unauthorized access to computer systems
- Gramm-Leach-Bliley Act (GLBA): Protects financial information
- Health Insurance Portability and Accountability Act (HIPAA): Protects health information
- General Data Protection Regulation (GDPR): EU regulation affecting data handling
Ethical Considerations
Professional Ethics
- Confidentiality: Protect all information gathered during the engagement
- Integrity: Report findings honestly and accurately
- Professionalism: Conduct yourself professionally throughout the engagement
- Responsibility: Act in the best interest of the client and affected parties
Ethical Decision Framework
flowchart TD
A[Consider Recon Technique] --> B{Is it within scope?}
B -->|No| C[Do NOT proceed]
B -->|Yes| D{Is it allowed by RoE?}
D -->|No| C
D -->|Yes| E{Could it cause harm?}
E -->|Yes| F[Consult with client/lead]
E -->|No| G[Proceed with technique]
F --> H{Approved?}
H -->|No| C
H -->|Yes| G
OSCP Exam Legal Context
The OSCP exam operates within a controlled, legal environment:
- All targets are authorized: Offensive Security owns or has permission to test all exam machines
- Scope is clearly defined: The exam provides specific IP ranges and domains
- Rules are explicit: The exam rules document outlines what is and isn’t allowed
- No legal risk: As long as you stay within the exam scope, there is no legal risk
Important: Even in the exam context, maintain professional ethics. Do not attempt to access systems outside the exam scope, and do not share exam findings with others.
Reconnaissance in the OSCP Exam
The OSCP exam has specific characteristics that affect how you should approach reconnaissance.
Exam Environment Characteristics
| Characteristic | Description | Impact on Recon |
|---|---|---|
| Controlled Environment | All machines are in an isolated lab | No external noise, clean results |
| Multiple Machines | 5 machines per exam (3 required for pass) | Need efficient recon across all targets |
| Time Limit | 24 hours total | Recon must be efficient, not exhaustive |
| Difficulty Range | Easy to hard machines | Recon depth varies by machine difficulty |
| Common Services | Web, SMB, SSH, FTP, DNS, etc. | Focus on common service enumeration |
| Deliberate Clues | Machines contain discoverable information | Passive recon often reveals key info |
OSCP Recon Strategy
Phase 1: Quick Passive Recon (15-30 minutes)
# Rapid passive recon for all targets
for ip in 10.10.10.1 10.10.10.2 10.10.10.3 10.10.10.4 10.10.10.5; do
echo "=== $ip ==="
nmap -sV -sC -O --top-ports 100 $ip
done
Phase 2: Focused Active Recon (30-60 minutes per target)
# Full port scan on promising targets
nmap -sS -p- -T4 target_ip
# Service version detection on open ports
nmap -sV -p 22,80,443,8080,3306 target_ip
# Script scanning for common vulnerabilities
nmap --script=vuln -p 80,443 target_ip
Phase 3: Service-Specific Enumeration (as needed)
# Web application enumeration
gobuster dir -u http://target_ip -w /usr/share/wordlists/dirb/common.txt -t 50
# SMB enumeration
enum4linux -a target_ip
# SNMP enumeration
onesixtyone -c /usr/share/doc/snmp/mibs/EXAMPLES target_ip
Common OSCP Recon Patterns
-
Web Service Discovery: Most OSCP machines have at least one web service. Enumerate directories, subdomains, and parameters.
-
SMB/Windows Services: Windows machines often have SMB enabled. Enumerate shares, users, and policies.
-
Linux Services: Look for misconfigured services, default credentials, and known vulnerabilities.
-
DNS Information: DNS records often reveal internal infrastructure and subdomains.
-
Banner Information: Service banners frequently reveal version information that leads to known exploits.
Time Management for Recon
| Phase | Time Allocation | Goal |
|---|---|---|
| Initial Scan (all targets) | 15-30 minutes | Identify open ports and services on all machines |
| Passive Recon | 15-30 minutes | Gather WHOIS, DNS, and OSINT data |
| Active Recon (per target) | 30-60 minutes | Deep scan and service enumeration |
| Service Enumeration | As needed | Targeted enumeration of promising services |
| Total Recon Budget | 2-4 hours | Do not exceed this without findings |
Critical Rule: If you have spent 2-4 hours on recon without finding exploitable information, pivot to exploitation of what you have found. Perfect recon is the enemy of good progress.
When to Stop Recon and Start Exploiting
One of the most important skills in penetration testing is knowing when to transition from reconnaissance to exploitation.
Signs You Should Start Exploiting
| Signal | Description | Action |
|---|---|---|
| Known Vulnerability Found | Service version matches a known exploit | Start exploitation immediately |
| Default Credentials | Service accepts default login | Attempt authentication |
| Exposed Files | Sensitive files accessible via web | Analyze and exploit |
| Misconfiguration | Service misconfigured in an exploitable way | Exploit the misconfiguration |
| Time Pressure | Recon time budget exceeded | Exploit best findings so far |
| Clear Attack Path | Recon reveals obvious entry point | Follow the path |
The Recon-Exploit Cycle
Reconnaissance and exploitation are not strictly sequential. They form a cycle:
flowchart TD
A[Reconnaissance] --> B{Exploitable Finding?}
B -->|Yes| C[Attempt Exploitation]
B -->|No| D[Continue Recon]
C --> E{Success?}
E -->|Yes| F[Post-Exploitation / Pivot]
E -->|No| G{Alternative Found?}
G -->|Yes| C
G -->|No| D
D --> H{Time Remaining?}
H -->|Yes| A
H -->|No| I[Pivot to Known Vectors]
I --> C
Decision Criteria
Use the following criteria to decide when to stop recon:
-
You have at least one promising attack vector: If you have identified a service with a known vulnerability, start exploiting it.
-
Diminishing returns: If additional recon is not yielding new information, it’s time to exploit.
-
Time pressure: If you are approaching your time budget, start exploiting with what you have.
-
Clear path forward: If recon has revealed a clear attack path, follow it.
-
Multiple targets: If you have multiple targets, recon all of them briefly, then focus exploitation on the most promising.
Common Mistakes
- Recon paralysis: Spending too much time gathering information without acting on it
- Ignoring obvious vectors: Overlooking simple attacks while searching for complex ones
- Not documenting: Failing to record findings, leading to lost progress
- Tunnel vision: Focusing on one target while ignoring others that may be easier
Documentation Best Practices
Proper documentation is critical during reconnaissance. It ensures you can track your progress, share findings, and build on previous work.
Documentation Framework
1. Target Information
## Target: [IP/Domain]
### Basic Information
- IP Address: 10.10.10.1
- Hostname: target.example.com
- Operating System: Linux (detected via nmap)
- Scan Date: 2026-09-01
### Open Ports
| Port | Service | Version | Notes |
|------|---------|---------|-------|
| 22 | SSH | OpenSSH 7.4 | Default config |
| 80 | HTTP | Apache 2.4.6 | Custom web app |
| 443 | HTTPS | Apache 2.4.6 | Self-signed cert |
| 3306 | MySQL | 5.7.30 | Exposed to network |
2. Reconnaissance Notes
### Reconnaissance Notes
#### Passive Recon
- WHOIS: Domain registered 2020-01-15, registrar: Example Registrar
- DNS Records:
- A: target.example.com -> 10.10.10.1
- MX: mail.example.com
- TXT: v=spf1 include:example.com ~all
#### Active Recon
- Nmap scan completed at 2026-09-01 10:30
- Full port scan: 4 open ports found
- Service detection: Versions identified for all services
- OS detection: Linux kernel 3.10 - 4.11
#### Enumeration Findings
- Web: Directory listing enabled at /backup/
- SMB: No anonymous access
- MySQL: No remote access
3. Command Log
### Commands Executed
```bash
# Initial scan
nmap -sV -sC -O --top-ports 100 10.10.10.1
# Full port scan
nmap -sS -p- -T4 10.10.10.1
# Service enumeration
nmap -sV -p 22,80,443,3306 10.10.10.1
# Web directory enumeration
gobuster dir -u http://10.10.10.1 -w /usr/share/wordlists/dirb/common.txt
### Documentation Tools
| Tool | Purpose | Notes |
|------|---------|-------|
| **Markdown Files** | Structured notes | Recommended for OSCP |
| **Nmap Output** | Scan results | Save in XML and grepable format |
| **Screenshots** | Visual evidence | Capture important findings |
| **Text Files** | Quick notes | Use for rapid logging |
| **Spreadsheet** | Target tracking | Track multiple targets |
### Nmap Output Formats
Always save nmap output in multiple formats:
```bash
# Save in all formats
nmap -sV -sC -O -oA scan_results target_ip
# This creates:
# scan_results.nmap (normal output)
# scan_results.xml (XML format)
# scan_results.gnmap (grepable format)
Documentation Checklist
- Target IP and hostname recorded
- Open ports and services documented
- Service versions noted
- OS detection results recorded
- WHOIS information captured
- DNS records documented
- Web application findings noted
- Enumeration results recorded
- Commands executed logged
- Screenshots taken for key findings
- Timeline of activities maintained
- Findings categorized by severity
Attack Chain Position
Reconnaissance is the first phase of the cyber kill chain and penetration testing methodology.
flowchart LR
A[Reconnaissance] --> B[Scanning & Enumeration]
B --> C[Vulnerability Analysis]
C --> D[Exploitation]
D --> E[Post-Exploitation]
E --> F[Pivoting]
F --> G[Privilege Escalation]
G --> H[Objective Completion]
style A fill:#ff6b6b,stroke:#333,stroke-width:2px
Reconnaissance in the Kill Chain
| Kill Chain Phase | Reconnaissance Activities |
|---|---|
| Reconnaissance | Passive and active information gathering |
| Weaponization | N/A (not part of recon) |
| Delivery | N/A (not part of recon) |
| Exploitation | N/A (not part of recon) |
| Installation | N/A (not part of recon) |
| Command & Control | N/A (not part of recon) |
| Actions on Objectives | N/A (not part of recon) |
Reconnaissance in PTES (Penetration Testing Execution Standard)
| PTES Phase | Description | Recon Activities |
|---|---|---|
| 1. Intelligence Gathering | Pre-engagement and intelligence collection | Passive recon, OSINT, footprinting |
| 2. Threat Modeling | Analyzing attack surface | Attack surface mapping, risk assessment |
| 3. Vulnerability Analysis | Identifying weaknesses | Active recon, scanning, enumeration |
| 4. Exploitation | Gaining access | N/A |
| 5. Post-Exploitation | Maintaining access | N/A |
| 6. Reporting | Documenting findings | N/A |
How Recon Feeds Subsequent Phases
- To Scanning: Recon identifies targets and services to scan
- To Enumeration: Recon reveals which services need detailed enumeration
- To Vulnerability Analysis: Recon provides version information for exploit matching
- To Exploitation: Recon identifies the most promising attack vectors
- To Post-Exploitation: Recon provides context for lateral movement planning
OSCP Exam Tips
Critical Exam Advice
1. Start with Passive Recon
# Always begin with passive techniques
whois target.com
dig target.com ANY
# Check for subdomains
dig ns target.com
dig mx target.com
2. Efficient Nmap Usage
# Quick initial scan (fast, covers common ports)
nmap -sV -sC -O --top-ports 100 -T4 target_ip
# If you find interesting services, do a full scan
nmap -sS -p- -T4 target_ip
# Deep service detection on open ports
nmap -sV -sC -p <open_ports> target_ip
3. Document Everything
- Save all nmap output with
-oAflag - Keep a running notes file for each target
- Screenshot important findings
- Record commands that produce useful results
4. Time Management
- Spend no more than 2-4 hours on total recon
- If stuck, pivot to exploitation of known findings
- Don’t let perfect recon prevent good progress
5. Common OSCP Recon Targets
| Service | What to Look For | Common Exploits |
|---|---|---|
| HTTP/HTTPS | Directory listing, backup files, admin panels, CMS versions | CMS exploits, file inclusion, default credentials |
| SMB | Anonymous access, shares, user enumeration | MS17-010, default shares, null sessions |
| SSH | Version info, weak ciphers | Version-specific exploits, brute force |
| FTP | Anonymous login, version info | Version-specific exploits, anonymous access |
| MySQL | Remote access, version info | Default credentials, version exploits |
| DNS | Zone transfers, misconfigurations | AXFR, DNS rebinding |
| SNMP | Community strings, MIB data | Default community strings, information disclosure |
6. Quick Recon Checklist for Exam
# 1. Quick scan all targets
for ip in 10.10.10.{1..5}; do
nmap -sV -sC -O --top-ports 100 -T4 -oA quick_$ip $ip
done
# 2. Check for common services
nmap --script=http-enum -p 80,443,8080 target_ip
# 3. Web directory brute force
gobuster dir -u http://target_ip -w /usr/share/wordlists/dirb/common.txt -t 50
# 4. Check for SMB
nmap -p 445 --script=smb-enum-shares,smb-enum-users target_ip
# 5. Check for SNMP
nmap -p 161 --script=snmp-info target_ip
7. Red Flags That Mean “Exploit Now”
- Service version matches a known exploit in ExploitDB
- Default credentials work
- Directory listing reveals sensitive files
- Backup files (.bak, .old, .sql) are accessible
- Configuration files are exposed
- Admin panel is accessible without authentication
Common Exam Mistakes to Avoid
- Skipping passive recon: Always check WHOIS and DNS first
- Not saving output: Use
-oAfor all nmap scans - Ignoring less common ports: Full port scan (
-p-) is often necessary - Not enumerating services: Open ports are just the beginning
- Spending too long on one target: Balance time across all machines
- Not documenting: You will need your notes for the report
Summary
Reconnaissance is the foundation of successful penetration testing. Key takeaways:
- Start passive, go active: Always begin with passive techniques before interacting directly with targets
- Document everything: Your notes are your most valuable asset during the exam
- Time management is critical: Don’t let recon paralysis prevent progress
- Know when to pivot: Transition to exploitation when you have promising findings
- Stay within scope: Legal and ethical boundaries are non-negotiable
- Use the right tools: Nmap, WHOIS, DNS tools, and web enumeration tools are your primary weapons
- Think like an attacker: Look for misconfigurations, default settings, and exposed information
Mastering reconnaissance fundamentals will significantly improve your OSCP exam performance and your overall penetration testing skills.
References and Further Reading
- Nmap Manual
- OSCP Exam Rules
- Penetration Testing Execution Standard (PTES)
- Cyber Kill Chain
- OWASP Testing Guide
Last Updated: 2026-09-01 Chapter 03: Information Gathering - Topic 01: Reconnaissance Fundamentals