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

Using the OpenAPI Specification

In Chapter 1, What Is API Security?, I described the various benefits of the design-first approach to API development: code generation, mock servers, data validation, documentation, and, of course, security (think of it as security-as-code for APIs).

We will now take a deeper look at the security constructs that can be leveraged within the OpenAPI definition of an API. There are two main categories: data definitions and security specifications.

API-first versus design-first versus code-first

In this chapter, we will make heavy use of these three terms and, given that they have a fairly specific and implicit meaning in the world of API design, I would like to disambiguate them for readers who may not have this context:

API-first: This is a business objective in which the product is built around APIs (which are invariably published) in the first instance and, from there, the user interface and so on is developed. This contrasts with the more...