Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Burp Suite Essentials

You're reading from   Burp Suite Essentials Discover the secrets of web application pentesting using Burp Suite, the best tool for the job

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher Packt
ISBN-13 9781783550111
Length 144 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Akash Mahajan Akash Mahajan
Author Profile Icon Akash Mahajan
Akash Mahajan
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Getting Started with Burp FREE CHAPTER 2. Configuring Browsers to Proxy through Burp 3. Setting the Scope and Dealing with Upstream Proxies 4. SSL and Other Advanced Settings 5. Using Burp Tools As a Power User – Part 1 6. Using Burp Tools As a Power User – Part 2 7. Searching, Extracting, Pattern Matching, and More 8. Using Engagement Tools and Other Utilities 9. Using Burp Extensions and Writing Your Own 10. Saving Securely, Backing Up, and Other Maintenance Activities 11. Resources, References, and Links Index

Scope inclusion versus exclusion

The target scope works on URL patterns. URL patterns can either be inclusive or exclusive. An inclusive pattern will allow all URLs matching the pattern to go through. An exclusive pattern will disallow all URLs matching the pattern from proceeding further. To match the scope, Burp Suite matches URLs to the patterns defined in the included list first. This allows us to add targets easily in scope. Once a target URL pattern is matched, it is checked against in the exclusion list. This is done to ensure that we don't inadvertently trigger critical functionality. For example, if we want to attack everything and not get logged out, we can exclude the Logout page. If some functionality triggers automated e-mails to thousands of users, we don't want to annoy the users by sending e-mails while testing by mistake. We should explicitly put the mentioned URLs in the exclusion list.

Spending some quality time figuring out the scope, adding the required target...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime