Intoduction
Reconnaissance Vs Enumeration
Reconnaissance
is the initial, broad info-gathering phase (e.g., finding IPs or domains)
Enumeration
is a deeper, active step to extract specific details (e.g., usernames or services) after reconnaissance.
Enumeration
Enumeration is the process of gathering information about a target using active methods (like scanning) and passive methods (like OSINT). However, OSINT is separate from enumeration because it relies only on publicly available data without direct interaction with the target.
Enumeration is an iterative process, meaning you continuously gather more information based on what you already know.
The main goal is to understand the target's infrastructure rather than blindly attacking it. Many testers make the mistake of immediately brute-forcing authentication services (SSH, RDP, WinRM), which is a noisy approach that can get them blacklisted. Instead, a smarter approach is to first analyze the company's setup, security measures, and services before launching attacks
Enumeration Methodology


How to identify a company's online presence?
use SSL certificate to collect subdomains
crt.sh. This source is Certificate Transparency logs, which SSL certificate is assigned in audit-proof logs

Shodan - IP List
DNS Records
dig tool
dnsrecon tool
Cloud Resources
Publicly accessible storage (S3, Blobs, Cloud Storage) can expose sensitive data if left open.
S3 Buckets → AWS
Blobs → Azure
Cloud Storage → GCP
When testing a company's hosted servers and cloud resources, we check subdomains and IP addresses using commands like:
💡 Findings:
Some IP addresses belong to internal servers
Others are cloud services like AWS S3
🚨 Security Risk:
If S3 buckets are misconfigured, anyone can access stored files
Google Dorks (e.g.,
inurl:s3.amazonaws.com intext:"confidential") can help find exposed cloud storage
use to search on bucket : https://buckets.grayhatwarfare.com/buckets
Staff
search on LinkedIn or any sites offer jobs
Last updated