Security testing Python Web applications

CYDWebPyTst3d
3 days
Python
Web

Platform

Linux, Windows

Preparedness

General Web development

Audience

Developers and testers working on Web applications

Group size

12 participants

Labs

Hands-on

Outline

  • Cybersecurity basics
  • Security testing
  • The OWASP Top Ten
  • Common software security weaknesses
  • JSON security
  • Wrap up

Objective list

  • Understanding security testing methodology and approaches
  • Getting familiar with common security testing techniques and tools
  • 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
  • Handling security challenges in your Python code
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in Python

Description

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

Handling security needs a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hand on labs and stories from real life, all to substantially improve code hygiene. Mistakes, consequences and best practices are our blood, sweat and tears.

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.All this is put in the context of Java, and extended by core programming issues, discussing security pitfalls of the Java language and framework.

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

So that nothing unexpected happens.

Nothing.

Table of contents

  • Cybersecurity basics
    • What is security?
    • Threat and risk
    • Cybersecurity threat types
    • Consequences of insecure software
    • Constraints and the market
    • The dark side
  • Security testing
    • Security testing vs functional testing
    • Manual and automated methods
  • The OWASP Top Ten
    • OWASP Top 10 – 2017
    • 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
        • SQL injection and ORM
      • Parameter manipulation
      • CRLF injection
        • Log forging
        • Lab – Log forging
        • HTTP response splitting
      • Code injection
        • OS command injection
          • Lab – Command injection
          • Case study – Shellshock
          • Lab – Shellshock
          • Case study – Command injection via ping
          • Testing for command injection
        • Script injection
          • Server-side template injection (SSTI)
          • Lab – Template injection
    • A2 – Broken Authentication
      • Authentication basics
      • Authentication weaknesses
      • Spoofing on the Web
      • Testing for weak authentication
      • Case study – PayPal 2FA bypass
      • User interface best practices
      • Lab – On-line password brute forcing
      • Password management
        • Inbound password management
          • Storing account passwords
          • Password in transit
          • Lab – Why is just hashing passwords not enough?
          • Dictionary attacks and brute forcing
          • Salting
          • Adaptive hash functions for password storage
          • Password policy
            • NIST authenticator requirements for memorized secrets
            • Password length
            • Password hardening
            • Using passphrases
          • The Ashley Madison data breach
            • The dictionary attack
            • The ultimate crack
            • Exploitation and the lessons learned
            • (Mis)handling None passwords
            • Testing for password management issues
        • Outbound password management
          • Hard coded passwords
          • Protecting sensitive information in memory
            • Challenges in protecting memory
      • Session management
        • Session management essentials
        • Session ID best practices
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Session handling in Flask
        • Testing for session management issues
        • Cross-site Request Forgery (CSRF)
          • Lab – Cross-site Request Forgery
          • Testing for CSRF
        • Cookie security
          • Testing cookie security
  • The OWASP Top Ten
    • A3 – Sensitive Data Exposure
      • Information exposure
      • Exposure through extracted data and aggregation
      • Case study – Strava fitness app data exposure
      • System information leakage
        • Leaking system information
        • Error and exception handling principles
        • Information exposure through error reporting
        • Information leakage via error pages
        • Lab – Flask information leakage
    • A4 – XML External Entities (XXE)
      • DTD and the entities
      • Entity expansion
      • Lab – Billion laughs attack
      • Attribute blowup
      • 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
      • Lab – 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
        • Server-side Request Forgery (SSRF)
        • Testing for confused deputy weaknesses
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
        • Testing for file upload vulnerabilities
    • A6 – Security Misconfiguration
      • Configuration principles
      • Configuration management
      • Server misconfiguration
      • Python configuration best practices
        • Configuring Flask
        • Testing for misconfiguration issues
    • 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
        • Additional protection layers
        • Blacklisting-based XSS protection evasion
        • Testing for XSS
    • A8 – Insecure Deserialization
      • Serialization and deserialization challenges
      • Deserializing untrusted streams
      • Deserialization with pickle
      • Lab – Deserializing with Pickle
      • Deserialization with PyYAML
      • Testing for insecure deserialization
    • A9 – Using Components with Known Vulnerabilities
      • Using vulnerable components
      • Assessing the environment
      • Hardening
      • Untrusted functionality import
      • Malicious packages in Python
      • Importing JavaScript
      • Lab – Importing JavaScript
      • Case study – The British Airways data breach
      • Vulnerability management
        • Patch management
        • Vulnerability databases and scanning tools
        • The build process and CI / CD
        • Dependency checking in Python
        • Lab – Detecting vulnerable components
  • The OWASP Top Ten
    • A10 – Insufficient Logging & Monitoring
      • Logging and monitoring principles
      • Insufficient logging
      • Plaintext passwords at Facebook
    • Web application security beyond the Top Ten
      • Client-side security
      • Tabnabbing
      • Lab – Reverse tabnabbing
      • Frame sandboxing
        • Cross-Frame Scripting (XFS) attack
        • Lab – Clickjacking
        • Clickjacking beyond hijacking a click
  • Security testing
    • 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
        • Attacker profiling
        • 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
      • Security testing approaches
        • Reporting, recommendations, and review
    • Security testing techniques and tools
      • Code analysis
        • Security aspects of code review
        • Static Application Security Testing (SAST)
        • 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
        • Using web vulnerability scanners
        • SQL injection tools
        • Using SQL injection tools
        • Proxy servers
        • Fuzzing
  • Common software security weaknesses
    • Input validation
      • Input validation principles
        • Lab – Input validation
        • Encoding challenges
        • Lab – Encoding challenges
        • Validation with regex
        • Lab – Regular expression denial of service (ReDoS)
  • JSON security
    • JSON injection
    • Dangers of JSONP
    • JSON/JavaScript hijacking
    • JSON testing
    • ReactJS vulnerability in HackerOne
  • Wrap up
    • And now what?
      • Further sources and readings
      • Python resources
      • Security testing resources

Pricing

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

Inquiry

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