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

Managing the design-first process in the real world

In Chapter 8, Shift-Left for API Security, we examined the concepts associated with design-first API development, namely that the API development team starts with the API design first (via an OpenAPI definition) and then proceeds to implement the API code. There are numerous benefits to adopting this approach, including the following:

  • Incorporating security early: Incorporating security early in the design lifecycle ensures that designers and developers are forced to consider how they will secure their APIs (for example, an OAS definition can be parsed to check if a security method has been specified and generate a warning if not). This makes it harder to leave security considerations for a later stage in the lifecycle.
  • Automated document generation: A well-formed OAS definition can be used to generate comprehensive API documentation for an API developer portal, making it easier for consumers to integrate with the API...