ethical-hacking-methodology

⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.

Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:

1. Ask the user to state the exact target URL, IP, account, or resource.
2. Ask the user to confirm written authorization and the permitted scope.
3. Show the exact command(s) and explain their expected effect.
4. Wait for explicit confirmation in the current conversation.

Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.

AUTHORIZED USE ONLY: Use this skill only for authorized penetration testing engagements, defensive validation, or controlled educational environments.

Ethical Hacking Methodology

Purpose

Master the complete penetration testing lifecycle from reconnaissance through reporting. This skill covers the five stages of ethical hacking methodology, essential tools, attack techniques, and professional reporting for authorized security assessments.

Prerequisites

Required Environment

• Kali Linux installed (persistent or live)
• Network access to authorized targets
• Written authorization from system owner

Required Knowledge

• Basic networking concepts
• Linux command-line proficiency
• Understanding of web technologies
• Familiarity with security concepts

Outputs and Deliverables

1. Reconnaissance Report - Target information gathered
2. Vulnerability Assessment - Identified weaknesses
3. Exploitation Evidence - Proof of concept attacks
4. Final Report - Executive and technical findings

Core Workflow

Phase 1: Understanding Hacker Types

Classification of security professionals:

White Hat Hackers (Ethical Hackers)

• Authorized security professionals
• Conduct penetration testing with permission
• Goal: Identify and fix vulnerabilities
• Also known as: penetration testers, security consultants

Black Hat Hackers (Malicious)

• Unauthorized system intrusions
• Motivated by profit, revenge, or notoriety
• Goal: Steal data, cause damage
• Also known as: crackers, criminal hackers

Grey Hat Hackers (Hybrid)

• May cross ethical boundaries
• Not malicious but may break rules
• Often disclose vulnerabilities publicly
• Mixed motivations

Other Classifications

• Script Kiddies: Use pre-made tools without understanding
• Hacktivists: Politically or socially motivated
• Nation State: Government-sponsored operatives
• Coders: Develop tools and exploits

Phase 2: Reconnaissance

Gather information without direct system interaction:

Passive Reconnaissance

# WHOIS lookup
whois target.com
 
# DNS enumeration
nslookup target.com
dig target.com ANY
dig target.com MX

Google Hacking (OSINT)

Google Hacking Database Categories:

• Files containing passwords
• Sensitive directories
• Web server detection
• Vulnerable servers
• Error messages
• Login portals

Social Media Reconnaissance

• LinkedIn: Organizational charts, technologies used
• Twitter: Company announcements, employee info
• Facebook: Personal information, relationships
• Job postings: Technology stack revelations

Phase 3: Scanning

Active enumeration of target systems:

Host Discovery

Port Scanning

Service Enumeration

Common Port Reference

Phase 4: Vulnerability Analysis

Identify exploitable weaknesses:

Automated Scanning

Web Application Testing (OWASP)

• SQL Injection
• Cross-Site Scripting (XSS)
• Broken Authentication
• Security Misconfiguration
• Sensitive Data Exposure
• XML External Entities (XXE)
• Broken Access Control
• Insecure Deserialization
• Using Components with Known Vulnerabilities
• Insufficient Logging & Monitoring

Manual Techniques

Phase 5: Exploitation

Actively exploit discovered vulnerabilities:

Metasploit Framework

Password Attacks

Web Exploitation

Phase 6: Maintaining Access

Establish persistent access:

Backdoors

Privilege Escalation

Covering Tracks (Ethical Context)

• Document all actions taken
• Maintain logs for reporting
• Avoid unnecessary system changes
• Clean up test files and backdoors

Phase 7: Reporting

Document findings professionally:

Report Structure

1. Executive Summary

   • High-level findings
   • Business impact
   • Risk ratings
   • Remediation priorities

2. Technical Findings

   • Vulnerability details
   • Proof of concept
   • Screenshots/evidence
   • Affected systems

3. Risk Ratings

   • Critical: Immediate action required
   • High: Address within 24-48 hours
   • Medium: Address within 1 week
   • Low: Address within 1 month
   • Informational: Best practice recommendations

4. Remediation Recommendations

   • Specific fixes for each finding
   • Short-term mitigations
   • Long-term solutions
   • Resource requirements

5. Appendices

   • Detailed scan outputs
   • Tool configurations
   • Testing timeline
   • Scope and methodology

Phase 8: Common Attack Types

Phishing

• Email-based credential theft
• Fake login pages
• Malicious attachments
• Social engineering component

Malware Types

• Virus: Self-replicating, needs host file
• Worm: Self-propagating across networks
• Trojan: Disguised as legitimate software
• Ransomware: Encrypts files for ransom
• Rootkit: Hidden system-level access
• Spyware: Monitors user activity

Network Attacks

• Man-in-the-Middle (MITM)
• ARP Spoofing
• DNS Poisoning
• DDoS (Distributed Denial of Service)

Phase 9: Kali Linux Setup

Install penetration testing platform:

Hard Disk Installation

1. Download ISO from kali.org
2. Boot from installation media
3. Select "Graphical Install"
4. Configure language, location, keyboard
5. Set hostname and root password
6. Partition disk (Guided - use entire disk)
7. Install GRUB bootloader
8. Reboot and login

Live USB (Persistent)

Phase 10: Ethical Guidelines

Legal Requirements

• Obtain written authorization
• Define scope clearly
• Document all testing activities
• Report all findings to client
• Maintain confidentiality

Professional Conduct

• Work ethically with integrity
• Respect privacy of data accessed
• Avoid unnecessary system damage
• Execute planned tests only
• Never use findings for personal gain

Quick Reference

Penetration Testing Lifecycle

Essential Commands

Constraints and Limitations

Authorization Required

• Never test without written permission
• Stay within defined scope
• Report unauthorized access attempts

Professional Standards

• Follow rules of engagement
• Maintain client confidentiality
• Document methodology used
• Provide actionable recommendations

Troubleshooting

Scans Blocked

Solutions:

1. Use slower scan rates
2. Try different scanning techniques
3. Use proxy or VPN
4. Fragment packets

Exploits Failing

Solutions:

1. Verify target vulnerability exists
2. Check payload compatibility
3. Adjust exploit parameters
4. Try alternative exploits

When to Use

This skill is applicable to execute the workflow or actions described in the overview.