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

Automating API security

When we consider all the possible ways in which an API can be vulnerable to attack, it may feel like a lost cause—with so many attack vectors, frameworks, access-control schemes, coding flaws, and so on, where do we even start?

The really good news is that a vast number of flaws are easily detectable using automated tools during the development lifecycle. A typical distribution of flaw occurrence (by count) against the difficulty of detection is shown here:

Figure 8.11 – Sweet spot for flaw detection

Figure 8.11 – Sweet spot for flaw detection

The sweet spot is where most of the low-hanging fruit exists—these are very basic flaws that can be detected easily. For example, all the OpenAPI definition flaws identified in the previous section can be detected in real time, with precision, at various stages in the lifecycle (IDEs, repositories, and CI/CD pipelines). Next, let us take a look at some quick wins from the integration API security checks into...