> For the complete documentation index, see [llms.txt](https://www.pentest-book.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pentest-book.com/others/master-assessment-mindmap.md).

# Master assessment mindmaps

## Web Application Pentesting Mindmap

Key areas to assess during web application security testing:

### Reconnaissance

* Subdomain enumeration
* Technology fingerprinting
* Hidden content discovery
* API endpoint mapping

### Authentication Testing

* Brute force protection
* Password policies
* Session management
* Multi-factor authentication bypass
* Account lockout mechanisms

### Authorization Testing

* Horizontal privilege escalation (IDOR)
* Vertical privilege escalation
* Function-level access control
* Insecure direct object references

### Input Validation

* SQL Injection (all types)
* XSS (Reflected, Stored, DOM)
* Command Injection
* SSRF / CSRF
* XXE Injection
* Template Injection (SSTI)

### Business Logic

* Workflow bypass
* Price manipulation
* Quantity tampering
* Feature abuse

### Infrastructure

* Server misconfigurations
* Default credentials
* Exposed admin panels
* Information disclosure

![](https://1729840239-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M5x1LJiRQvXWpt04_ee%2F-MG33U1tPKkztqqfsks0%2F-MG33dIgvN3YUZUMnKCs%2Fimage.png?alt=media\&token=b9e7d007-78ff-4f6f-9b9b-03c39dd5cffa)

## Bug Bounty Methodology

![](https://blog.it-securityguard.com/pbbt.png)

## Comprehensive Pentest Methodology

### Phase 1: Information Gathering

1. Passive reconnaissance (OSINT)
2. Active scanning and enumeration
3. Vulnerability identification

### Phase 2: Exploitation

1. Vulnerability validation
2. Exploit development/selection
3. Initial access

### Phase 3: Post-Exploitation

1. Privilege escalation
2. Persistence
3. Lateral movement
4. Data exfiltration

### Phase 4: Reporting

1. Finding documentation
2. Risk assessment
3. Remediation recommendations

![](https://1729840239-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M5x1LJiRQvXWpt04_ee%2F-MB8gbhAoFg9IFNKBZYU%2F-MB8iKf1-S8141P3waGS%2FMethodology%5B1%5D.png?alt=media\&token=20b83dc7-d8b2-4a09-b276-09042a7726e1)

## Additional Resources

* [OWASP Testing Guide](https://owasp.org/www-project-web-security-testing-guide/)
* [PortSwigger Web Security Academy](https://portswigger.net/web-security)
* [HackTricks](https://book.hacktricks.xyz/)
* [PayloadsAllTheThings](https://github.com/swisskyrepo/PayloadsAllTheThings)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pentest-book.com/others/master-assessment-mindmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
