{"course":{"productid":24023,"modality":6,"active":true,"language":"de","title":"Web Application Security in Java","productcode":"WASEC-J","vendorcode":"CY","vendorname":"Cydrill","fullproductcode":"CY-WASEC-J","courseware":{"has_ekit":false,"has_printkit":true,"language":""},"url":"https:\/\/portal.flane.ch\/course\/cydrill-wasec-j","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 Java<\/li><li>Going beyond the low hanging fruits<\/li><li>Managing vulnerabilities in third party components<\/li><li>Identify vulnerabilities and their consequences<\/li><li>Learn the security best practices in Java<\/li><li>Input validation approaches and principles<\/li><\/ul>","essentials":"<p>General Java and Web development<\/p>","audience":"<p>Java developers working on Web applications<\/p>","contents":"<ul>\n<li>Cyber security basics<\/li><li>The OWASP Top Ten<\/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><\/ul><\/li><li>Code injection\n<ul>\n<li>OS command injection\n<ul>\n<li>OS command injection best practices<\/li><li>Using Runtime.exec()<\/li><li>Using ProcessBuilder<\/li><li>Case study &ndash; Shellshock<\/li><li>Lab &ndash; Shellshock<\/li><li>Case study &ndash; Command injection via ping<\/li><\/ul><\/li><li>Script injection<\/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>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 null passwords<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>DAY 2<br\/><\/strong><\/p>\n<p><strong>The OWASP Top Ten<\/strong>\n<\/p>\n<ul>\n<li>A2 &ndash; Broken Authentication\n<ul>\n<li>Session management\n<ul>\n<li>Session management essentials<\/li><li>Session ID best practices<\/li><li>Why do we protect session IDs &ndash; Session hijacking<\/li><li>Session fixation<\/li><li>Cross-site Request Forgery (CSRF)\n<ul>\n<li>Lab &ndash; Cross-site Request Forgery<\/li><li>CSRF best practices<\/li><li>CSRF defense in depth<\/li><li>Lab &ndash; CSRF protection with tokens<\/li><\/ul><\/li><li>Cookie security\n<ul>\n<li>Cookie security best practices<\/li><li>Cookie attributes<\/li><\/ul><\/li><\/ul><\/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>Preventing XXE<\/li><li>Lab &ndash; Prohibiting DTD expansion<\/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>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><\/ul><\/li><li>File upload\n<ul>\n<li>Unrestricted file upload<\/li><li>Good practices<\/li><li>Lab &ndash; Unrestricted file upload<\/li><\/ul><\/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>Lab &ndash; Stored XSS<\/li><li>Lab &ndash; Reflected XSS<\/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>XSS protection APIs in Java<\/li><li>XSS protection in JSP<\/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><\/ul><\/li><\/ul><\/li><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>Using ReadObject<\/li><li>Sealed objects<\/li><li>Look ahead deserialization<\/li><li>Property Oriented Programming (POP)\n<ul>\n<li>Creating payload<\/li><li>POP best practices<\/li><li>Lab &ndash; Creating a POP payload<\/li><li>Lab &ndash; Using the POP payload<\/li><\/ul><\/li><\/ul><\/li><li>A9 &ndash; Using Components with Known Vulnerabilities\n<ul>\n<li>Using vulnerable components<\/li><li>Assessing the environment<\/li><li>Hardening<\/li><li>Untrusted functionality import<\/li><li>Importing JavaScript<\/li><li>Lab &ndash; 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>Lab &ndash; Finding vulnerabilities in third-party components<\/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>Web application security beyond the Top Ten\n<ul>\n<li>Client-side security<\/li><li>Same Origin Policy\n<ul>\n<li>Tabnabbing<\/li><li>Lab &ndash; Reverse tabnabbing<\/li><\/ul><\/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>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>Integer handling problems\n<ul>\n<li>Representing signed numbers<\/li><li>Integer visualization<\/li><li>Integer overflow<\/li><li>Lab &ndash; Integer overflow<\/li><li>Signed \/ unsigned confusion in Java<\/li><li>Case study &ndash; The Stockholm Stock Exchange<\/li><li>Integer truncation<\/li><li>Best practices\n<ul>\n<li>Upcasting<\/li><li>Precondition testing<\/li><li>Postcondition testing<\/li><li>Using big integer libraries<\/li><li>Integer handling in Java<\/li><li>Lab &ndash; Integer handling<\/li><\/ul><\/li><\/ul><\/li><li>Files and streams\n<ul>\n<li>Path traversal<\/li><li>Path traversal-related examples<\/li><li>Lab &ndash; Path traversal<\/li><li>Additional challenges in Windows<\/li><li>Path traversal best practices<\/li><\/ul><\/li><li>Unsafe reflection\n<ul>\n<li>Reflection without validation<\/li><li>Lab &ndash; Unsafe reflection<\/li><\/ul><\/li><li>Unsafe native code\n<ul>\n<li>Native code dependence<\/li><li>Lab &ndash; Unsafe JNI<\/li><li>Best practices for dealing with native code<\/li><\/ul><\/li><\/ul><\/li><li>Code quality\n<ul>\n<li>Data handling\n<ul>\n<li>Initialization and cleanup\n<ul>\n<li>Constructors and destructors<\/li><li>Class initialization cycles<\/li><li>Lab &ndash; Initialization cycles<\/li><\/ul><\/li><li>Unreleased resource\n<ul>\n<li>The finalize() method &ndash; best practices<\/li><\/ul><\/li><\/ul><\/li><li>Object oriented programming pitfalls\n<ul>\n<li>Accessibility modifiers\n<ul>\n<li>Are accessibility modifiers a security feature?<\/li><li>Accessibility modifiers &ndash; best practices<\/li><li>Overriding and accessibility modifiers<\/li><\/ul><\/li><li>Inheritance and overriding<\/li><li>Mutability\n<ul>\n<li>Lab &ndash; Mutable object<\/li><\/ul><\/li><li>Cloning<\/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>Java resources<\/li><\/ul><\/li><\/ul>","summary":"<p>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 -231? Because that&rsquo;s what the bad guys will do &ndash; and the list is far from complete.<\/p>\n<p>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.<\/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.All this is put in the context of Java, and extended by core programming issues, discussing security pitfalls of the Java language and framework.<\/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 Java\n- Going beyond the low hanging fruits\n- Managing vulnerabilities in third party components\n- Identify vulnerabilities and their consequences\n- Learn the security best practices in Java\n- Input validation approaches and principles","essentials_plain":"General Java and Web development","audience_plain":"Java developers working on Web applications","contents_plain":"- Cyber security basics\n- The OWASP Top Ten\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- Code injection\n\n- OS command injection\n\n- OS command injection best practices\n- Using Runtime.exec()\n- Using ProcessBuilder\n- Case study \u2013 Shellshock\n- Lab \u2013 Shellshock\n- Case study \u2013 Command injection via ping\n- Script 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- 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 null passwords\nDAY 2\n\n\nThe OWASP Top Ten\n\n\n\n- A2 \u2013 Broken Authentication\n\n- Session management\n\n- Session management essentials\n- Session ID best practices\n- Why do we protect session IDs \u2013 Session hijacking\n- Session fixation\n- Cross-site Request Forgery (CSRF)\n\n- Lab \u2013 Cross-site Request Forgery\n- CSRF best practices\n- CSRF defense in depth\n- Lab \u2013 CSRF protection with tokens\n- Cookie security\n\n- Cookie security best practices\n- Cookie attributes\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- Preventing XXE\n- Lab \u2013 Prohibiting DTD expansion\n- A5 \u2013 Broken Access Control\n\n- Access control basics\n- Failure to restrict URL access\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- File upload\n\n- Unrestricted file upload\n- Good practices\n- Lab \u2013 Unrestricted file upload\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- Lab \u2013 Stored XSS\n- Lab \u2013 Reflected XSS\n- Case study \u2013 XSS in Fortnite accounts\n- XSS protection best practices\n\n- Protection principles \u2013 escaping\n- XSS protection APIs in Java\n- XSS protection in JSP\n- Lab \u2013 XSS fix \/ stored\n- Lab \u2013 XSS fix \/ reflected\n- Additional protection layers\n- Client-side protection principles\n- A8 \u2013 Insecure Deserialization\n\n- Serialization and deserialization challenges\n- Deserializing untrusted streams\n- Deserialization best practices\n- Using ReadObject\n- Sealed objects\n- Look ahead deserialization\n- Property Oriented Programming (POP)\n\n- Creating payload\n- POP best practices\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- Assessing the environment\n- Hardening\n- Untrusted functionality import\n- Importing JavaScript\n- Lab \u2013 Importing JavaScript\n- Case study \u2013 The British Airways data breach\n- Vulnerability management\n\n- Patch management\n- Vulnerability databases\n- Lab \u2013 Finding vulnerabilities in third-party components\nDAY 3\n\nThe OWASP Top Ten\n\n\n\n- Web application security beyond the Top Ten\n\n- Client-side security\n- Same Origin Policy\n\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\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- Integer handling problems\n\n- Representing signed numbers\n- Integer visualization\n- Integer overflow\n- Lab \u2013 Integer overflow\n- Signed \/ unsigned confusion in Java\n- Case study \u2013 The Stockholm Stock Exchange\n- Integer truncation\n- Best practices\n\n- Upcasting\n- Precondition testing\n- Postcondition testing\n- Using big integer libraries\n- Integer handling in Java\n- Lab \u2013 Integer handling\n- Files and streams\n\n- Path traversal\n- Path traversal-related examples\n- Lab \u2013 Path traversal\n- Additional challenges in Windows\n- Path traversal best practices\n- Unsafe reflection\n\n- Reflection without validation\n- Lab \u2013 Unsafe reflection\n- Unsafe native code\n\n- Native code dependence\n- Lab \u2013 Unsafe JNI\n- Best practices for dealing with native code\n- Code quality\n\n- Data handling\n\n- Initialization and cleanup\n\n- Constructors and destructors\n- Class initialization cycles\n- Lab \u2013 Initialization cycles\n- Unreleased resource\n\n- The finalize() method \u2013 best practices\n- Object oriented programming pitfalls\n\n- Accessibility modifiers\n\n- Are accessibility modifiers a security feature?\n- Accessibility modifiers \u2013 best practices\n- Overriding and accessibility modifiers\n- Inheritance and overriding\n- Mutability\n\n- Lab \u2013 Mutable object\n- Cloning\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- Java resources","summary_plain":"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 -231? Because that\u2019s what the bad guys will do \u2013 and the list is far from complete.\n\nHandling 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.\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.All this is put in the context of Java, and extended by core programming issues, discussing security pitfalls of the Java language and framework.\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 Tage"},"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:40:46+01:00","parenturl":"https:\/\/portal.flane.ch\/swisscom\/json-courses","nexturl_course_schedule":"https:\/\/portal.flane.ch\/swisscom\/json-course-schedule\/24023","source_lang":"de","source":"https:\/\/portal.flane.ch\/swisscom\/json-course\/cydrill-wasec-j"}}