{"course":{"productid":24033,"modality":6,"active":true,"language":"de","title":"Desktop Application Security in Java","productcode":"DASEC-J","vendorcode":"CY","vendorname":"Cydrill","fullproductcode":"CY-DASEC-J","courseware":{"has_ekit":false,"has_printkit":true,"language":""},"url":"https:\/\/portal.flane.ch\/course\/cydrill-dasec-j","objective":"<ul>\n<li>Getting familiar with essential cyber security concepts<\/li><li>Identify vulnerabilities and their consequences<\/li><li>Learn the security best practices in Java<\/li><li>Input validation approaches and principles<\/li><li>Understanding how cryptography can support appplication security<\/li><li>Learning how to use cryptographic APIs correctly in Java<\/li><li>Managing vulnerabilities in third party components<\/li><\/ul>","essentials":"<p>General Java development<\/p>","audience":"<p>Java developers working on desktop applications<\/p>","contents":"<ul>\n<li>Cyber security basics<\/li><li>Input validation<\/li><li>Security features<\/li><li>Time and state<\/li><li>Errors<\/li><li>Cryptography for developers<\/li><li>Common software security weaknesses<\/li><li>Using vulnerable components<\/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\n<ul>\n<li>Constraints and the market<\/li><li>The dark side<\/li><\/ul><\/li><li>Categorization of bugs\n<ul>\n<li>The Seven Pernicious Kingdoms<\/li><li>Common Weakness Enumeration (CWE)<\/li><li>CWE Top 25 Most Dangerous Software Errors<\/li><li>SEI CERT Secure Coding Guidelines<\/li><\/ul><\/li><\/ul><p><strong>Input validation<\/strong>\n<\/p>\n<ul>\n<li>Input validation principles\n<ul>\n<li>Blacklists and whitelists<\/li><li>Data validation techniques<\/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>Validation with regex<\/li><\/ul><\/li><li>Injection\n<ul>\n<li>Injection principles<\/li><li>Injection attacks<\/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>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><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><\/ul><p><strong>DAY 2<\/strong><\/p>\n<p><strong>Security features<\/strong>\n<\/p>\n<ul>\n<li>Authentication\n<ul>\n<li>Authentication basics<\/li><li>Multi-factor authentication<\/li><li>Authentication weaknesses &ndash; spoofing<\/li><li>Case study &ndash; PayPal 2FA bypass<\/li><li>User interface best practices<\/li><li>Lab &ndash; On-line password brute forcing<\/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><li>Password length<\/li><li>Password hardening<\/li><li>Using passphrases<\/li><li>Lab &ndash; Applying a password policy<\/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>Outbound password management\n<ul>\n<li>Hard coded passwords<\/li><li>Best practices<\/li><li>Lab &ndash; Hardcoded password<\/li><li>Protecting sensitive information in memory\n<ul>\n<li>Challenges in protecting memory<\/li><li>Storing sensitive data in memory<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>Authorization\n<ul>\n<li>Access control basics<\/li><\/ul><\/li><li>Information exposure\n<ul>\n<li>Exposure through extracted data and aggregation<\/li><li>Case study &ndash; Strava data exposure<\/li><li>System information leakage\n<ul>\n<li>Leaking system information<\/li><\/ul><\/li><li>Information exposure best practices<\/li><\/ul><\/li><li>Java platform security\n<ul>\n<li>The Java programming language and runtime environment<\/li><li>Type safety and security<\/li><li>Security features of the JRE\n<ul>\n<li>The ClassLoader and the BytecodeVerifier<\/li><\/ul><\/li><li>Application-level access control in Java\n<ul>\n<li>Permissions and the Security Manager<\/li><li>Privilege best practices<\/li><\/ul><\/li><li>Role-based access control\n<ul>\n<li>Java Authentication and Authorization Services (JAAS)<\/li><\/ul><\/li><li>Protecting Java code and applications\n<ul>\n<li>Code signing<\/li><li>Lab &ndash; Code signing and permissions<\/li><\/ul><\/li><\/ul><\/li><li>UI security\n<ul>\n<li>UI security principles<\/li><li>Sensitive information in the user interface<\/li><li>Misinterpretation of UI features or actions<\/li><li>Insufficient UI feedback<\/li><li>Relying on hidden or disabled UI element<\/li><li>Insufficient anti-automation<\/li><\/ul><\/li><\/ul><p><strong>Time and state<\/strong>\n<\/p>\n<ul>\n<li>Race conditions\n<ul>\n<li>Race condition in object data members\n<ul>\n<li>Singleton member fields<\/li><li>Lab &ndash; Singleton member fields<\/li><\/ul><\/li><li>File race condition\n<ul>\n<li>Time of check to time of usage &ndash; TOCTTOU<\/li><li>Insecure temporary file<\/li><\/ul><\/li><li>Database race conditions\n<ul>\n<li>Lab &ndash; Database race conditions<\/li><\/ul><\/li><li>Avoiding race conditions in Java<\/li><\/ul><\/li><\/ul><p><strong>Errors<\/strong>\n<\/p>\n<ul>\n<li>Error and exception handling principles<\/li><li>Error handling\n<ul>\n<li>Returning a misleading status code<\/li><li>Reachable assertion<\/li><li>Information exposure through error reporting<\/li><\/ul><\/li><li>Exception handling\n<ul>\n<li>In the catch block. And now what?<\/li><li>Catching NullPointerException<\/li><li>Empty catch block<\/li><\/ul><\/li><\/ul><p><strong>DAY 3<\/strong><\/p>\n<p><strong>Cryptography for developers<\/strong>\n<\/p>\n<ul>\n<li>Cryptography basics<\/li><li>Java Cryptographic Architecture (JCA) in brief<\/li><li>Elementary algorithms\n<ul>\n<li>Random number generation\n<ul>\n<li>Pseudo random number generators (PRNGs)<\/li><li>Cryptographically strong PRNGs<\/li><li>Using virtual random streams<\/li><li>Weak and strong PRNGs in Java<\/li><li>Using random numbers in Java<\/li><li>Case study &ndash; Equifax credit account freeze<\/li><li>Lab &ndash; Random numbers in Java<\/li><\/ul><\/li><li>Hashing\n<ul>\n<li>Hashing basics<\/li><li>Common hashing mistakes<\/li><li>Hashing in Java<\/li><li>Lab &ndash; Hashing in JCA<\/li><\/ul><\/li><\/ul><\/li><li>Confidentiality protection\n<ul>\n<li>Symmetric encryption\n<ul>\n<li>Block ciphers<\/li><li>Modes of operation<\/li><li>Modes of operation and IV &ndash; best practices<\/li><li>Symmetric encryption in Java<\/li><li>Lab &ndash; Symmetric encryption in JCA<\/li><li>Asymmetric encryption\n<ul>\n<li>The RSA algorithm\n<ul>\n<li>Using RSA &ndash; best practices<\/li><li>RSA in Java<\/li><li>Lab &ndash; Using RSA in JCA<\/li><\/ul><\/li><li>Elliptic Curve Cryptography\n<ul>\n<li>The ECC algorithm<\/li><li>Using ECC &ndash; best practices<\/li><li>ECC in Java<\/li><li>Lab &ndash; Using ECC in JCA<\/li><\/ul><\/li><li>Combining symmetric and asymmetric algorithms<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>Integrity protection\n<ul>\n<li>Message Authentication Code (MAC)\n<ul>\n<li>Calculating MAC in Java<\/li><li>Lab &ndash; Using MAC in JCA<\/li><\/ul><\/li><li>Digital signature\n<ul>\n<li>Digital signature with RSA<\/li><li>Digital signature with ECC<\/li><li>Digital signature in Java<\/li><li>Lab &ndash; Digital signature in JCA<\/li><\/ul><\/li><\/ul><\/li><li>Public Key Infrastructure (PKI)\n<ul>\n<li>Some further key management challenges<\/li><li>Certificates\n<ul>\n<li>Chain of trust<\/li><li>Certificate management &ndash; best practices<\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>Common software security weaknesses<\/strong>\n<\/p>\n<ul>\n<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>Using vulnerable components<\/strong>\n<\/p>\n<ul>\n<li>Assessing the environment<\/li><li>Hardening<\/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><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 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>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- Identify vulnerabilities and their consequences\n- Learn the security best practices in Java\n- Input validation approaches and principles\n- Understanding how cryptography can support appplication security\n- Learning how to use cryptographic APIs correctly in Java\n- Managing vulnerabilities in third party components","essentials_plain":"General Java development","audience_plain":"Java developers working on desktop applications","contents_plain":"- Cyber security basics\n- Input validation\n- Security features\n- Time and state\n- Errors\n- Cryptography for developers\n- Common software security weaknesses\n- Using vulnerable components\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\n\n- Constraints and the market\n- The dark side\n- Categorization of bugs\n\n- The Seven Pernicious Kingdoms\n- Common Weakness Enumeration (CWE)\n- CWE Top 25 Most Dangerous Software Errors\n- SEI CERT Secure Coding Guidelines\nInput validation\n\n\n\n- Input validation principles\n\n- Blacklists and whitelists\n- Data validation techniques\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- Validation with regex\n- Injection\n\n- Injection principles\n- Injection attacks\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- 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\nDAY 2\n\nSecurity features\n\n\n\n- Authentication\n\n- Authentication basics\n- Multi-factor authentication\n- Authentication weaknesses \u2013 spoofing\n- Case study \u2013 PayPal 2FA bypass\n- User interface best practices\n- Lab \u2013 On-line password brute forcing\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- Password length\n- Password hardening\n- Using passphrases\n- Lab \u2013 Applying a password policy\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- Outbound password management\n\n- Hard coded passwords\n- Best practices\n- Lab \u2013 Hardcoded password\n- Protecting sensitive information in memory\n\n- Challenges in protecting memory\n- Storing sensitive data in memory\n- Authorization\n\n- Access control basics\n- Information exposure\n\n- Exposure through extracted data and aggregation\n- Case study \u2013 Strava data exposure\n- System information leakage\n\n- Leaking system information\n- Information exposure best practices\n- Java platform security\n\n- The Java programming language and runtime environment\n- Type safety and security\n- Security features of the JRE\n\n- The ClassLoader and the BytecodeVerifier\n- Application-level access control in Java\n\n- Permissions and the Security Manager\n- Privilege best practices\n- Role-based access control\n\n- Java Authentication and Authorization Services (JAAS)\n- Protecting Java code and applications\n\n- Code signing\n- Lab \u2013 Code signing and permissions\n- UI security\n\n- UI security principles\n- Sensitive information in the user interface\n- Misinterpretation of UI features or actions\n- Insufficient UI feedback\n- Relying on hidden or disabled UI element\n- Insufficient anti-automation\nTime and state\n\n\n\n- Race conditions\n\n- Race condition in object data members\n\n- Singleton member fields\n- Lab \u2013 Singleton member fields\n- File race condition\n\n- Time of check to time of usage \u2013 TOCTTOU\n- Insecure temporary file\n- Database race conditions\n\n- Lab \u2013 Database race conditions\n- Avoiding race conditions in Java\nErrors\n\n\n\n- Error and exception handling principles\n- Error handling\n\n- Returning a misleading status code\n- Reachable assertion\n- Information exposure through error reporting\n- Exception handling\n\n- In the catch block. And now what?\n- Catching NullPointerException\n- Empty catch block\nDAY 3\n\nCryptography for developers\n\n\n\n- Cryptography basics\n- Java Cryptographic Architecture (JCA) in brief\n- Elementary algorithms\n\n- Random number generation\n\n- Pseudo random number generators (PRNGs)\n- Cryptographically strong PRNGs\n- Using virtual random streams\n- Weak and strong PRNGs in Java\n- Using random numbers in Java\n- Case study \u2013 Equifax credit account freeze\n- Lab \u2013 Random numbers in Java\n- Hashing\n\n- Hashing basics\n- Common hashing mistakes\n- Hashing in Java\n- Lab \u2013 Hashing in JCA\n- Confidentiality protection\n\n- Symmetric encryption\n\n- Block ciphers\n- Modes of operation\n- Modes of operation and IV \u2013 best practices\n- Symmetric encryption in Java\n- Lab \u2013 Symmetric encryption in JCA\n- Asymmetric encryption\n\n- The RSA algorithm\n\n- Using RSA \u2013 best practices\n- RSA in Java\n- Lab \u2013 Using RSA in JCA\n- Elliptic Curve Cryptography\n\n- The ECC algorithm\n- Using ECC \u2013 best practices\n- ECC in Java\n- Lab \u2013 Using ECC in JCA\n- Combining symmetric and asymmetric algorithms\n- Integrity protection\n\n- Message Authentication Code (MAC)\n\n- Calculating MAC in Java\n- Lab \u2013 Using MAC in JCA\n- Digital signature\n\n- Digital signature with RSA\n- Digital signature with ECC\n- Digital signature in Java\n- Lab \u2013 Digital signature in JCA\n- Public Key Infrastructure (PKI)\n\n- Some further key management challenges\n- Certificates\n\n- Chain of trust\n- Certificate management \u2013 best practices\nCommon software security weaknesses\n\n\n\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\nUsing vulnerable components\n\n\n\n- Assessing the environment\n- Hardening\n- Vulnerability management\n\n- Patch management\n- Vulnerability databases\n- Lab \u2013 Finding vulnerabilities in third-party components\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 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\nAll 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:38:37+01:00","parenturl":"https:\/\/portal.flane.ch\/swisscom\/json-courses","nexturl_course_schedule":"https:\/\/portal.flane.ch\/swisscom\/json-course-schedule\/24033","source_lang":"de","source":"https:\/\/portal.flane.ch\/swisscom\/json-course\/cydrill-dasec-j"}}