Cloud application security in C# for Azure
39 Labs
19 Case Studies
Platform
Cloud, Web
Audience
C# developers working on Web applications and Azure
Preparedness
General C# and Web development
Standards and references
OWASP, CWE and Fortify Taxonomy
Group size
12 participants
Outline
- Cyber security basics
- The OWASP Top Ten 2021
- Cloud security
- Input validation
- Wrap up
What you will learn
- Understand cloud security specialties
- 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
- Learn to deal with cloud infrastructure security
- Input validation approaches and principles
- Identify vulnerabilities and their consequences
- Learn the security best practices in C#
Description
Your cloud 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.
The cloud has become a critical aspect of online services. No matter which model you’re using (SaaS, PaaS, IaaS), part of your service is now operated by someone else. This may look like a net positive, but it also greatly expands the attack surface and brings in several new risks that may not be obvious. Have you configured all security settings correctly? Are you prepared for supply chain attacks? How can you protect the confidentiality of user data in the cloud? And most importantly: can the bad guys use your exposure to their advantage?
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 Azure cloud platform.
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
- Cloud security basics
- Cloud infrastructure basics
- The Cloud Cube Model and Zero Trust Architecture
- Case study – ChaosDB vulnerability in Azure Cosmos DB
- The OWASP Top Ten 2021
- The OWASP Top 10 2021
- A01 – 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
- Open redirects and forwards
- Case study – Unvalidated redirect at Epic Games
- Open redirects and forwards – best practices
- Cross-site Request Forgery (CSRF)
- Lab – Cross-site Request Forgery
- CSRF best practices
- CSRF defense in depth
- Lab – CSRF protection with tokens
- A02 – Cryptographic Failures
- Information exposure
- Exposure through extracted data and aggregation
- Case study – Strava data exposure
- Cryptography for developers
- Cryptography basics
- Crypto APIs in C#
- Elementary algorithms
- Random number generation
- Pseudo random number generators (PRNGs)
- Cryptographically strong 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
- Information exposure
- The OWASP Top Ten 2021
- A02 – Cryptographic Failures (continued)
- Cryptography for developers
- 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
- The RSA algorithm
- Using RSA – best practices
- RSA in C#
- The RSA algorithm
- Combining symmetric and asymmetric algorithms
- Some further key management challenges
- Symmetric encryption
- Confidentiality protection
- Certificates
- Certificates and PKI
- X.509 certificates
- Chain of trust
- PKI actors and procedures
- PGP – Web of Trust
- Certificate revocation
- Transport security
- Transport security weaknesses
- The TLS protocol
- TLS basics
- TLS features (changes in v1.3)
- The handshake in a nutshell (v1.3)
- TLS best practices
- Lab – Using a secure socket in C#
- HTTP Strict Transport Security (HSTS)
- Cryptography for developers
- A03 – 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
- NoSQL injection
- NoSQL injection basics
- NoSQL injection in MongoDB
- “NoSQL” injection in CosmosDB
- SQL injection best practices
- Input validation
- Parameterized queries
- Lab – Using prepared statements
- Additional considerations
- Case study – Hacking Fortnite accounts
- SQL injection protection and ORM
- Parameter manipulation
- CRLF injection
- 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
- A02 – Cryptographic Failures (continued)
- The OWASP Top Ten 2021
- A03 – Injection (continued)
- HTML injection – 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
- Further XSS protection techniques
- Lab – XSS fix / stored
- Lab – XSS fix / reflected
- Additional protection layers – defense in depth
- HTML injection – Cross-site scripting (XSS)
- A04 – Insecure Design
- The STRIDE model of threats
- Secure design principles of Saltzer and Schroeder
- Economy of mechanism
- Fail-safe defaults
- Complete mediation
- Open design
- Separation of privilege
- Least privilege
- Least common mechanism
- Psychological acceptability
- Client-side security
- Frame sandboxing
- Cross-Frame Scripting (XFS) attacks
- Lab – Clickjacking
- Clickjacking beyond hijacking a click
- Clickjacking protection best practices
- Lab – Using CSP to prevent clickjacking
- Frame sandboxing
- A05 – Security Misconfiguration
- Configuration principles
- Cookie security
- Cookie attributes
- XML entities
- 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
- A06 – Vulnerable and Outdated Components
- Using vulnerable components
- Untrusted functionality import
- Vulnerability management
- Patch management
- Vulnerability databases
- Lab – Finding vulnerabilities in third-party components
- A07 – Identification and Authentication Failures
- Authentication
- Authentication basics
- Multi-factor authentication
- Case study – PayPal 2FA bypass
- Session management
- Session management essentials
- Why do we protect session IDs – Session hijacking
- Session fixation
- Single sign-on (SSO)
- Single sign-on concept
- OAuth 2.0
- OAuth 2.0 basics
- OAuth 2.0 prerequisites
- OAuth 2.0 flow for Authorization Code Grant – Step #1
- OAuth 2.0 flow for Authorization Code Grant – Step #2
- OAuth 2.0 flow for Authorization Code Grant – Step #3
- OAuth 2.0 flow for Authorization Code Grant – Step #4
- OAuth 2.0 flow for Authorization Code Grant – Step #5
- OAuth 2.0 flow for Authorization Code Grant – Step #6
- OAuth 2.0 flow for Authorization Code Grant – Step #7
- OAuth 2.0 grant types
- Best practices
- Case study – Stealing SSO tokens from Epic Games accounts
- SAML
- SAML basics
- SAML profiles
- SAML security
- Identity and access management (IAM)
- Identity and access management in Azure
- Azure Active Directory
- Multi-factor authentication and password management with Azure
- Azure RBAC
- The Azure AD hybrid identity model
- Azure Shared Access Signatures (SAS)
- Authentication
- A03 – Injection (continued)
- The OWASP Top Ten 2021
- A07 – Identification and Authentication Failures (continued)
- 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 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
- Inbound password management
- Password management
- A08 – Software and Data Integrity Failures
- Integrity protection
- Message Authentication Code (MAC)
- Digital signature
- Elliptic Curve Cryptography
- ECC basics
- Digital signature with ECC
- Elliptic Curve Cryptography
- Subresource integrity
- Importing JavaScript
- Lab – Importing JavaScript
- Case study – The British Airways data breach
- Insecure deserialization
- Serialization and deserialization challenges
- Integrity – deserializing untrusted streams
- Integrity – deserialization best practices
- Property Oriented Programming (POP)
- Creating a POP payload
- Lab – Creating a POP payload
- Lab – Using the POP payload
- Integrity protection
- A09 – Security Logging and Monitoring Failures
- Logging and monitoring principles
- Insufficient logging
- Case study – Plaintext passwords at Facebook
- Logging best practices
- Detection and monitoring in Azure
- Utilizing Azure monitoring for security
- The Azure Security Center
- The Azure Application Gateway WAF
- A10 – Server-Side Request Forgery (SSRF)
- Server-side Request Forgery (SSRF)
- Case study – SSRF and the Capital One breach
- A07 – Identification and Authentication Failures (continued)
- Cloud security
- Azure security
- Security considerations for Azure
- Azure and security
- Azure security features
- The Azure shared responsibility model
- Azure hardening
- Security considerations for Azure
- Container security
- Container security concerns
- Containerization, virtualization and security
- The attack surface
- Docker security
- Docker and security
- Common Docker security mistakes
- Docker security best practices
- Lab – Static analysis of Docker images
- Hardening Docker
- Kubernetes security
- The Kubernetes architecture and security
- Securing Kubernetes hosts
- Best practices for Kubernetes access control
- Building secure Kubernetes images
- Secure deployment of Kubernetes containers
- Protecting Kubernetes deployments at runtime
- Case study – Azurescape
- Azure security
- Cloud security
- Data security in the cloud
- Data confidentiality and integrity in the cloud
- Data privacy in the cloud
- Compliance considerations
- Data security in Azure
- Storing cryptographic keys
- Protecting data at rest
- Protecting data in transit
- JSON security
- JSON validation
- JSON injection
- Dangers of JSONP
- JSON/JavaScript hijacking
- Best practices
- Case study – ReactJS vulnerability in HackerOne
- Data security in the cloud
- The OWASP Top Ten 2021
- Web application security beyond the Top Ten
- Code quality
- Data handling
- Initialization and cleanup
- Class initialization cycles
- Lab – Initialization cycles
- Object oriented programming pitfalls
- Inheritance and overriding
- Mutability
- Lab – Mutable object
- Readonly collections
- Denial of service
- Flooding
- Resource exhaustion
- Sustained client engagement
- Algorithm complexity issues
- Regular expression denial of service (ReDoS)
- Lab – ReDoS in C#
- Dealing with ReDoS
- Regular expression denial of service (ReDoS)
- Code quality
- Web application security beyond the Top Ten
- 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
- 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
- Using big integer libraries
- Integer handling in C#
- Lab – Checked arithmetics
- Files and streams
- Path traversal
- Lab – Path traversal
- Path traversal-related examples
- Additional challenges in Windows
- Virtual resources
- Path traversal best practices
- Lab – Path canonicalization
- 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
- Wrap up
- Secure coding principles
- Principles of robust programming by Matt Bishop
- And now what?
- Software security sources and further reading
- .NET and C# resources
- Secure coding principles
Pricing
5 days Session Price
3750 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