Book Image

Hands-On Application Penetration Testing with Burp Suite

By : Carlos A. Lozano, Dhruv Shah, Riyaz Ahemed Walikar
Book Image

Hands-On Application Penetration Testing with Burp Suite

By: Carlos A. Lozano, Dhruv Shah, Riyaz Ahemed Walikar

Overview of this book

Burp suite is a set of graphic tools focused towards penetration testing of web applications. Burp suite is widely used for web penetration testing by many security professionals for performing different web-level security tasks. The book starts by setting up the environment to begin an application penetration test. You will be able to configure the client and apply target whitelisting. You will also learn to setup and configure Android and IOS devices to work with Burp Suite. The book will explain how various features of Burp Suite can be used to detect various vulnerabilities as part of an application penetration test. Once detection is completed and the vulnerability is confirmed, you will be able to exploit a detected vulnerability using Burp Suite. The book will also covers advanced concepts like writing extensions and macros for Burp suite. Finally, you will discover various steps that are taken to identify the target, discover weaknesses in the authentication mechanism, and finally break the authentication implementation to gain access to the administrative console of the application. By the end of this book, you will be able to effectively perform end-to-end penetration testing with Burp Suite.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Contributors
About Packt
Preface
12
Exploiting and Exfiltrating Data from a Large Shipping Corporation
Index

Differences between a bug bounty and a client-initiated pentest


Before we jump into the core details, let's first understand these two mindsets: 

  • Bug bounty pentest mindset
    • The aim is to find vulnerabilities that have an impact and fetch a good bounty
    • A complete assessment of the application doesn't need to be done
    • One bug is enough to qualify for a bounty
    • All the vulnerabilities in the application are not reported, only the ones found
    • There are no particular timelines; it can be done at the pentester's convenience
  • Client-initiated pentest mindset:
    • The aim is to ensure that all the application processes and functionalities are tested
    • There is a limited timeline in which the whole application needs to be audited
    • There is no bounty or rewards
    • There is a need to ensure that all the vulnerabilities found by a scanner are validated and reported
    • There is a need to also scope the entire application by understanding all the inter-dependencies and ensure that endpoints are well protected, since there will...