OWASP Annotated Application Security Verification Standard
latest

Browse by chapter:

  • v1 Architecture, design and threat modelling
    • 1.1 All components are identified
    • 1.2 All dependencies are identified
    • 1.3 A high-level architecture as been defined
    • 1.4 All components are defined
    • 1.5 All dependant components are defined
    • 1.6 A STRIDE threat model has been produced
    • 1.7 Central implementation for security controls
    • 1.8 Components are segregated
    • 1.9 Clear separation between data, controller and display
    • 1.10 Client side logic does not contain secrets
  • 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
  • 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 »
  • v1 Architecture, design and threat modelling
  • Edit on GitHub

v1 Architecture, design and threat modellingΒΆ

  • 1.1 All components are identified
  • 1.2 All dependencies are identified
  • 1.3 A high-level architecture as been defined
  • 1.4 All components are defined
  • 1.5 All dependant components are defined
  • 1.6 A STRIDE threat model has been produced
  • 1.7 Central implementation for security controls
  • 1.8 Components are segregated
  • 1.9 Clear separation between data, controller and display
  • 1.10 Client side logic does not contain secrets
Next Previous

© Copyright 2015, Boy Baukema. Revision 471fcb0a.

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