+CON.10.A15 Prevention of Cross-Site Request Forgery (S)
|
CON.10.A15 Prevention of Cross-Site Request Forgery (S)
Developers SHOULD equip web applications with the security mechanisms required to distinguish between users' intended page requests and unintentionally forwarded third-party commands. At minimum, whether a secret token is required in addition to the session ID for access to protected resources and functions SHOULD be checked.
1. Vue d’ensemble
1.1 Références
1.2 Exigences identifiées
1.3 Réglementations associées
2. Exigences identifiées
Exigences
| Source |
Exigence |
3. Réglementations associées
Réglementations
| Source |
Réglementation |
Tickets liés
|