Checklist catalog
Access control
Whether each new route or handler checks who may call it, including who owns the IDs it takes, tenant isolation and roles.
- Check run:
Axon Shaft / access-control - How it checks: A script built into the action gathers facts, and the model judges them.
- Suits: Services and APIs, Web front ends
- In templates: Security review, Strict review, Node or Bun API, Python service
What it looks for
- New routes with no check on who may call them
- IDs from the request used without checking who owns them
- Data that can cross from one tenant to another
- Missing role checks
A finding might read: GET /invoices/:id doesn't check the invoice belongs to the caller
Files it runs on
It runs only when a changed file matches one of these, and is skipped otherwise.
**/*{route,router,handler,controller,middleware,policy,policies,guard,resolver}***/{routes,api,handlers,controllers,middleware,middlewares,policies}/**
Last updated on