Encrypt client-side session information
Summary
The system must encrypt and verify client-side session information (ViewState).
Description
Using client-side encryption makes it less likely for the data session to be intercepted by hostile third parties.
Supported In
This requirement is verified in following services
| Plan | Supported |
|---|---|
| Essential | 🟢 |
| Advanced | 🟢 |
References
- 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
- 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
Vulnerabilities
Free trial
Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.