Book Image

Defending APIs

By : Colin Domoney
Book Image

Defending APIs

By: Colin Domoney

Overview of this book

Along with the exponential growth of API adoption comes a rise in security concerns about their implementation and inherent vulnerabilities. For those seeking comprehensive insights into building, deploying, and managing APIs as the first line of cyber defense, this book offers invaluable guidance. Written by a seasoned DevSecOps expert, Defending APIs addresses the imperative task of API security with innovative approaches and techniques designed to combat API-specific safety challenges. The initial chapters are dedicated to API building blocks, hacking APIs by exploiting vulnerabilities, and case studies of recent breaches, while the subsequent sections of the book focus on building the skills necessary for securing APIs in real-world scenarios. Guided by clear step-by-step instructions, you’ll explore offensive techniques for testing vulnerabilities, attacking, and exploiting APIs. Transitioning to defensive techniques, the book equips you with effective methods to guard against common attacks. There are plenty of case studies peppered throughout the book to help you apply the techniques you’re learning in practice, complemented by in-depth insights and a wealth of best practices for building better APIs from the ground up. By the end of this book, you’ll have the expertise to develop secure APIs and test them against various cyber threats targeting APIs.
Table of Contents (19 chapters)
1
Part 1: Foundations of API Security
6
Part 2: Attacking APIs
10
Part 3: Defending APIs

Learning the key skills of API attacking

The best way to learn how to hack APIs is by getting hands-on experience with hacking tools and a vulnerable API. We will start by building our own API hacking laboratory using many of the popular tools we have explored, and then use this laboratory to attack some deliberately vulnerable API-based applications. This hands-on approach will equip you with the skills necessary to attack real-world APIs in the upcoming chapters.

Building a laboratory

The choice of a personal laboratory is somewhat dependent on individual preferences for OSs and favored tools. For most users, I would recommend three core components: a versatile modern editor (such as Visual Studio Code), a container runtime environment (such as Docker), and the ubiquitous Kali Linux hacking OS.

Visual Studio Code

The choice of a code editor and/or integrated development environment (IDE) is a deeply personal one (as anyone who remembers the vi versus emacs debates of...