Validation and Business Logic Documentation
V2.1.1
Verify that the application's documentation defines input validation rules for how to check the validity of data items against an expected structure. This could be common data formats such as credit card numbers, email addresses, telephone numbers, or it could be an internal data format.
Required for Level 1, 2 and 3
Related CAPEC™ Requirements
CAPEC™ (3.9): 113, 120, 126, 137, 140, 152, 153, 160, 165, 19, 267, 272, 28, 3, 4, 43, 48, 52, 586, 64, 71, 72, 77, 78, 79, 80
V2.1.2
Verify that the application's documentation defines how to validate the logical and contextual consistency of combined data items, such as checking that suburb and ZIP code match.
Required for Level 2 and 3
Related CAPEC™ Requirements
CAPEC™ (3.9): 137, 152, 153, 19, 28
V2.1.3
Verify that expectations for business logic limits and validations are documented, including both per-user and globally across the application.
Required for Level 2 and 3
Related CAPEC™ Requirements
CAPEC™ (3.9): 137, 152, 153, 19, 212, 28, 43, 77
Disclaimer
Credit via OWASP ASVS.For more information visit: The OWASP ASVS Project or Github respository.. OWASP ASVS is under the Creative Commons Attribution-Share Alike v4.0 license.
