Security testing Python Web applications

3 days
On-site or online

29 Labs


10 Case Studies


Python developers and testers working on Web applications


General Python and Web development, testing and QA

Standards and references

OWASP, CWE and Fortify Taxonomy

Group size

12 participants


  • Cyber security basics
  • The OWASP Top Ten
  • Security testing
  • API security
  • Wrap up

What you'll have learned

  • Getting familiar with essential cyber security concepts
  • Understanding Web application security issues
  • Detailed analysis of the OWASP Top Ten elements
  • Putting Web application security in the context of Python
  • Going beyond the low hanging fruits
  • Understanding security testing methodology and approaches
  • Managing vulnerabilities in third party components
  • Getting familiar with security testing techniques and tools
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in Python
  • Input validation approaches and principles


Your Web application written in Python is tested functionally, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -1 or -231? Because that’s what the bad guys will do – and the list is far from complete.

Testing for security needs a remarkable software security expertise and a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands-on labs and stories from real life.

The curriculum goes through the common Web application security issues following the OWASP Top Ten but goes far beyond it both in coverage and the details.A special focus is given to finding all discussed issues during testing, and an overview is provided on security testing methodology, techniques and tools.

So that you are prepared for the forces of the dark side.

So that nothing unexpected happens.


Table of contents

  • Cyber security basics
  • The OWASP Top Ten
    • The OWASP Top 10
    • A1 – Injection
      • Injection principles
      • Injection attacks
      • SQL injection
        • SQL injection basics
        • Lab – SQL injection
        • Attack techniques
        • Content-based blind SQL injection
        • Time-based blind SQL injection
        • Case study – Hacking Fortnite accounts
        • Testing for SQL injection
      • Code injection
        • Code injection via input()
        • OS command injection
          • Lab – Command injection
          • Lab – Command injection best practices
          • Case study – Shellshock
          • Lab – Shellshock
          • Testing for command injection
      • Script injection
        • Server-side template injection (SSTI)
        • Lab – Template injection
    • A2 – Broken Authentication
      • Authentication
        • Authentication basics
        • Multi-factor authentication
        • Case study – PayPal 2FA bypass
        • Testing for weak authentication
      • Password management
  • Security testing
    • Security testing vs functional testing
    • Manual and automated methods
    • Security testing methodology
      • Security testing – goals and methodologies
      • Overview of security testing processes
      • Identifying and rating assets
        • Preparation
        • Identifying assets
        • Identifying the attack surface
        • Assigning security requirements
        • Lab – Identifying and rating assets
      • Threat modeling
        • SDL threat modeling
        • Mapping STRIDE to DFD
        • DFD example
        • Attack trees
        • Attack tree example
        • Lab – Crafting an attack tree
        • Misuse cases
        • Misuse case examples
        • Risk analysis
        • Lab – Risk analysis
        • Reporting, recommendations, and review
  • The OWASP Top Ten
    • A3 – Sensitive Data Exposure
      • Information exposure
      • Exposure through extracted data and aggregation
      • Case study – Strava data exposure
      • Error and exception handling principles
    • A4 – XML External Entities (XXE)
      • DTD and the entities
      • Entity expansion
      • Lab – Billion laughs attack
      • External Entity Attack (XXE)
        • File inclusion with external entities
        • Server-Side Request Forgery with external entities
        • Lab – External entity attack
        • Case study – XXE vulnerability in SAP Store
        • Preventing XXE
      • Testing for XXE and XML entity-related vulnerabilities
    • A5 – Broken Access Control
      • Access control basics
      • Failure to restrict URL access
      • Testing for authorization issues
      • Confused deputy
        • Insecure direct object reference (IDOR)
        • Lab – Insecure Direct Object Reference
        • Authorization bypass through user-controlled keys
        • Case study – Authorization bypass on Facebook
        • Lab – Horizontal authorization
        • Testing for confused deputy weaknesses
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
        • Testing for file upload vulnerabilities
    • A7 – Cross-site Scripting (XSS)
      • Cross-site scripting basics
      • Cross-site scripting types
        • Persistent cross-site scripting
        • Reflected cross-site scripting
        • Client-side (DOM-based) cross-site scripting
      • Lab – Stored XSS
      • Lab – Reflected XSS
      • Case study – XSS in Fortnite accounts
      • Testing for XSS
  • The OWASP Top Ten
    • A8 – Insecure Deserialization
      • Serialization and deserialization challenges
      • Integrity – deserializing untrusted streams
      • Deserialization with pickle
      • Lab – Deserializing with Pickle
      • PyYAML deserialization challenges
      • Testing for insecure deserialization
    • A9 – Using Components with Known Vulnerabilities
      • Using vulnerable components
      • Assessing the environment
      • Hardening
      • Untrusted functionality import
      • Importing JavaScript
      • Case study – The British Airways data breach
      • Vulnerability management
        • Patch management
        • Bug bounty programs
        • Vulnerability databases
        • Vulnerability rating – CVSS
        • DevOps, the build process and CI / CD
        • Dependency checking in Python
        • Lab – Detecting vulnerable components
    • Web application security beyond the Top Ten
      • Client-side security
      • Lab – Client-side security
      • Tabnabbing
      • Frame sandboxing
        • Cross-Frame Scripting (XFS) attack
        • Lab – Clickjacking
        • Clickjacking beyond hijacking a click
      • Some further best practices
        • HTML5 security best practices
        • CSS security best practices
        • Ajax security best practices
  • Security testing
    • Security testing techniques and tools
      • Code analysis
        • Static Application Security Testing (SAST)
        • Lab – Using static analysis tools
      • Dynamic analysis
        • Security testing at runtime
        • Penetration testing
        • Stress testing
        • Dynamic analysis tools
          • Dynamic Application Security Testing (DAST)
          • Web vulnerability scanners
          • Lab – Using web vulnerability scanners
          • SQL injection tools
          • Lab – Using SQL injection tools
        • Fuzzing
  • API security
    • Input validation
      • Input validation principles
        • Lab – Input validation
        • Encoding challenges
        • Unicode challenges
        • Lab – Encoding challenges
        • Validation with regex
        • Regular expression denial of service (ReDoS)
        • Lab – ReDoS in Python
        • Dealing with ReDoS
      • Files and streams
        • Path traversal
        • Lab – Path traversal
        • Path traversal-related examples
        • Additional challenges in Windows
        • Virtual resources
        • Path traversal best practices
        • Lab – Path canonicalization
        • Testing for path traversal
      • Format string issues
      • Unsafe native code
        • Native code dependence
        • Lab – Unsafe native code
        • Best practices for dealing with native code
  • Wrap up
    • And now what?
      • Software security sources and further reading
      • Python resources
      • Security testing resources


3 days Session Price

2250 EUR / person

  • Live, instructor led classroom training
  • Discussion and insight into the hacker’s mindset
  • Hands-on practice using case studies based on high-profile hacks and live lab exercises
Customized Course

Tailor a course to your preferences

  • Send us a brief description of your business’s training needs
  • Include your contact information
  • One of our colleagues will be in touch to schedule a free 45 minute pre-training consultation


Interested in the trainings but still have some questions? Curious about how you can customize a training for your team? Send us a message and a team member will be in touch within 24 hours.

This field is required

This field is required

Send us your phone number if you prefer to discuss further on a call

This field is required

This field is required

This field is required

This field is required