Signing in does not approve every sensitive action. Bind authorization to specific content and user intent.
Evaluation approach
Show relevant amount, destination or privilege changes. The server compares approved and executed content.
Application example
Changing a recipient after approval must invalidate that approval.
Limits and considerations
Client-screen confirmation does not replace server enforcement.
What should the server execute?
Use the same amount and destination that were approved. Later client fields must not broaden approval; changed requests need new authorization.
Checks and decisions
- Define approved fields
- Reject changes
- Test server outcomes
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.