# The Web Application Hacker's Handbook Based off of the original *Web Application Hacker's Handbook*, this project was revamped as a free online training site at . The author of the original books worked in conjunction with Portswigger to create the Web Security Academy. The below checklist is meant as a methodology to complement their training. ## Task Checklist ### Recon and analysis * [ ] Map visible content * [ ] Discover hidden & default content * [ ] Test for debug parameters * [ ] Identify data entry points * [ ] Identify the technologies used * [ ] Map the attack surface ### Test handling of Identity and Access Management (IAM) * [ ] Authentication * [ ] Test password quality rules * [ ] Test for username enumeration * [ ] Test resilience to password guessing * [ ] Test any account recovery function * [ ] Test any "remember me" function * [ ] Test any impersonation function * [ ] Test username uniqueness * [ ] Check for unsafe distribution of credentials * [ ] Test for fail-open conditions * [ ] Test any multi-stage mechanisms * [ ] Session handling * [ ] Test tokens for meaning * [ ] Test tokens for predictability * [ ] Check for insecure transmission of tokens * [ ] Check for disclosure of tokens in logs * [ ] Check mapping of tokens to sessions * [ ] Check session termination * [ ] Check for session fixation * [ ] Check for cross-site request forgery * [ ] Check cookie scope * [ ] Access controls * [ ] Understand the access control requirements * [ ] Test effectiveness of controls, using multiple accounts if possible * [ ] Test for insecure access control methods (request parameters, Referer header, etc) ### Test handling of input * [ ] Fuzz all request parameters * [ ] Test for SQL injection * [ ] Identify all reflected data * [ ] Test for reflected XSS * [ ] Test for HTTP header injection * [ ] Test for arbitrary redirection * [ ] Test for stored attacks * [ ] Test for OS command injection * [ ] Test for path traversal * [ ] Test for script injection * [ ] Test for file inclusion * [ ] Test for SMTP injection * [ ] Test for native software flaws (buffer overflow, integer bugs, format strings) * [ ] Test for SOAP injection * [ ] Test for LDAP injection * [ ] Test for XPath injection ### Test application logic * [ ] Identify the logic attack surface * [ ] Test transmission of data via the client * [ ] Test for reliance on client-side input validation * [ ] Test any thick-client components (Java, ActiveX, Flash) * [ ] Test multi-stage processes for logic flaws * [ ] Test handling of incomplete input * [ ] Test trust boundaries * [ ] Test transaction logic ### Assess application hosting * [ ] Test segregation in shared infrastructures * [ ] Test segregation between ASP-hosted applications * [ ] Test for web server vulnerabilities * [ ] Default credentials * [ ] Default content * [ ] Dangerous HTTP methods * [ ] Proxy functionality * [ ] Virtual hosting misconfiguration * [ ] Bugs in web server software ### Miscellaneous tests * [ ] Check for DOM-based attacks * [ ] Check for frame injection * [ ] Check for local privacy vulnerabilities * [ ] Persistent cookies * [ ] Caching * [ ] Sensitive data in URL parameters * [ ] Forms with autocomplete enabled * [ ] Follow up any information leakage * [ ] Check for weak SSL ciphers ## References * * If you like this content and would like to see more, please consider [buying me a coffee](https://www.buymeacoffee.com/zweilosec)! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://zweilosec.gitbook.io/hackers-rest/web/web-notes/the-web-application-hackers-handbook.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.