Attack surface map of the code you own
Most teams can list their public pages but not the admin routes, webhook receivers, file importers, queue consumers and debug endpoints that also accept input from outside. Mapping every place untrusted data enters your code tells you where the next six months of security effort should go, and it is the first thing a penetration tester will ask for.
First tasks
- Export the full route list from each service's router
- Add webhooks, queue consumers, file imports and scheduled jobs that read external data
- Mark each entry point with its audience and whether it touches money or personal data
- Raise tickets for endpoints that should not exist or lack authentication