Desktop application security in C#
25 Labs
7 Case Studies
Platform
Desktop
Audience
C# developers working on desktop applications
Preparedness
General C# development
Standards and references
CWE and Fortify Taxonomy
Group size
12 participants
Outline
- Cyber security basics
- Input validation
- Security features
- Errors
- Denial of service
- Cryptography for developers
- Common software security weaknesses
- Wrap up
What you will learn
- Getting familiar with essential cyber security concepts
- Input validation approaches and principles
- Identify vulnerabilities and their consequences
- Learn the security best practices in C#
- Correctly implementing various security features
- Understanding how cryptography supports security
- Learning how to use cryptographic APIs correctly 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 -1 or -2^31? 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.
All this is put in the context of C#, and extended by core programming issues, discussing security pitfalls of the C# language and the .NET framework.
So that you are prepared for the forces of the dark side.
So that nothing unexpected happens.
Nothing.
Table of contents
- Cyber security basics
- What is security?
- Threat and risk
- Cyber security threat types – the CIA triad
- Cyber security threat types – the STRIDE model
- Consequences of insecure software
- Input validation
- Input validation principles
- Denylists and allowlists
- What to validate – the attack surface
- Where to validate – defense in depth
- When to validate – validation vs transformations
- Validation with regex
- Injection
- Injection principles
- Injection attacks
- Code injection
- OS command injection
- Lab – Command injection
- OS command injection best practices
- Avoiding command injection with the right APIs
- Lab – Command injection best practices
- Case study – Command injection via ping
- OS command injection
- Integer handling problems
- Representing signed numbers
- Integer visualization
- Integer overflow
- Lab – Integer overflow
- Signed / unsigned confusion
- Case study – The Stockholm Stock Exchange
- Lab – Signed / unsigned confusion
- Integer truncation
- Best practices
- Upcasting
- Precondition testing
- Postcondition testing
- Integer handling in C#
- Lab – Checked arithmetics
- Files and streams
- Path traversal
- Lab – Path traversal
- Path traversal best practices
- Lab – Path canonicalization
- Unsafe reflection
- Reflection without validation
- Lab – Unsafe reflection
- Security features
- Authentication
- Authentication basics
- Multi-factor authentication (MFA)
- Time-based One Time Passwords (TOTP)
- 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 C#
- Password policy
- Case study – The Ashley Madison data breach
- The ultimate crack
- Exploitation and the lessons learned
- Password database migration
- 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
- Inbound password management
- Information exposure
- Exposure through extracted data and aggregation
- Case study – Strava data exposure
- Platform security
- .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
- Code Access Security
- .NET platform security
- Authentication
- 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
- Lab – Exception handling mess
- Denial of service
- Flooding
- Resource exhaustion
- Algorithmic complexity issues
- Regular expression denial of service (ReDoS)
- Lab – ReDoS
- Dealing with ReDoS
- Regular expression denial of service (ReDoS)
- Cryptography for developers
- Cryptography basics
- Crypto APIs in C#
- Elementary algorithms
- Random number generation
- Pseudo random number generators (PRNGs)
- Cryptographically secure PRNGs
- Weak and strong PRNGs
- Using random numbers in C#
- Lab – Using random numbers in C#
- Case study – Equifax credit account freeze
- Hashing
- Hashing basics
- Hashing in C#
- Lab – Hashing in C#
- Random number generation
- Confidentiality protection
- Symmetric encryption
- Block ciphers
- Modes of operation
- Modes of operation and IV – best practices
- Symmetric encryption in C#
- Symmetric encryption in C# with streams
- Lab – Symmetric encryption in C#
- Asymmetric encryption
- Combining symmetric and asymmetric algorithms
- Symmetric encryption
- Integrity protection
- Message Authentication Code (MAC)
- Calculating HMAC in C#
- Lab – Calculating MAC in C#
- Digital signature
- Elliptic Curve Cryptography
- ECC basics
- Digital signature with ECC
- Digital signature in C#
- Lab – Digital signature with ECDSA in C#
- Elliptic Curve Cryptography
- Message Authentication Code (MAC)
- Public Key Infrastructure (PKI)
- Some further key management challenges
- Certificates
- Certificates and PKI
- X.509 certificates
- Chain of trust
- PKI actors and procedures
- Certificate revocation
- Common software security weaknesses
- Code quality
- Code quality and security
- Data handling
- Initialization and cleanup
- Class initialization cycles
- Lab – Initialization cycles
- Unreleased resource
- Initialization and cleanup
- Object oriented programming pitfalls
- Accessibility modifiers
- Are accessibility modifiers a security feature?
- Accessibility modifiers – best practices
- Mutability
- Lab – Mutable object
- Readonly collections
- Accessibility modifiers
- Serialization
- Serialization and deserialization challenges
- Confidentiality – Serializing sensitive data
- Confidentiality – serialization best practices
- Integrity – deserializing untrusted streams
- Integrity – deserialization best practices
- Look ahead deserialization
- Property Oriented Programming (POP)
- Creating a POP payload
- Lab – Creating a POP payload
- Lab – Using the POP payload
- Summary – POP best practices
- Code quality
- 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
- .NET and C# resources
- Secure coding principles
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 consultation about training requirements
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.
Related Courses
Web application security in C#
CYDCsWeb3d
3 days
>
Audience
C# developers working on Web applications
Group size
12 participants
Labs
Hands-on
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 -1 or -2^31? 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 C#, and extended by core programming issues, discussing security pitfalls of the C# language and the ASP.NET framework.
So that you are prepared for the forces of the dark side.
So that nothing unexpected happens.
Nothing.
Outline
- Cyber security basics
- The OWASP Top Ten 2021
- Wrap up
What you will learn
- Getting familiar with essential cyber security concepts
- Understanding how cryptography supports security
- Learning how to use cryptographic APIs correctly in C#
- 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
- Managing vulnerabilities in third party components