Guides › Cybersecurity
Ethical Hacking Complete Roadmap for Beginners
Learn ethical hacking step by step, including networking, Linux, reconnaissance, web security testing, vulnerability assessment, reporting, and hands-on practice in authorized labs.
Ethical Hacking Complete Roadmap for Beginners
Introduction
Ethical hacking is the authorized assessment of systems to identify security weaknesses and help organizations fix them. Ethical hackers work within a defined scope and follow written rules of engagement.
Important: Only test systems you own or have explicit permission to assess.
1. Understand Ethical Hacking
Learn the differences between:
- Ethical hacking: Authorized security testing.
- Penetration testing: A scoped assessment that validates security risks.
- Vulnerability assessment: Identifying and prioritizing weaknesses.
- Red teaming: A goal-oriented simulation of adversary behavior.
- Defensive security: Protecting, detecting, and responding to threats.
2. Learn Networking
Study:
- IP addressing and subnetting.
- TCP and UDP.
- DNS and DHCP.
- HTTP and HTTPS.
- Ports and network services.
- Routing and firewalls.
- TLS certificates.
- Proxies and VPN concepts.
Practice explaining how a browser resolves a domain and establishes a secure connection.
3. Learn Linux
Learn how to:
- Navigate directories.
- Read files and search text.
- Manage users and permissions.
- Inspect processes and services.
- Understand logs.
- Install and update packages.
- Use SSH securely.
- Write basic shell scripts.
Practice in a local virtual machine that you control.
4. Learn Windows Fundamentals
Study:
- Users, groups, and permissions.
- Services and scheduled tasks.
- Windows event logs.
- Updates and endpoint protection.
- PowerShell fundamentals.
- Active Directory concepts.
- Secure configuration and identity management.
5. Learn Programming and Scripting
Useful skills include:
- Python for automation and data processing.
- Bash for Linux tasks.
- PowerShell for Windows administration.
- JavaScript for understanding web applications.
- SQL for understanding database queries.
Write small scripts to parse your own logs, validate input, or summarize authorized test results.
6. Set Up a Legal Practice Lab
Use isolated virtual machines, intentionally vulnerable applications, or designated training platforms.
A safe lab should:
- Run on a computer or environment you control.
- Use isolated networking where appropriate.
- Contain no real user data or production credentials.
- Use snapshots so you can restore the environment.
- Stay within the lab's permitted scope.
Never expose intentionally vulnerable systems publicly.
7. Understand Reconnaissance
Reconnaissance collects information relevant to an authorized assessment.
Learn the distinction between:
- Passive research using permitted public information.
- Active checks that send traffic to a target.
For every engagement, define the permitted domains, IP addresses, time window, and excluded systems before testing.
8. Learn Vulnerability Assessment
Learn how to:
- Identify software versions and configurations in scope.
- Review vendor security advisories.
- Understand vulnerability severity.
- Validate findings safely.
- Distinguish confirmed issues from scanner false positives.
- Recommend fixes and compensating controls.
Avoid intrusive checks unless the written scope explicitly allows them.
9. Web Application Security
Study common weakness categories:
- Broken access control.
- Injection flaws.
- Cross-site scripting (XSS).
- Authentication and session weaknesses.
- Cross-site request forgery (CSRF).
- Security misconfiguration.
- Vulnerable dependencies.
- Insecure file upload handling.
Use a deliberately vulnerable local application to understand each issue and practice fixing it.
10. Secure Authentication Testing
Learn how to assess your own test application for:
- Weak password policies.
- Missing multifactor authentication.
- Insecure account recovery.
- Poor session expiration.
- Missing rate limits.
- Inadequate authorization checks.
Use test accounts only. Do not attempt to access accounts that belong to other people.
11. SQL Injection: Understand and Prevent
SQL injection happens when untrusted input changes the structure of a database query.
Prevention:
- Use parameterized queries.
- Avoid string concatenation for SQL.
- Apply least-privilege database permissions.
- Validate input according to business requirements.
- Avoid exposing detailed database errors to users.
Practice on an intentionally vulnerable training application and verify that the corrected version uses safe query parameters.
12. Security Tools
Learn the purpose and responsible use of:
- Wireshark for packet analysis.
- Nmap for authorized network discovery.
- OWASP ZAP for web application testing.
- Burp Suite for web request analysis.
- OpenVAS or similar tools for vulnerability assessment.
- Git for tracking test scripts and documentation.
Tool output is not proof by itself. Verify findings and understand the impact before reporting them.
13. Network Traffic Analysis
In a lab, learn to:
- Capture traffic from your own test environment.
- Identify protocols and endpoints.
- Understand DNS requests and TCP connections.
- Recognize unencrypted traffic.
- Inspect TLS connection metadata.
- Document suspicious patterns.
Do not capture other people's traffic without appropriate authorization.
14. Reporting Findings
A professional security report should include:
- Executive summary.
- Scope and limitations.
- Methodology.
- Finding title and severity.
- Affected component.
- Evidence gathered safely.
- Reproduction steps within the authorized environment.
- Potential impact.
- Recommended remediation.
- Retest results.
Avoid including secrets or unnecessary personal data in reports.
15. Remediation and Retesting
A security assessment is incomplete without useful remediation guidance.
For each finding:
- Explain the root cause.
- Recommend a specific fix.
- Identify relevant configuration or code changes.
- Retest the fix.
- Record any remaining risk.
16. Build a Beginner Portfolio
Portfolio project ideas:
- Secure a local Linux server.
- Analyze sample security logs.
- Create a password-policy checker.
- Build a secure login demo with MFA concepts.
- Document common web vulnerabilities in a local lab.
- Create a vulnerability-report template.
- Harden a sample web application.
- Write a guide for securing a home network.
Publish sanitized reports and code. Never publish credentials, real target data, or unauthorized findings.
17. Suggested Learning Schedule
- Weeks 1–2: Networking and operating systems.
- Weeks 3–4: Linux, Windows, and Python fundamentals.
- Weeks 5–6: Web architecture and security basics.
- Weeks 7–8: Authorized lab practice and defensive fixes.
- Weeks 9–10: Vulnerability assessment and reporting.
- Weeks 11–12: Portfolio projects and review.
Adjust the schedule to your prior experience and available study time.
18. Ethical and Legal Responsibilities
- Obtain explicit authorization.
- Follow the written scope.
- Respect privacy and confidentiality.
- Avoid unnecessary service disruption.
- Stop if you encounter out-of-scope systems or sensitive data.
- Report findings through the agreed channel.
- Follow applicable laws and platform rules.
Conclusion
Ethical hacking combines technical knowledge, careful testing, clear reporting, and responsible behavior. Start with networking and operating systems, practice in legal labs, and focus on helping organizations reduce risk.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.