Book Image

Mastering Kali Linux for Web Penetration Testing

By : Michael McPhee
Book Image

Mastering Kali Linux for Web Penetration Testing

By: Michael McPhee

Overview of this book

You will start by delving into some common web application architectures in use, both in private and public cloud instances. You will also learn about the most common frameworks for testing, such as OWASP OGT version 4, and how to use them to guide your efforts. In the next section, you will be introduced to web pentesting with core tools and you will also see how to make web applications more secure through rigorous penetration tests using advanced features in open source tools. The book will then show you how to better hone your web pentesting skills in safe environments that can ensure low-risk experimentation with the powerful tools and features in Kali Linux that go beyond a typical script-kiddie approach. After establishing how to test these powerful tools safely, you will understand how to better identify vulnerabilities, position and deploy exploits, compromise authentication and authorization, and test the resilience and exposure applications possess. By the end of this book, you will be well-versed with the web service architecture to identify and evade various protection mechanisms that are used on the Web today. You will leave this book with a greater mastery of essential test techniques needed to verify the secure design, development, and operation of your customers' web applications.
Table of Contents (13 chapters)

The X-factor - XML and XPath injections

Some app developers are eschewing SQL for new, open-standards-based data structures written in XML. Why will someone choose this? Relational databases composed with SQL are certainly leveraging a very stable, mature technology, but sometimes data that has multiple indices of relationships is more compact when rendered and stored in XML. This needs to be balanced against the performance in the database tier. Relational databases differentiate between variable types, which means they can provide optimized treatment of those based on whether they are a string, integer, Boolean, or others. XML treats everything like a string of text, so the burden is on the Application Tier to comb over the stored data and make manipulations with more complex logic and processing overhead. There is no 100% right answer – these factors will be weighed...