{"course":{"productid":24048,"modality":6,"active":true,"language":"fr","title":"Security Testing C# Web Applications","productcode":"SECT-C#WA","vendorcode":"CY","vendorname":"Cydrill","fullproductcode":"CY-SECT-C#WA","courseware":{"has_ekit":false,"has_printkit":true,"language":""},"url":"https:\/\/portal.flane.ch\/course\/24048","objective":"<ul>\n<li>Getting familiar with essential cyber security concepts<\/li><li>Understanding Web application security issues<\/li><li>Detailed analysis of the OWASP Top Ten elements<\/li><li>Putting Web application security in the context of C#<\/li><li>Going beyond the low hanging fruits<\/li><li>Understanding security testing methodology and approaches<\/li><li>Getting familiar with common security testing techniques and tools<\/li><li>Managing vulnerabilities in third party components<\/li><li>Identify vulnerabilities and their consequences<\/li><li>Learn the security best practices in C#<\/li><li>Input validation approaches and principles<\/li><\/ul>","essentials":"<p>General C# and Web development, testing and QA<\/p>","audience":"<p>C# developers and testers working on Web applications<\/p>","contents":"<ul>\n<li>Cyber security basics<\/li><li>The OWASP Top Ten<\/li><li>Security testing<\/li><li>Common software security weaknesses<\/li><li>Wrap up<\/li><\/ul>","outline":"<p><strong>DAY 1 <\/strong><\/p>\n<p><strong>Cyber security basics<\/strong>\n<\/p>\n<ul>\n<li>What is security?<\/li><li>Threat and risk<\/li><li>Cyber security threat types<\/li><li>Consequences of insecure software<\/li><\/ul><p><strong>The OWASP Top Ten<\/strong>\n<\/p>\n<ul>\n<li>OWASP Top 10 &ndash; 2017<\/li><li>A1 &ndash; Injection\n<ul>\n<li>Injection principles<\/li><li>Injection attacks<\/li><li>SQL injection\n<ul>\n<li>SQL injection basics<\/li><li>Lab &ndash; SQL injection<\/li><li>Attack techniques<\/li><li>Content-based blind SQL injection<\/li><li>Time-based blind SQL injection<\/li><\/ul><\/li><li>SQL injection best practices\n<ul>\n<li>Input validation<\/li><li>Parameterized queries<\/li><li>Additional considerations<\/li><li>Lab &ndash; Using prepared statements<\/li><li>Case study &ndash; Hacking Fortnite accounts<\/li><li>Testing for SQL injection<\/li><\/ul><\/li><li>Code injection\n<ul>\n<li>OS command injection\n<ul>\n<li>Lab &ndash; Command injection<\/li><li>OS command injection best practices<\/li><li>Lab &ndash; Command injection best practices<\/li><li>Case study &ndash; Command injection via ping<\/li><li>Testing for command injection<\/li><\/ul><\/li><\/ul><\/li><li>General protection best practices<\/li><\/ul><\/li><li>A2 &ndash; Broken Authentication\n<ul>\n<li>Authentication basics<\/li><li>Multi-factor authentication<\/li><li>Authentication weaknesses &ndash; spoofing<\/li><li>Spoofing on the Web<\/li><li>Testing for weak authentication<\/li><li>Case study &ndash; PayPal 2FA bypass<\/li><li>Password management\n<ul>\n<li>Inbound password management\n<ul>\n<li>Storing account passwords<\/li><li>Password in transit<\/li><li>Lab &ndash; Is just hashing passwords enough?<\/li><li>Dictionary attacks and brute forcing<\/li><li>Salting<\/li><li>Adaptive hash functions for password storage<\/li><li>Password policy\n<ul>\n<li>NIST authenticator requirements for memorized secrets<\/li><\/ul><\/li><li>Case study &ndash; The Ashley Madison data breach\n<ul>\n<li>The dictionary attack<\/li><li>The ultimate crack<\/li><li>Exploitation and the lessons learned<\/li><\/ul><\/li><li>Password database migration\n<ul>\n<li>(Mis)handling passwords<\/li><li>Testing for password management issues<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>DAY 2<\/strong><\/p>\n<p><strong>Security testing<\/strong>\n<\/p>\n<ul>\n<li>Security testing vs functional testing<\/li><li>Manual and automated methods<\/li><li>Security testing methodology\n<ul>\n<li>Security testing &ndash; goals and methodologies<\/li><li>Overview of security testing processes<\/li><li>Identifying and rating assets\n<ul>\n<li>Preparation<\/li><li>Identifying assets<\/li><li>Identifying the attack surface<\/li><li>Assigning security requirements<\/li><li>Lab &ndash; Identifying and rating assets<\/li><\/ul><\/li><li>Threat modeling\n<ul>\n<li>SDL threat modeling<\/li><li>Mapping STRIDE to DFD<\/li><li>DFD example<\/li><li>Attack trees<\/li><li>Attack tree example<\/li><li>Lab &ndash; Crafting an attack tree<\/li><li>Misuse cases<\/li><li>Misuse case examples<\/li><li>Risk analysis<\/li><li>Lab &ndash; Risk analysis<\/li><\/ul><\/li><li>Security testing approaches\n<ul>\n<li>Reporting, recommendations, and review<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>The OWASP Top Ten<\/strong>\n<\/p>\n<ul>\n<li>A3 &ndash; Sensitive Data Exposure\n<ul>\n<li>Information exposure<\/li><li>Exposure through extracted data and aggregation<\/li><li>Case study &ndash; Strava data exposure<\/li><\/ul><\/li><li>A4 &ndash; XML External Entities (XXE)\n<ul>\n<li>DTD and the entities<\/li><li>Entity expansion<\/li><li>External Entity Attack (XXE)\n<ul>\n<li>File inclusion with external entities<\/li><li>Server-Side Request Forgery with external entities<\/li><li>Lab &ndash; External entity attack<\/li><li>Case study &ndash; XXE vulnerability in SAP Store<\/li><li>Lab &ndash; Prohibiting DTD<\/li><\/ul><\/li><\/ul><\/li><li>A5 &ndash; Broken Access Control\n<ul>\n<li>Access control basics<\/li><li>Failure to restrict URL access<\/li><li>Testing for authorization issues<\/li><li>Confused deputy\n<ul>\n<li>Insecure direct object reference (IDOR)<\/li><li>Lab &ndash; Insecure Direct Object Reference<\/li><li>Authorization bypass through user-controlled keys<\/li><li>Case study &ndash; Authorization bypass on Facebook<\/li><li>Lab &ndash; Horizontal authorization<\/li><li>Testing for confused deputy weaknesses<\/li><\/ul><\/li><li>File upload\n<ul>\n<li>Unrestricted file upload<\/li><li>Good practices<\/li><li>Lab &ndash; Unrestricted file upload<\/li><li>Testing for file upload vulnerabilities<\/li><\/ul><\/li><\/ul><\/li><li>A6 &ndash; Security Misconfiguration\n<ul>\n<li>Configuration principles<\/li><li>Configuration management<\/li><li>Testing for misconfiguration issues<\/li><\/ul><\/li><li>A7 &ndash; Cross-site Scripting (XSS)\n<ul>\n<li>Cross-site scripting basics<\/li><li>Cross-site scripting types\n<ul>\n<li>Persistent cross-site scripting<\/li><li>Reflected cross-site scripting<\/li><li>Client-side (DOM-based) cross-site scripting<\/li><li>Case study &ndash; XSS in Fortnite accounts<\/li><\/ul><\/li><li>XSS protection best practices\n<ul>\n<li>Protection principles &ndash; escaping<\/li><li>Lab &ndash; XSS fix \/ stored<\/li><li>Lab &ndash; XSS fix \/ reflected<\/li><li>Additional protection layers<\/li><li>Client-side protection principles<\/li><li>Testing for XSS<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>DAY 3<\/strong><\/p>\n<p><strong>The OWASP Top Ten<\/strong>\n<\/p>\n<ul>\n<li>A8 &ndash; Insecure Deserialization\n<ul>\n<li>Serialization and deserialization challenges<\/li><li>Deserializing untrusted streams<\/li><li>Deserialization best practices<\/li><li>Testing for insecure deserialization<\/li><li>Lab &ndash; Creating a POP payload<\/li><li>Lab &ndash; Using the POP payload<\/li><\/ul><\/li><li>A9 &ndash; Using Components with Known Vulnerabilities\n<ul>\n<li>Using vulnerable components<\/li><li>Untrusted functionality import<\/li><li>Importing JavaScript<\/li><li>Case study &ndash; The British Airways data breach<\/li><li>Vulnerability management\n<ul>\n<li>Patch management<\/li><li>Vulnerability databases<\/li><li>DevOps, the build process and CI \/ CD<\/li><\/ul><\/li><\/ul><\/li><li>A10 &ndash; Insufficient Logging &amp; Monitoring\n<ul>\n<li>Logging and monitoring principles<\/li><li>Insufficient logging<\/li><li>Plaintext passwords at Facebook<\/li><li>Logging best practices<\/li><\/ul><\/li><li>Web application security beyond the Top Ten\n<ul>\n<li>Client-side security<\/li><li>Tabnabbing<\/li><li>Lab &ndash; Reverse tabnabbing<\/li><li>Frame sandboxing\n<ul>\n<li>Cross-Frame Scripting (XFS) attack<\/li><li>Lab &ndash; Clickjacking<\/li><li>Clickjacking beyond hijacking a click<\/li><li>Clickjacking protection best practices<\/li><li>Lab &ndash; Using CSP to prevent clickjacking<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>Security testing<\/strong>\n<\/p>\n<ul>\n<li>Security testing techniques and tools\n<ul>\n<li>Code analysis\n<ul>\n<li>Security aspects of code review<\/li><li>Static Application Security Testing (SAST)<\/li><\/ul><\/li><li>Dynamic analysis\n<ul>\n<li>Security testing at runtime<\/li><li>Penetration testing<\/li><li>Stress testing<\/li><li>Dynamic analysis tools\n<ul>\n<li>Dynamic Application Security Testing (DAST)<\/li><li>Web vulnerability scanners<\/li><li>SQL injection tools<\/li><li>Proxy servers<\/li><\/ul><\/li><li>Fuzzing<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>Common software security weaknesses<\/strong>\n<\/p>\n<ul>\n<li>Input validation\n<ul>\n<li>Input validation principles\n<ul>\n<li>Blacklists and whitelists<\/li><li>Data validation techniques<\/li><li>Lab &ndash; Input validation<\/li><li>What to validate &ndash; the attack surface<\/li><li>Where to validate &ndash; defense in depth<\/li><li>How to validate &ndash; validation vs transformations<\/li><li>Output sanitization<\/li><li>Encoding challenges<\/li><li>Lab &ndash; Encoding challenges<\/li><li>Validation with regex<\/li><\/ul><\/li><li>Files and streams\n<ul>\n<li>Path traversal<\/li><li>Path traversal-related examples<\/li><li>Additional challenges in Windows<\/li><li>Path traversal best practices<\/li><li>Testing for path traversal<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>Wrap up<\/strong>\n<\/p>\n<ul>\n<li>Secure coding principles\n<ul>\n<li>Principles of robust programming by Matt Bishop<\/li><li>Secure design principles of Saltzer and Schr&ouml;der<\/li><\/ul><\/li><li>And now what?\n<ul>\n<li>Software security sources and further reading<\/li><li>Security testing resources<\/li><\/ul><\/li><\/ul>","summary":"<p>Your Web application written in C# is tested functionally, 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 -231? Because that&rsquo;s what the bad guys will do &ndash; and the list is far from complete.<\/p>\n<p>Testing for security needs a remarkable software security expertise and 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.<\/p>\n<p>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.A special focus is given to finding all discussed issues during testing, and an overview is provided on security testing methodology, techniques and tools.<\/p>\n<p>So that you are prepared for the forces of the dark side.<\/p>\n<p>So that nothing unexpected happens.<\/p>\n<p>Nothing.<\/p>","objective_plain":"- Getting familiar with essential cyber security concepts\n- Understanding Web application security issues\n- Detailed analysis of the OWASP Top Ten elements\n- Putting Web application security in the context of C#\n- Going beyond the low hanging fruits\n- Understanding security testing methodology and approaches\n- Getting familiar with common security testing techniques and tools\n- Managing vulnerabilities in third party components\n- Identify vulnerabilities and their consequences\n- Learn the security best practices in C#\n- Input validation approaches and principles","essentials_plain":"General C# and Web development, testing and QA","audience_plain":"C# developers and testers working on Web applications","contents_plain":"- Cyber security basics\n- The OWASP Top Ten\n- Security testing\n- Common software security weaknesses\n- Wrap up","outline_plain":"DAY 1 \n\nCyber security basics\n\n\n\n- What is security?\n- Threat and risk\n- Cyber security threat types\n- Consequences of insecure software\nThe OWASP Top Ten\n\n\n\n- OWASP Top 10 \u2013 2017\n- A1 \u2013 Injection\n\n- Injection principles\n- Injection attacks\n- SQL injection\n\n- SQL injection basics\n- Lab \u2013 SQL injection\n- Attack techniques\n- Content-based blind SQL injection\n- Time-based blind SQL injection\n- SQL injection best practices\n\n- Input validation\n- Parameterized queries\n- Additional considerations\n- Lab \u2013 Using prepared statements\n- Case study \u2013 Hacking Fortnite accounts\n- Testing for SQL injection\n- Code injection\n\n- OS command injection\n\n- Lab \u2013 Command injection\n- OS command injection best practices\n- Lab \u2013 Command injection best practices\n- Case study \u2013 Command injection via ping\n- Testing for command injection\n- General protection best practices\n- A2 \u2013 Broken Authentication\n\n- Authentication basics\n- Multi-factor authentication\n- Authentication weaknesses \u2013 spoofing\n- Spoofing on the Web\n- Testing for weak authentication\n- Case study \u2013 PayPal 2FA bypass\n- Password management\n\n- Inbound password management\n\n- Storing account passwords\n- Password in transit\n- Lab \u2013 Is just hashing passwords enough?\n- Dictionary attacks and brute forcing\n- Salting\n- Adaptive hash functions for password storage\n- Password policy\n\n- NIST authenticator requirements for memorized secrets\n- Case study \u2013 The Ashley Madison data breach\n\n- The dictionary attack\n- The ultimate crack\n- Exploitation and the lessons learned\n- Password database migration\n\n- (Mis)handling passwords\n- Testing for password management issues\nDAY 2\n\nSecurity testing\n\n\n\n- Security testing vs functional testing\n- Manual and automated methods\n- Security testing methodology\n\n- Security testing \u2013 goals and methodologies\n- Overview of security testing processes\n- Identifying and rating assets\n\n- Preparation\n- Identifying assets\n- Identifying the attack surface\n- Assigning security requirements\n- Lab \u2013 Identifying and rating assets\n- Threat modeling\n\n- SDL threat modeling\n- Mapping STRIDE to DFD\n- DFD example\n- Attack trees\n- Attack tree example\n- Lab \u2013 Crafting an attack tree\n- Misuse cases\n- Misuse case examples\n- Risk analysis\n- Lab \u2013 Risk analysis\n- Security testing approaches\n\n- Reporting, recommendations, and review\nThe OWASP Top Ten\n\n\n\n- A3 \u2013 Sensitive Data Exposure\n\n- Information exposure\n- Exposure through extracted data and aggregation\n- Case study \u2013 Strava data exposure\n- A4 \u2013 XML External Entities (XXE)\n\n- DTD and the entities\n- Entity expansion\n- External Entity Attack (XXE)\n\n- File inclusion with external entities\n- Server-Side Request Forgery with external entities\n- Lab \u2013 External entity attack\n- Case study \u2013 XXE vulnerability in SAP Store\n- Lab \u2013 Prohibiting DTD\n- A5 \u2013 Broken Access Control\n\n- Access control basics\n- Failure to restrict URL access\n- Testing for authorization issues\n- Confused deputy\n\n- Insecure direct object reference (IDOR)\n- Lab \u2013 Insecure Direct Object Reference\n- Authorization bypass through user-controlled keys\n- Case study \u2013 Authorization bypass on Facebook\n- Lab \u2013 Horizontal authorization\n- Testing for confused deputy weaknesses\n- File upload\n\n- Unrestricted file upload\n- Good practices\n- Lab \u2013 Unrestricted file upload\n- Testing for file upload vulnerabilities\n- A6 \u2013 Security Misconfiguration\n\n- Configuration principles\n- Configuration management\n- Testing for misconfiguration issues\n- A7 \u2013 Cross-site Scripting (XSS)\n\n- Cross-site scripting basics\n- Cross-site scripting types\n\n- Persistent cross-site scripting\n- Reflected cross-site scripting\n- Client-side (DOM-based) cross-site scripting\n- Case study \u2013 XSS in Fortnite accounts\n- XSS protection best practices\n\n- Protection principles \u2013 escaping\n- Lab \u2013 XSS fix \/ stored\n- Lab \u2013 XSS fix \/ reflected\n- Additional protection layers\n- Client-side protection principles\n- Testing for XSS\nDAY 3\n\nThe OWASP Top Ten\n\n\n\n- A8 \u2013 Insecure Deserialization\n\n- Serialization and deserialization challenges\n- Deserializing untrusted streams\n- Deserialization best practices\n- Testing for insecure deserialization\n- Lab \u2013 Creating a POP payload\n- Lab \u2013 Using the POP payload\n- A9 \u2013 Using Components with Known Vulnerabilities\n\n- Using vulnerable components\n- Untrusted functionality import\n- Importing JavaScript\n- Case study \u2013 The British Airways data breach\n- Vulnerability management\n\n- Patch management\n- Vulnerability databases\n- DevOps, the build process and CI \/ CD\n- A10 \u2013 Insufficient Logging & Monitoring\n\n- Logging and monitoring principles\n- Insufficient logging\n- Plaintext passwords at Facebook\n- Logging best practices\n- Web application security beyond the Top Ten\n\n- Client-side security\n- Tabnabbing\n- Lab \u2013 Reverse tabnabbing\n- Frame sandboxing\n\n- Cross-Frame Scripting (XFS) attack\n- Lab \u2013 Clickjacking\n- Clickjacking beyond hijacking a click\n- Clickjacking protection best practices\n- Lab \u2013 Using CSP to prevent clickjacking\nSecurity testing\n\n\n\n- Security testing techniques and tools\n\n- Code analysis\n\n- Security aspects of code review\n- Static Application Security Testing (SAST)\n- Dynamic analysis\n\n- Security testing at runtime\n- Penetration testing\n- Stress testing\n- Dynamic analysis tools\n\n- Dynamic Application Security Testing (DAST)\n- Web vulnerability scanners\n- SQL injection tools\n- Proxy servers\n- Fuzzing\nCommon software security weaknesses\n\n\n\n- Input validation\n\n- Input validation principles\n\n- Blacklists and whitelists\n- Data validation techniques\n- Lab \u2013 Input validation\n- What to validate \u2013 the attack surface\n- Where to validate \u2013 defense in depth\n- How to validate \u2013 validation vs transformations\n- Output sanitization\n- Encoding challenges\n- Lab \u2013 Encoding challenges\n- Validation with regex\n- Files and streams\n\n- Path traversal\n- Path traversal-related examples\n- Additional challenges in Windows\n- Path traversal best practices\n- Testing for path traversal\nWrap up\n\n\n\n- Secure coding principles\n\n- Principles of robust programming by Matt Bishop\n- Secure design principles of Saltzer and Schr\u00f6der\n- And now what?\n\n- Software security sources and further reading\n- Security testing resources","summary_plain":"Your Web application written in C# is tested functionally, 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 -231? Because that\u2019s what the bad guys will do \u2013 and the list is far from complete.\n\nTesting for security needs a remarkable software security expertise and 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.\n\nThe 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.A special focus is given to finding all discussed issues during testing, and an overview is provided on security testing methodology, techniques and tools.\n\nSo that you are prepared for the forces of the dark side.\n\nSo that nothing unexpected happens.\n\nNothing.","skill_level":"Intermediate","version":"1.0","duration":{"unit":"d","value":3,"formatted":"3 jours"},"pricelist":{"List Price":{"SI":{"country":"SI","currency":"EUR","taxrate":20,"price":2250},"DE":{"country":"DE","currency":"EUR","taxrate":19,"price":2250},"AT":{"country":"AT","currency":"EUR","taxrate":20,"price":2250},"GB":{"country":"GB","currency":"EUR","taxrate":20,"price":2250},"IT":{"country":"IT","currency":"EUR","taxrate":20,"price":2250},"NL":{"country":"NL","currency":"EUR","taxrate":21,"price":2250},"BE":{"country":"BE","currency":"EUR","taxrate":21,"price":2250},"FR":{"country":"FR","currency":"EUR","taxrate":19.6,"price":2250},"MK":{"country":"MK","currency":"EUR","taxrate":null,"price":2250},"GR":{"country":"GR","currency":"EUR","taxrate":null,"price":2250},"HU":{"country":"HU","currency":"EUR","taxrate":20,"price":2250}}},"lastchanged":"2026-01-12T11:34:38+01:00","parenturl":"https:\/\/portal.flane.ch\/swisscom\/fr\/json-courses","nexturl_course_schedule":"https:\/\/portal.flane.ch\/swisscom\/fr\/json-course-schedule\/24048","source_lang":"fr","source":"https:\/\/portal.flane.ch\/swisscom\/fr\/json-course\/24048"}}