Web application security in C#

CYDCsWeb3d
3 days
C#
Web

Platform

Windows

Preparedness

General C# and Web development

Audience

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

Description

Your Web application written in 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 C#, and extended by core programming issues, discussing security pitfalls of the C# language and .NET 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
  • 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
        • Case study – Hacking Fortnite accounts
      • Code injection
        • OS command injection
          • Lab – Command injection
          • OS command injection best practices
          • Command injection best practices
          • Lab – Command injection best practices
          • 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
      • 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
          • 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
            • Sensitive data in memory
      • 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
    • A3 – Sensitive Data Exposure
      • Information exposure
      • Exposure through extracted data and aggregation
      • Case study – Strava fitness app data exposure
  • The OWASP Top Ten
    • 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
        • 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
    • 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
        • Request validation in ASP.NET
        • Further XSS protection techniques
        • Lab – XSS fix / stored
        • Lab – XSS fix / reflected
        • Additional protection layers
    • A8 – Insecure Deserialization
      • Serialization and deserialization challenges
      • Deserializing untrusted streams
      • Deserializing best practices
      • Property Oriented Programming (POP)
        • Creating payload
        • POP best practices
        • Lab – Creating a POP payload
        • Lab – Using the POP payload
    • A9 – Using Components with Known Vulnerabilities
      • Using vulnerable components
      • Untrusted functionality import
      • Importing JavaScript
      • Lab – Importing JavaScript
      • Case study – The British Airways data breach
    • A10 – Insufficient Logging & Monitoring
      • Logging and monitoring principles
    • 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
        • 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
        • Lab – Signed / unsigned confusion
        • Integer truncation
        • Best practices
          • Upcasting
          • Precondition testing
          • Postcondition testing
          • Using big integer libraries
          • Integer handling in C#
          • Lab – Checked arithmetics
      • Other numeric problems
        • Division by zero
      • Unsafe reflection
        • Reflection without validation
        • Lab – Unsafe reflection
      • Unsafe native code
        • Native code dependence
        • Lab – Unsafe native code
        • Best practices for dealing with native code
    • 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
    • Errors
      • Error and exception handling principles
      • Error handling
        • Returning a misleading status code
        • Information exposure through error reporting
          • Information leakage via error pages
      • Exception handling
        • In the catch block. And now what?
        • Catching NullReferenceException
        • Empty catch block
        • Catching and throwing SystemExceptions
        • Lab – Exception handling mess
    • Code quality
      • Class initialization cycles
      • Lab – Initialization cycles
      • Unreleased resource
      • Object oriented programming pitfalls
        • Relying on accessibility modifiers
        • Accessibility modifiers
        • Inheritance and overriding
        • Implementing Equals()
        • Mutability
          • Lab – Mutable object
          • Readonly collections
      • Serialization
        • Serializing sensitive data
        • Serialization best practices
  • 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

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