Inventory Deployed APIs and Prevent Version Drift
Reconcile contracts, source routes, gateway mounts, deployed hosts, and retirement plans to find weaker alternate entry points.
You’re reading a preview. Premium includes the full lesson and specialist practice. View the full curriculum.
Review the API that is deployed, not only the one documented
An API inventory connects routes and methods to deployed hosts, versions, owners, data stores, consumers, and retirement plans. An OpenAPI document is one input, not proof that every reachable endpoint appears in it or follows its security requirements.
MediaDesk protects /api/v2/ with authentication middleware. A new /api/v3/ router is mounted outside that chain and exposes analytics. The handlers look familiar, but the middleware that established identity never runs on the new mount.
app.use('/api/v2', authenticate, v2Router);
app.use('/api/v3', v3Router);
The first question is whether the v3 route is reachable in the deployment. The next is whether another middleware or service policy enforces the missing guarantee. A source omission becomes a demonstrated exposure when the complete reachable path lacks the required control.