Extended Web application security

CYDWeb4d
4 days
On-site or online
Hands-on
Developer
Instructor-led
labs

27 Labs

case_study

18 Case Studies

Platform

Web

Audience

Web developers

Preparedness

General Web development

Standards and references

OWASP, CWE and Fortify Taxonomy

Group size

12 participants

Outline

  • Cyber security basics
  • The OWASP Top Ten 2025
  • Wrap up

What you will learn

  • Getting familiar with essential cyber security concepts
  • Managing vulnerabilities in third party components
  • Understanding Web application security issues
  • Detailed analysis of the OWASP Top Ten elements
  • Putting Web application security in the context of any programming language
  • Going beyond the low hanging fruits
  • Understanding how cryptography supports security
  • Input validation approaches and principles

Description

Your application written in any programming language 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 -1 or -2^31? 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 hands-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.

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

So that nothing unexpected happens.

Nothing.

They said about us

Hands-on experience

The exercises we had in the lab were entertaining. It made things more understandable. That was very good.

Employee at a Government Organization , October, 2020

Oslo, Norway

Table of contents

  • Cyber security basics
  • The OWASP Top Ten 2025
    • A01 – Broken Access Control
      • Access control basics
      • Confused deputy
        • Insecure direct object reference (IDOR)
        • Path traversal
        • Lab – Insecure Direct Object Reference
        • Path traversal best practices
        • Authorization bypass through user-controlled keys
        • Case study – Remote takeover of Nexx garage doors and alarms
        • Lab – Horizontal authorization
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
      • Open redirects and forwards
        • Case study – Hacking Fortnite accounts
        • Case study – Unvalidated redirect at Epic Games
        • Open redirects and forwards – best practices
      • Server-side Request Forgery (SSRF)
        • Case study – SSRF and the Capital One breach
    • A02 – Security Misconfiguration
      • Configuration principles
      • Web security configuration issues
        • Content Security Policy
        • Fetch directives
        • Source allowlisting
        • Strict CSP: using nonces and hashes
        • Navigation and reporting directives
        • Document restrictions and sandboxing
        • CSP best practices
      • Cookie security
        • Cookie attributes
      • Secrets management
        • Hard coded passwords
        • Best practices
        • Lab – Hardcoded password
      • XML entities
        • DTD and the entities
        • Entity expansion
        • External Entity Attack (XXE)
          • File inclusion with external entities
          • Server-Side Request Forgery with external entities
          • Lab – External entity attack
          • Lab – Prohibiting DTD
          • Case study – XXE vulnerability in Ivanti products
    • A03 – Software Supply Chain Failures
  • The OWASP Top Ten 2025
    • A04 – Cryptographic Failures
      • Information exposure
        • Exposure through extracted data and aggregation
        • Case study – Strava data exposure
      • Cryptography for developers
        • Cryptography basics
        • Elementary algorithms
          • Hashing
            • Hashing basics
            • Common hashing mistakes
            • Lab – Hashing
          • Random number generation
            • Pseudo random number generators (PRNGs)
            • Cryptographically secure PRNGs
            • Using virtual random streams
            • Lab – Using random numbers
            • Case study – Equifax credit account freeze
        • Confidentiality protection
          • Symmetric encryption
            • Block ciphers
            • Modes of operation
            • Modes of operation and IV – best practices
            • Lab – Symmetric encryption
          • Asymmetric encryption
            • The RSA algorithm
              • Using RSA – best practices
              • Case study – RSA attacks: Bleichenbacher, ROBOT, and Marvin
          • Combining symmetric and asymmetric algorithms
          • Key exchange and agreement
            • Key exchange
            • Diffie-Hellman key agreement algorithm
            • Key exchange pitfalls and best practices
    • A05 – Injection
      • Input validation
        • Input validation principles
        • Denylists and allowlists
        • What to validate – the attack surface
        • Where to validate – defense in depth
        • When to validate – validation vs transformations
        • Output sanitization
        • Encoding challenges
        • Unicode challenges
        • Validation with regex
      • SQL injection
        • SQL injection basics
        • Lab – SQL injection
        • Attack techniques
        • Content-based blind SQL injection
        • Time-based blind SQL injection
        • SQL injection best practices
          • Input validation
          • Parameterized queries
          • Lab – Using prepared statements
          • Database defense in depth
          • Case study – Hacking Fortnite accounts
  • The OWASP Top Ten 2025
    • A05 – Injection (continued)
      • Input validation
      • Code injection
        • OS command injection
          • OS command injection best practices
          • Case study – Shellshock
          • Lab – Shellshock
      • HTML injection – 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
        • XSS protection best practices
          • Protection principles – escaping
          • Lab – XSS fix / stored
          • Lab – XSS fix / reflected
          • Client-side protection principles
          • Additional protection layers – defense in depth
    • A06 – Insecure Design
      • The STRIDE model of threats
      • Secure design principles of Saltzer and Schroeder
        • Economy of mechanism
        • Fail-safe defaults
        • Complete mediation
        • Open design
        • Separation of privilege
        • Least privilege
        • Least common mechanism
        • Psychological acceptability
      • Client-side security
        • Same Origin Policy
          • Simple request
          • Preflight request
          • Cross-Origin Resource Sharing (CORS)
        • Frame sandboxing
          • Cross-Frame Scripting (XFS) attacks
          • Lab – Clickjacking
          • Clickjacking beyond hijacking a click
          • Clickjacking protection best practices
          • Lab – Using CSP to prevent clickjacking
    • A07 – Authentication Failures
      • Authentication
        • Authentication basics
        • Multi-factor authentication (MFA)
        • Case study – The InfinityGauntlet attack
        • Passwordless solutions
        • Time-based One Time Passwords (TOTP)
        • Authentication weaknesses
        • Spoofing on the Web
        • User interface best practices
        • Lab – On-line password brute forcing
      • Password management
        • Storing account passwords
        • Password in transit
        • Lab – Is just hashing passwords enough?
        • Dictionary attacks and brute forcing
        • Salting
        • Adaptive hash functions for password storage
        • Password database migration
        • (Mis)handling null passwords
  • The OWASP Top Ten 2025
    • A07 – Authentication Failures (continued)
      • Session handling
        • Session management essentials
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Session invalidation
        • Session ID best practices
      • Password policy
    • A08 – Software and Data Integrity Failures
      • Integrity protection
        • Message Authentication Code (MAC)
          • Lab – Calculating MAC
        • Digital signature
          • Digital signature with RSA
          • Elliptic Curve Cryptography
            • ECC basics
            • Digital signature with ECC
            • Lab – Digital signature with ECDSA
      • Public Key Infrastructure (PKI)
        • Key management challenges
        • Certificates
          • Certificates and PKI
          • Chain of trust
      • Subresource integrity
        • Importing JavaScript
        • Lab – Importing JavaScript
        • Case study – The British Airways data breach
      • Insecure deserialization
        • Serialization and deserialization challenges
        • Integrity – deserializing untrusted streams
        • Integrity – deserialization best practices
        • Property Oriented Programming (POP)
          • Creating a POP payload
          • Lab – Creating a POP payload
          • Lab – Using the POP payload
          • Summary – POP best practices
    • A09 – Logging and Alerting Failures
      • Logging and monitoring principles
      • Insufficient logging
      • Case study – Plaintext passwords at Facebook
      • Log forging
      • Web log forging
      • Log forging – best practices
      • Logging best practices
      • Monitoring best practices
    • A10 – Mishandling of Exceptional Conditions
      • Error and exception handling principles
      • Error handling
        • Returning a misleading status code
        • Information exposure through error reporting
          • Information leakage via error pages
          • Case study – Information leakage via errors in Apache Superset
      • Exception handling
        • In the catch block. And now what?
        • Empty catch block
        • Lab – Exception handling mess
      • Control flow
        • Incorrect block delimitation
        • Dead code
        • Using if-then-else and switch defensively
    • Web application security beyond the Top Ten
      • X01 – Lack of Application Resilience
        • Denial of service
        • Flooding
        • Resource exhaustion
        • Sustained client engagement
        • Infinite loop
        • Economic Denial of Sustainability (EDoS)
        • Algorithmic complexity issues
          • Regular expression denial of service (ReDoS)
            • Lab – ReDoS
            • Dealing with ReDoS
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
    • And now what?
      • Software security sources and further reading

Pricing

4 days Session Price

3000 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 consultation about training requirements

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