< Back to catalog

Security testing Java Web applications

CYDWebJvTst3d
3 days
On-site or online
Hands-on
Java
Developer
Tester
Instructor-led
Pricing Inquiry Download PDF
labs

30 Labs

case_study

12 Case Studies

Platform

Web

Audience

Java developers and testers working on Web applications

Preparedness

General Java and Web development, testing and QA

Standards and references

OWASP, SEI CERT, CWE and Fortify Taxonomy

Group size

12 participants

Outline

  • Cyber security basics
  • The OWASP Top Ten 2025
  • Security testing
  • 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 Java
  • Going beyond the low hanging fruits
  • Input validation approaches and principles
  • Understanding security testing methodology and approaches
  • Getting familiar with security testing techniques and tools

Description

Your Web application written in Java 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 -2^31? 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.

Nothing.

They said about us

”

Highly recommended

At points very demanding, but well above the average. One would call it an advanced material, but given the importance of right coding habits from the beginning, should be available to all developers.

Open session participant , September, 2019

Helsinki, Finland

Table of contents

  • Cyber security basics
    • What is security?
    • Threat and risk
    • Cyber security threat types – the CIA triad
    • Consequences of insecure software
    • Security testing
      • Security testing vs functional testing
      • Manual and automated methods
      • Black box, white box, and hybrid testing
  • The OWASP Top Ten 2025
    • A01 – Broken Access Control
      • Access control basics
      • Case study – Broken authn/authz in Apache OFBiz
      • Testing for authorization issues
      • Confused deputy
        • Insecure direct object reference (IDOR)
        • Path traversal
        • Case study – RCE via path traversal in Apache OFBiz
        • 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
        • Testing for confused deputy weaknesses
        • Lab – IDOR fuzzing with DotDotPwn
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
        • Case study – File upload vulnerability in Netflix Genie
        • Testing for file upload vulnerabilities
        • Lab – Creating polyglot files for testing
      • Server-side Request Forgery (SSRF)
        • Case study – SSRF in Ivanti Connect Secure
        • Testing for SSRF
    • A02 – Security Misconfiguration
      • 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
          • Preventing XXE
          • Lab – Prohibiting DTD
          • Case study – XXE vulnerability in Ivanti products
        • Testing for XXE and XML entity-related vulnerabilities
    • A03 – Software Supply Chain Failures
  • The OWASP Top Ten 2025
    • A05 – Injection
      • Input validation
        • Input validation principles
        • What to validate – the attack surface
        • Where to validate – defense in depth
        • When to validate – validation vs transformations
      • SQL injection
        • SQL injection basics
        • Lab – SQL injection
        • Testing for SQL injection
          • Testing SQL injection
          • SQL injection tools
          • Lab – Using SQL injection tools
        • SQL injection best practices
          • Input validation
          • Parameterized queries
          • Lab – Using prepared statements
          • Case study – SQL injection in Fortra FileCatalyst
      • Code injection
        • OS command injection
          • OS command injection best practices
          • Using Runtime.exec()
          • Case study – Shellshock
          • Lab – Shellshock
          • Case study – Command injection in VMware Aria
          • Testing for command injection
      • 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
        • Testing for XSS
          • Testing for XSS with tools
          • Lab – Using XSS testing tools
        • XSS protection best practices
          • Protection principles – escaping
          • Lab – XSS fix / stored
          • Lab – XSS fix / reflected
          • Case study – XSS vulnerabilities in DrayTek Vigor routers
  • Security testing
    • Security testing methodology
      • Security testing – goals and methodologies
      • Overview of security testing processes
      • Identifying and rating assets
        • Preparation and scoping
        • 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
        • Lab – SDL threat modelling with OWASP Threat Dragon
        • Attack trees
        • Attack tree example
        • Risk analysis
  • The OWASP Top Ten 2025
    • A06 – Insecure Design
      • Client-side security
        • Frame sandboxing
          • Cross-Frame Scripting (XFS) attacks
          • Lab – Clickjacking
          • Clickjacking beyond hijacking a click
          • Clickjacking protection best practices
          • Lab – Using CSP to prevent clickjacking
        • Testing for client-side security weaknesses
    • A07 – Authentication Failures
      • Session handling
        • Session management essentials
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Session ID best practices
        • Testing for session management issues
      • 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
        • Lab – Using adaptive hash functions in JCA
        • Using password cracking tools
        • Password cracking in Windows
        • Lab – Password audit with John the Ripper
      • Password policy
    • A08 – Software and Data Integrity Failures
      • Subresource integrity
        • Importing JavaScript
        • Lab – Importing JavaScript
        • Case study – The British Airways data breach
        • Testing for subresource integrity
      • Insecure deserialization
        • Serialization and deserialization challenges
        • Integrity – deserializing untrusted streams
        • Integrity – deserialization best practices
        • Look ahead deserialization
        • Testing for insecure deserialization
        • Property Oriented Programming (POP)
          • Creating a POP payload
          • Lab – Creating a POP payload
          • Lab – Using the POP payload
          • Case study – Deserialization RCEs in NextGen Mirth Connect
  • 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
        • Fuzzing
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
      • Secure design principles of Saltzer and Schroeder
    • And now what?
      • Software security sources and further reading
      • Java 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
Inquiry
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

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