OWASP Annotated Application Security Verification Standard
latest

Browse by chapter:

  • v1 Architecture, design and threat modelling
  • v2 Authentication verification requirements
  • v3 Session management verification requirements
  • v4 Access control verification requirements
  • v5 Malicious input handling verification requirements
  • v6 Output encoding / escaping
  • v7 Cryptography at rest verification requirements
  • v8 Error handling and logging verification requirements
  • v9 Data protection verification requirements
    • 9.1 Sensitive data does not get cached
    • 9.2 Sensitive data is identified and access policy exists and is enforced
    • 9.3 Sensitive data does not get sent in the URL
    • 9.4 Temporary client caches of sensitive data are properly cleaned up
    • 9.5 Temporary server caches of sensitive data are properly cleaned up
    • 9.6 Sensitive data can be removed after required retention period
    • 9.7 Minimal parameters are sent to untrusted systems
    • 9.8 Abnormal behaviour is detectable
    • 9.9 Client side storage does not contain secrets
    • 9.10 Accessing sensitive data is logged
    • 9.11 Sensitive data is rapidly sanitized from memory
  • v10 Communications security verification requirements
  • v11 HTTP security configuration verification requirements
  • v12 Security configuration verification requirements
  • v13 Malicious controls verification requirements
  • v14 Internal security verification requirements
  • v15 Business logic verification requirements
  • v16 Files and resources verification requirements
  • v17 Mobile verification requirements
  • v18 Web services verification requirements
  • v19 Configuration

Browse by level:

  • Level 1: Opportunistic
  • Level 2: Standard
  • Level 3: Advanced
OWASP Annotated Application Security Verification Standard
  • Docs »
  • v9 Data protection verification requirements
  • Edit on GitHub

v9 Data protection verification requirementsΒΆ

  • 9.1 Sensitive data does not get cached
  • 9.2 Sensitive data is identified and access policy exists and is enforced
  • 9.3 Sensitive data does not get sent in the URL
  • 9.4 Temporary client caches of sensitive data are properly cleaned up
  • 9.5 Temporary server caches of sensitive data are properly cleaned up
  • 9.6 Sensitive data can be removed after required retention period
  • 9.7 Minimal parameters are sent to untrusted systems
  • 9.8 Abnormal behaviour is detectable
  • 9.9 Client side storage does not contain secrets
  • 9.10 Accessing sensitive data is logged
  • 9.11 Sensitive data is rapidly sanitized from memory
Next Previous

© Copyright 2015, Boy Baukema Revision 471fcb0a.

Built with Sphinx using a theme provided by Read the Docs.