liveBook · Manning

Ghost api

As explained in Secure APIs

A ghost API is an API exposed by a library, infrastructure component, or other third party rather than deliberately created and managed by the organization.

A ghost API is an API exposed by a third-party library, infrastructure component, or other system rather than deliberately created and managed by the organization. section 3.7

Ghost APIs are part of API sprawl: undocumented or poorly tracked interfaces that can remain outside normal security assessment. When attackers discover less-protected APIs, data breaches can result. section 3.5 section 3.7

Finding an undocumented interface

An API observability tool can inspect which requests API servers accept and reveal undocumented attack surfaces. Add discovered interfaces to an API catalog, assess their security, and apply the same validation standards used for other APIs. section 3.7

How Secure APIs covers it

How deep it goes
Defines ghost APIs, distinguishes neighboring API-sprawl types, and points to discovery and inventory practices without detailing implementation.
Examples
Uses API-sprawl comparisons and traffic inspection that reveals requests accepted by API servers.
What you can do after
Operate/configure API discovery and cataloging practices to identify undocumented third-party interfaces and assess their security.
How it connects
Connects ghost APIs with API sprawl, shadow APIs, zombie APIs, API catalogs, API observability, 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.