liveBook · Manning

Api sprawl

As explained in Secure APIs

API sprawl is the uncontrolled proliferation of APIs, often involving duplication, undocumented interfaces, and inadequate security oversight.

API sprawl is the uncontrolled proliferation of APIs, often duplicating functionality while remaining undocumented, untracked, or insufficiently assessed for security. It creates attack surfaces that organizations may not know they have. section 3.5 section 3.7

Recognize the main forms of API sprawl:

  • Shadow APIs are released under the radar without proper testing or evaluation, often remaining undocumented and less secure. section 3.5
  • Zombie APIs are deprecated APIs or versions that remain exposed after their owners forget to retire them. section 3.5
  • Ghost APIs are exposed by third-party libraries or systems, making ownership and security oversight harder. section 3.7

A hidden attack surface

During cloud migration or application modernization, teams may publish APIs ad hoc to expose new functionality. If those interfaces bypass planning, cataloging, testing, and security assessment, attackers may discover less-protected endpoints and cause data breaches. section 3.5

How Secure APIs covers it

How deep it goes
Defines API sprawl, distinguishes three forms, and identifies catalogs, observability, design review, and testing as mitigations.
Examples
Uses ad hoc migration APIs, undocumented interfaces, deprecated exposed versions, third-party APIs, and observability-based discovery.
What it assumes
Assumes only familiarity with APIs and develops the need for inventory, documentation, lifecycle management, and uniform security controls.
What you can do after
Diagnose API sprawl by cataloging interfaces, discovering undocumented traffic, retiring obsolete versions, and assessing security throughout the SDLC.
How it connects
Connects API sprawl with shadow APIs, zombie APIs, ghost APIs, API catalogs, API observability, security by design, and zero-trust security.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.