Cryptographic function errors always need to result in rejection. It is also useful to log (associated with the user's identity if possible) and flag these as possibly malicious activity for further analysis, or as input for application intrusion detection systems.
NB: Unlike other cards in this suit, CR 5 assumes that cryptographic functions are in place, however they do not correctly respond to errors.
Kyle can bypass cryptographic controls because they do not fail securely (i.e. they default to unprotected)
Owasp ASVS (4.0): 1.9.1 ,6.2.1 ,9.1.3 ,9.2.2
Capec:
Owasp SCP: 103,145
Owasp Appsensor:
Safecode: 21,29
ASVS V1.9 - Communications Architectural Requirements
ASVS V9.1 - Communications Security Requirements
ASVS V9.2 - Server Communications Security Requirements
Password Guessing/Brute Force Attacks
Session Hijacking (Man-in-the-Middle)
Loading comments 0%