Web application security in Java and C#

CYDJvCsWeb4d
4 days
C#
Java
Web

Platform

Windows

Preparedness

General Java, C# and Web development

Audience

Java and C# developers working on Web applications

Group size

12 participants

Labs

Hands-on

Outline

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

Objective list

  • 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
  • Handling security challenges in your Java and C# code
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in Java and C#

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

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
    • Categorization of bugs
      • The Seven Pernicious Kingdoms
      • SEI Cert Secure Coding Guidelines
  • 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
      • SQL injection best practices
        • Input validation
        • Parameterized queries
        • Additional considerations
        • Lab – Using prepared statements in C#
        • Case study – Hacking Fortnite accounts
      • Code injection
        • OS command injection
          • Lab – Command injection in C#
          • OS command injection best practices
          • Using Runtime.exec() in Java
          • Using ProcessBuilder in Java
          • Command injection best practices in C#
          • Lab – Command injection best practices in C#
          • Case study – Command injection via ping
        • Script injection
      • Injection best practices
    • A2 – Broken Authentication
      • Authentication basics
      • Authentication weaknesses
      • Spoofing on the Web
      • Case study – PayPal 2FA bypass
      • User interface best practices
      • Lab – On-line password brute forcing
      • Session management
        • Session management essentials
        • Session ID best practices
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Cross-site Request Forgery (CSRF)
          • Lab – Cross-site Request Forgery
          • CSRF best practices
          • Lab – CSRF protection with tokens
        • Cookie security
          • Cookie security best practices
          • Cookie attributes
  • The OWASP Top Ten
    • A2 – Broken Authentication
      • 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
            • Lab – Applying a password policy
          • The Ashley Madison data breach
            • The dictionary attack
            • The ultimate crack
            • Exploitation and the lessons learned
          • Password database migration
            • (Mis)handling null passwords
        • Outbound password management
          • Hard coded passwords
          • Best practices
          • Lab – Hardcoded password
          • Protecting sensitive information in memory
            • Challenges in protecting memory
            • Storing sensitive data in memory
            • Storing sensitive data in memory in Java
            • Sensitive data in memory in C#
    • 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
      • 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
    • A5 – Broken Access Control
      • Access control basics
      • Failure to restrict URL access
      • 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
    • A6 – Security Misconfiguration
      • Configuration principles
      • Configuration management
      • Server misconfiguration
      • Java related components – best practices
        • Tomcat configuration
      • ASP.NET and IIS configuration best practices
        • ASP.NET configuration
        • IIS configuration
    • 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
        • Client-side protection principles
  • The OWASP Top Ten
    • A8 – Insecure Deserialization
      • Serialization and deserialization challenges
      • Deserializing untrusted streams
      • Deserializing best practices
      • Using ReadObject in Java
      • Sealed objects in Java
      • Look ahead deserialization in Java
      • Property Oriented Programming (POP)
        • Creating payload in Java
        • Creating payload in C#
        • POP best practices
        • Lab – Creating a POP payload in C#
        • Lab – Using the POP payload
    • 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 and scanning tools
        • Lab – Searching for vulnerabilities in the used components in Java
        • Lab – Searching for vulnerabilities in the used components in C#
    • A10 – Insufficient Logging & Monitoring
      • Logging and monitoring principles
      • Insufficient logging
      • Plaintext passwords at Facebook
      • Logging best practices
      • OWASP security logging library for Java
      • C# logging best practices
      • Monitoring best practices
    • 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
        • When to validate – validation vs transformations
        • Where to validate – defense in depth
        • Output sanitization
        • Encoding challenges
        • Lab – Encoding challenges
        • Validation with regex
        • Lab – Regular expression denial of service (ReDoS)
      • Integer handling problems
        • Representing signed numbers
        • Integer visualization
        • Integer overflow
        • Lab – Integer overflow
        • Signed / unsigned confusion
        • Signed / unsigned confusion in Java
        • Lab – Signed / unsigned confusion
        • Integer truncation
        • Best practices
          • Upcasting
          • Precondition testing
          • Postcondition testing
          • Using big integer libraries
          • Integer handling in Java
          • Lab – Integer handling in Java
          • Integer handling in C#
          • Lab – Checked arithmetics in C#
      • Other numeric problems
        • Division by zero
        • Working with floating-point numbers in Java
      • Unsafe reflection
        • Reflection without validation
        • Lab – Unsafe reflection
      • Unsafe native code
        • Native code dependence
        • Lab – Unsafe JNI
        • Lab – Unsafe native code
        • Best practices for dealing with native code
    • Security features
      • 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
  • Common software security weaknesses
    • Security features
      • .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
          • Impersonation
          • 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
          • Lab – Singleton member fields
        • File race condition
          • Insecure temporary file
        • Database race conditions
          • Lab – Database race conditions
        • Avoiding race conditions in Java
        • 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
        • Lab – Exception handling mess
        • Catching and throwing SystemExceptions
        • Lab – Exception handling mess
    • Code quality
      • Constructors and destructors
      • Class initialization cycles
      • Lab – Initialization cycles
      • The finalize() method – best practices in Java
      • Object oriented programming pitfalls
        • Inheritance and overriding
        • Implementing equals()
        • Mutability
          • Lab – Mutable object
          • Readonly collections in C#
        • Cloning
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
      • Secure design principles of Saltzer and Schröder
    • And now what?
      • Further sources and readings
      • .NET and C# resources
      • Java 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