Educational guidance only. This article is not legal advice, an audit conclusion or an authorization to test systems.
Check permission on each action
Authentication establishes identity. Authorization decides what that identity may do. A hidden button is not an access control; the receiving system must enforce permission for every protected action.
Protect session and input boundaries
Use appropriate session lifetimes, secure transport and safe cookie settings. Validate input, use parameterized data access and encode output for its context. Different attack classes need different controls.
Review real workflows
Include account recovery, role changes, checkout and sensitive data export in an authorized review. Use safe test accounts and data; do not test customer systems without explicit permission.