Node.js web application security
26 Labs
14 Case Studies
Platform
Web
Audience
Node developers working on Web applications
Preparedness
General Node.js and Web development
Standards and references
OWASP, SEI CERT, CWE and Fortify Taxonomy
Group size
12 participants
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 JS/TS
- Understanding Web application security issues
- Detailed analysis of the OWASP Top Ten elements
- Putting Web application security in the context of JS/TS
- Going beyond the low hanging fruits
- Managing vulnerabilities in third party components
Description
Your Web application written in JS/TS 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 Node, and extended by core programming issues, discussing security pitfalls of the JS and TS language.
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
- Consequences of insecure software
- The OWASP Top Ten 2021
- A01 – Broken Access Control
- Access control basics
- Confused deputy
- Insecure direct object reference (IDOR)
- Path traversal
- Lab – Insecure Direct Object Reference
- Path traversal best practices
- 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 – Hacking Fortnite accounts
- Case study – Unvalidated redirect at Epic Games
- Open redirects and forwards – best practices
- A02 – Cryptographic Failures
- Information exposure
- Exposure through extracted data and aggregation
- Case study – Strava data exposure
- Cryptography for developers
- Cryptography basics
- Cryptography in Node.js
- Elementary algorithms
- Random number generation
- Pseudo random number generators (PRNGs)
- Cryptographically secure PRNGs
- Weak and strong PRNGs in Node.js
- Lab – Using random numbers in Node.js
- Case study – Equifax credit account freeze
- Hashing
- Hashing basics
- Hashing in Node.js
- Lab – Hashing in Node.js
- Random number generation
- Confidentiality protection
- Symmetric encryption
- Block ciphers
- Modes of operation
- Modes of operation and IV – best practices
- Symmetric encryption in Node.js via Crypto
- Symmetric encryption and decryption of streams in Node.js
- Lab – Symmetric encryption in Node.js
- Asymmetric encryption
- The RSA algorithm
- Using RSA – best practices
- RSA in Node.js
- The RSA algorithm
- Combining symmetric and asymmetric algorithms
- Symmetric encryption
- Information exposure
- A01 – Broken Access Control
- The OWASP Top Ten 2021
- 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
- SQL injection best practices
- Input validation
- Parameterized queries
- 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 – Shellshock
- Lab – Shellshock
- OS command injection
- 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
- Anti-XSS protection in Node.js
- Lab – XSS fix / stored
- Lab – XSS fix / reflected
- Additional protection layers – defense in depth
- XSS protection in Angular
- XSS protection in React
- XSS protection in Vue.js
- 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 protection best practices
- Lab – Using CSP to prevent clickjacking
- Frame sandboxing
- A05 – Security Misconfiguration
- Configuration principles
- Node.js configuration best practices
- General Node.js security considerations
- Express.js security
- Limiting resource use in Node.js apps
- Security headers
- Package manager considerations
- 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
- A03 – Injection
- The OWASP Top Ten 2021
- A06 – Vulnerable and Outdated Components
- Using vulnerable components
- Assessing the environment
- Hardening
- Untrusted functionality import
- Malicious packages in NPM
- Vulnerability management
- Patch management
- Vulnerability databases
- Lab – Finding vulnerabilities in third-party components
- DevOps, the CI / CD build process and Software Composition Analysis
- Dependency checking in NodeJS
- Lab – Detecting vulnerable components
- A07 – Identification and Authentication Failures
- 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 Node.js
- Password policy
- Case study – The Ashley Madison data breach
- The ultimate crack
- Exploitation and the lessons learned
- Inbound password management
- Authentication
- A08 – Software and Data Integrity Failures
- Integrity protection
- Message Authentication Code (MAC)
- MAC in Node.js
- Lab – Calculating MAC
- Digital signature
- Digital signature with RSA
- Elliptic Curve Cryptography
- ECC basics
- Digital signature with ECC
- Digital signature in Node.js
- Lab – Digital signature with ECDSA in Node.js
- Authenticated encryption
- Authenticated encryption modes of operation
- Authenticated encryption modes of operation: CCM
- Authenticated encryption modes of operation: GCM
- Message Authentication Code (MAC)
- Subresource integrity
- Importing JavaScript
- Lab – Importing JavaScript
- Subresource integrity in Angular
- Subresource integrity in Vue.js
- Case study – The British Airways data breach
- Insecure deserialization
- Serialization and deserialization challenges
- Integrity – deserializing untrusted streams
- Integrity – deserialization best practices
- Integrity protection
- A09 – Security Logging and Monitoring Failures
- Logging and monitoring principles
- Log forging
- Log forging – best practices
- Logging best practices
- A10 – Server-side Request Forgery (SSRF)
- Server-side Request Forgery (SSRF)
- Case study – SSRF and the Capital One breach
- A06 – Vulnerable and Outdated Components
- Wrap up
- Secure coding principles
- Principles of robust programming by Matt Bishop
- And now what?
- Software security sources and further reading
- NodeJS and JavaScript 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 Java
CYDJvWeb3d
3 days
>
Audience
Java developers working on Web applications
Group size
12 participants
Labs
Hands-on
Description
Your Web application written in Java 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 Java, and extended by core programming issues, discussing security pitfalls of the Java language and the runtime environment.
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 Java
- Understanding Web application security issues
- Detailed analysis of the OWASP Top Ten elements
- Putting Web application security in the context of Java
- Going beyond the low hanging fruits
- Managing vulnerabilities in third party components
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
Web application security in Python
CYDPyWeb3d
3 days
>
Audience
Python developers working on Web applications
Group size
12 participants
Labs
Hands-on
Description
Your Web application written in Python 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 Python, and extended by core programming issues, discussing security pitfalls of the programming language.
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 Python
- Understanding Web application security issues
- Detailed analysis of the OWASP Top Ten elements
- Putting Web application security in the context of Python
- Going beyond the low hanging fruits
- Managing vulnerabilities in third party components