Desktop application security in C#

CYDCsDsk3d
3 days
C#

Platform

Windows

Preparedness

General C# development

Audience

C# developers working on desktop applications

Group size

12 participants

Labs

Hands-on

Outline

  • Cybersecurity basics
  • Input validation
  • Using vulnerable components
  • Security features
  • Common software security weaknesses
  • Wrap up

Objective list

  • Handling security challenges in your C# code
  • Identify vulnerabilities and their consequences
  • Learn the security best practices in C#

Description

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

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
    • Categorization of bugs
      • The Seven Pernicious Kingdoms
  • Input validation
    • Input validation principles
      • Blacklists and whitelists
      • Data validation techniques
      • What to validate – the attack surface
      • When to validate – validation vs transformations
      • Where to validate – defense in depth
      • Output sanitization
      • Encoding challenges
      • Validation with regex
      • Lab – Regular expression denial of service (ReDoS)
    • Injection
      • Injection principles
      • Injection attacks
      • CRLF injection
        • Log forging
        • Lab – Log forging
        • Log forging – best practices
      • 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
    • 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
      • Containers
        • Security issues with containers and unused elements
        • Associative containers
    • Files and streams
      • Path traversal
      • Path traversal-related examples
      • Lab – Path traversal
      • Additional challenges in Windows
      • Virtual resources
      • Path traversal best practices
    • 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
  • Using vulnerable components
    • Assessing the environment
    • Hardening
    • Untrusted functionality import
    • Lab – Importing JavaScript
    • Case study – The Equifax data breach
    • Vulnerability management
      • Patch management
      • Vulnerability databases and scanning tools
      • Lab – Searching for vulnerabilities in the used components
  • Security features
    • Authentication
      • Authentication basics
      • Authentication weaknesses
      • Case study – PayPal 2FA bypass
      • User interface best practices
      • Lab – On-line password brute forcing
      • 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
            • Sensitive data in memory
    • Authorization
      • Access control basics
      • Access control in databases
      • Privileges and permissions
        • Permission manipulation
        • Case study – The Capital One breach
        • Incorrect use of privileged APIs
      • Permission best practices
        • Principle of least privilege
        • Principle of separation of privilege
        • Permission granting and handling
    • .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
    • 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
    • UI security
      • UI security principles
      • Sensitive information in the user interface
      • Lab – Extracting password from the UI
      • Misinterpretation of UI features or actions
      • Insufficient UI feedback
      • Relying on hidden or disabled UI element
      • Insufficient anti-automation
  • Common software security weaknesses
    • Time and state
      • Race conditions
        • Race condition in object data members
          • Lab – Singleton member fields
        • File race condition
          • Insecure temporary file
        • Database race conditions
        • Avoiding race conditions in C#
    • Errors
      • Error and exception handling principles
      • Error handling
        • Returning a misleading status code
        • Information exposure through error reporting
      • 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
    • Denial of service
      • Denial of Service
      • Resource exhaustion
      • Cash overflow
      • Flooding
      • Sustained client engagement
      • Denial of service problems in C#
      • Infinite loop
      • Lab – Resource exhausting
      • Amplification
        • Network amplification
        • Amplification in databases
        • Other amplification examples
      • Algorithm complexity issues
        • Regular expression denial of service (ReDoS)
          • Lab – ReDos
        • Hashtable collision
          • How hashtables work?
          • Hash collision in case of hashtables
          • Hashtable collision in C#
  • 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