The system must encrypt and verify client-side session information (ViewState).
Using client-side encryption makes it less likely for the data session to be intercepted by hostile third parties.
This requirement is verified in following services
- CAPEC™-39. Manipulating opaque client-based data tokens
- CAPEC™-74. Manipulating state
- CWE™-642. External control of critical state data
- CERT-J-LCK11-J. Avoid client-side locking when using classes that do not commit to their locking strategy
- CERT-J-MSC11-J. Do not let session information leak within a servlet
- MITRE ATT&CK®-M1041. Encrypt sensitive information
- CMMC-AC_L2-3_1_19. Encrypt CUI on mobile
- CMMC-CM_L2-3_4_9. User-installed software
- OWASP SCP-5. Access control
- OWASP MASVS-V8_11. Resilience requirements - Impede comprehension
- NIST 800-171-1_19. Encrypt CUI on mobile devices and mobile computing platforms
- OWASP ASVS-1_8_2. Data protection and privacy architecture
- CWE™-13. Misconfiguration - Password in configuration file
- OWASP ASVS-4_1_2. General access control design
- CASA-1_8_2. Data Protection and Privacy Architecture
- CASA-4_1_2. General Access Control Design
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.