Common web page checklist

This is at the heart of the checklist for web intrusion testing. As mentioned in the preceding workflow, you will need to apply this checklist to every page, regardless of its nature. Let's dive in:

1. Identify the entry points to the web page (which lead to the backend; remember that we will use the entry points in the next steps), including:
   • URLs
   • Headers (for example, cookie, URL referrer, and so on)
   • HTML controls (drop-down list, radio button, hidden input, textbox, and so on)
2. Check all of the backend or third-party web services and web APIs called using Burp Target.
3. Force the URL into HTTP mode, and see if it works, or if it stays in HTTPS.
4. Try to make the page generate an error; in another words, do error messages reveal clues to hackers?
5. Test for logic flaws (for example, purchasing an item with zero dollars, or applying a randomly generated...