Web application security in Java and C#

CYDJvCsWeb4d
4 days
On-site or online
Hands-on
C#
Java
Web
Developer
labs

39 Labs

case_study

12 Case Studies

Audience

Java and C# developers working on Web applications

Preparedness

General Java, C# and Web development

Standards and references

OWASP, SEI CERT, CWE and Fortify Taxonomy

Group size

12 participants

Outline

  • Cyber security basics
  • The OWASP Top Ten
  • Common software security weaknesses
  • Security features
  • 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 Java and C#
  • Going beyond the low hanging fruits
  • Managing vulnerabilities in third party components
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in Java and C#
  • Input validation approaches and principles

Description

Your application written in Java and C# 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 -231? 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 the discussed programming languages, and extended by core programming issues, discussing security pitfalls of the used frameworks.

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

So that nothing unexpected happens.

Nothing.

They said about us

Protect your data, not your code

The class did not only discuss the whole idea of security but is also helpful in planning the whole system together with how people would create applications from scratch. Pretty much useful since a lot of developers who start a project do not focus on security in the architecture phase but just specifications. Very useful in the long run.

Employee at a Global Insurance Group , May, 2019

Manila, The Philippines

Table of contents

  • Cyber security basics
    • What is security?
    • Threat and risk
    • Cyber security threat types
    • Consequences of insecure software
      • Constraints and the market
      • The dark side
  • 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
      • SQL injection best practices
        • Input validation
        • Parameterized queries
        • Lab – Using prepared statements in C#
        • Additional considerations
        • Case study – Hacking Fortnite accounts
      • Code injection
        • OS command injection
          • Lab – Command injection
          • OS command injection best practices
          • Using Runtime.exec() in Java
          • Using ProcessBuilder in Java
          • Avoiding command injection with the right APIs in C#
          • Lab – Command injection best practices
          • Case study – Command injection via ping
      • Script injection
    • A3 – Sensitive Data Exposure
      • Information exposure
      • Exposure through extracted data and aggregation
      • Case study – Strava data exposure
      • System information leakage
        • Leaking system information
      • Information exposure best practices
    • A4 – XML External Entities (XXE)
      • 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
        • Case study – XXE vulnerability in SAP Store
        • Preventing XXE in Java
        • Preventing XXE in C#
        • Lab – Prohibiting DTD
    • A10 – Insufficient Logging & Monitoring
      • Logging and monitoring principles
      • Insufficient logging
      • Case study – Plaintext passwords at Facebook
      • Logging best practices
      • Monitoring best practices
  • The OWASP Top Ten
    • A2 – Broken Authentication
      • Authentication
        • Authentication basics
        • Multi-factor authentication
        • Authentication weaknesses
        • Case study – PayPal 2FA bypass
      • Password management
        • Inbound 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
          • Password policy
          • Case study – The Ashley Madison data breach
            • The dictionary attack
            • The ultimate crack
            • Exploitation and the lessons learned
          • Password database migration
            • (Mis)handling null passwords
      • Session management
        • Session management essentials
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Session ID best practices
    • A5 – Broken Access Control
      • Access control basics
      • 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
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
    • 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
      • XSS protection best practices
        • Protection principles – escaping
        • XSS protection APIs in Java
        • XSS protection in JSP
        • XSS protection APIs in C#
        • Request validation in ASP.NET
        • Further XSS protection techniques in C#
        • Lab – XSS fix in C# / stored
        • Lab – XSS fix in C# / reflected
        • Additional protection layers
    • A8 – Insecure Deserialization
      • Serialization and deserialization challenges
      • Integrity – deserializing untrusted streams
      • Using readObject in Java
      • Integrity – deserialization best practices
      • Look ahead deserialization in Java
      • Property Oriented Programming (POP)
        • Creating payload in C#
        • Summary – POP best practices
        • Lab – Creating a POP payload
        • Lab – Using the POP payload
  • The OWASP Top Ten
    • A9 – Using Components with Known Vulnerabilities
      • Using vulnerable components
      • Assessing the environment
      • Hardening
      • Untrusted functionality import
      • Importing JavaScript
      • Lab – Importing JavaScript
      • Case study – The British Airways data breach
      • Vulnerability management
        • Patch management
        • Vulnerability databases
        • Lab – Finding vulnerabilities in third-party components
    • Web application security beyond the Top Ten
      • Client-side security
      • Same Origin Policy
      • Tabnabbing
      • Lab – Reverse tabnabbing
      • Frame sandboxing
        • Cross-Frame Scripting (XFS) attack
        • Lab – Clickjacking
        • Clickjacking beyond hijacking a click
        • Clickjacking protection best practices
        • Lab – Using CSP to prevent clickjacking
  • Common software security weaknesses
    • Input validation
      • Input validation principles
        • Blacklists and whitelists
        • Data validation techniques
        • Lab – Input validation
        • What to validate – the attack surface
        • Where to validate – defense in depth
        • When to validate – validation vs transformations
        • Validation with regex
        • Regular expression denial of service (ReDoS)
        • Lab – ReDoS
        • Dealing with ReDoS
      • Integer handling problems
        • Representing signed numbers
        • Integer visualization
        • Integer overflow
        • Lab – Integer overflow
        • Signed / unsigned confusion
        • Signed / unsigned confusion in Java
        • Case study – The Stockholm Stock Exchange
        • Lab – Signed / unsigned confusion
        • Integer truncation
        • Best practices
          • Upcasting
          • Precondition testing
          • Postcondition testing
          • Integer handling in Java
          • Lab – Integer handling in Java
          • Integer handling in C#
          • Lab – Checked arithmetics in C#
      • Unsafe reflection
        • Reflection without validation
        • Lab – Unsafe reflection
  • Common software security weaknesses
    • Security features
      • Platform security
        • Java platform security
          • The Java programming language and runtime environment
          • Type safety and security
          • Security features of the JRE
            • The ClassLoader and the BytecodeVerifier
          • Application-level access control in Java
            • Permissions and the Security Manager
            • Privilege best practices
          • Role-based access control
            • Java Authentication and Authorization Services (JAAS)
          • Protecting Java code and applications
            • Code signing
            • Lab – Code signing and permissions
        • .NET platform security
          • Code Access Security
            • Code Access Security and Evidence
            • Application Domains and Permissions
            • The Stack Walk
            • Lab – Code Access Security
          • The transparency model
            • Lab – The transparency model
          • Role-based security
            • Principal and identity
            • Role-based permissions
            • Lab – Role-based security
          • Protecting .NET code and applications
            • Code signing
    • Time and state
      • Race conditions
        • Race condition in object data members
          • Singleton member fields
        • File race condition
          • Time of check to time of usage – TOCTTOU
          • TOCTTOU attacks in practice
          • Insecure temporary file
        • Database race conditions
        • Race conditions in Java
          • Avoiding race conditions in Java
        • Race conditions in C#
          • Avoiding race conditions in C#
    • Errors
      • Error and exception handling principles
      • Error handling
        • Returning a misleading status code
        • Reachable assertion
        • Information exposure through error reporting
          • Information leakage via error pages
      • Exception handling
        • In the catch block. And now what?
        • Catching NullPointerException
        • Empty catch block
        • Overly broad throws
        • Improper completing of the finally block
        • Throwing undeclared checked exceptions
        • Swallowed ThreadDeath
        • Throwing RuntimeException, Exception, or Throwable
        • Catching and throwing SystemExceptions
        • Lab – Exception handling mess
    • Code quality
      • Data handling
        • Initialization and cleanup
          • Constructors and destructors
          • Class initialization cycles
          • Lab – Initialization cycles
        • Unreleased resource
          • The finalize() method – best practices in Java
      • Object oriented programming pitfalls
        • Accessibility modifiers
          • Are accessibility modifiers a security feature?
          • Accessibility modifiers – best practices
          • Overriding and accessibility modifiers in Java
        • Mutability
          • Lab – Mutable object
          • Readonly collections in C#
      • Serialization
        • Confidentiality – Serializing sensitive data
        • Confidentiality – serialization best practices
        • DoS with deserialization
        • Lab – Billion laughs with deserialization
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
      • Secure design principles of Saltzer and Schröder
    • And now what?
      • Software security sources and further reading
      • Java resources
      • .NET and C# resources

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 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