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.
- 01Map sensitive data and privileged actions
- 02Review authentication, authorization and inputs
- 03Inspect headers, dependencies and secrets
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.
- 01Fix high-impact reachable risks
- 02Document owners and residual risk
- 03Prepare logging, alerting and response paths
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 negative and abuse cases
- 02Verify production configuration
- 03Retest fixed issues independently
Common pitfall
A shortcut to avoid
A clean automated dependency scan does not establish that business logic and access control are safe.
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.