Scribd
Upload
26 views

HOD402_Pentesting_Reference-v1

The document outlines a structured pentesting process divided into six phases: Preparation and Planning, Information Gathering, Vulnerability Analysis, Exploitation, Post-Exploitation, and Reporting. Each phase includes specific objectives, methodologies, legal considerations, and detailed planning requirements. The document emphasizes the importance of thorough documentation and communication throughout the pentesting process.

Uploaded by

thientdhe171847
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
26 views

HOD402_Pentesting_Reference-v1

The document outlines a structured pentesting process divided into six phases: Preparation and Planning, Information Gathering, Vulnerability Analysis, Exploitation, Post-Exploitation, and Reporting. Each phase includes specific objectives, methodologies, legal considerations, and detailed planning requirements. The document emphasizes the importance of thorough documentation and communication throughout the pentesting process.

Uploaded by

thientdhe171847
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

HOD402

A Reference for Pentesting Process


Phase 1: Preperation and Planning

1. Objectives

2. Scope:

o Target system: app, site, database, infrastructure …

o Known-environment testing

o Unknown-environment testing

o Out of scope

3. Methodology

4. Timeline: milestones chart , Gantt chart …

5. Legal and Compliance:

o Regulatory Compliance Considerations

o Local Restrictions

o Service-level agreement (SLA), Confidentiality, Statement of work (SOW), Master


service agreement (MSA), Non-disclosure agreement (NDA)

o Contract

o Disclaimers

6. Rules of Engagement Document

7. Team and members

8. Written Agreement (Agreement/Contract):

o Include some or all of items 1.1 to 1.7

o Costs

o Responsibilities of each party.

o Process for handling critical vulnerabilities.

9. Detailed Planning: Create a detailed project plan document, including:

o Project phases (information gathering, analysis, exploitation, reporting).

o Specific schedule for each phase.

o Task assignments for each team member.

o List of tools to be used.

1
HOD402

o Communication and progress reporting methods.

Phase 2: Information Gathering (Reconnaissance)

1. Identify Assets and Activities

2. Identify Threats by a threat modeling

3. Performing Passive Reconnaissance

4. Performing Active Reconnaissance

Phase 3: Vulnerability Analysis

1. Manual Analysis: using some frameworks and standards, such as OWASP Top 10, SANS Top
25, Misconfiguration Checks, Session Management Checks, Authentication and
Authorization Checks, Input Validation Checks, Source Code Review (if White Box), API
Testing (if applicable) …

2. Severity Assessment: Using a scoring system like CVSS (Common Vulnerability Scoring
System) to determine the severity of each vulnerability (Critical, High, Medium, Low).

Phase 4: Exploitation

1. Exploiting Network-Based Vulnerabilities

2. Exploiting Wireless Vulnerabilities

3. Exploiting Application-Based Vulnerabilities

4. Exploiting cloud, mobile and IoT systems

Phase 5: Post-Exploitation

1. Creating a Foothold
2. Maintaining Persistence After Compromising a System

Phase 6: Reporting

1. Executive Summary
2. Scope Details
3. Methodology
4. Findings
5. Remediation
6. Conclusion
7. Appendix

You might also like