Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01List roles, resources and privileged actions
- 02Trace server-side checks for each endpoint
- 03Test object identifiers owned by another account
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Centralize policy decisions where practical
- 02Deny by default and scope database access
- 03Check authorization after every state transition
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Run horizontal and vertical privilege tests
- 02Call endpoints without the intended UI path
- 03Confirm logs capture denied high-risk actions
Common pitfall
A shortcut to avoid
Hiding buttons or routes in the client does not prevent direct requests to the underlying endpoint.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.