{"course":{"productid":26251,"modality":6,"active":true,"language":"de","title":"Web Application Security for PCI DSS","productcode":"WASEC-PCIDSS","vendorcode":"CY","vendorname":"Cydrill","fullproductcode":"CY-WASEC-PCIDSS","courseware":{"has_ekit":false,"has_printkit":true,"language":""},"url":"https:\/\/portal.flane.ch\/course\/cydrill-wasec-pcidss","objective":"<ul>\n<li>Getting familiar with essential cyber security concepts<\/li><li>Learning about security specialties of the finance sector<\/li><li>Having essential understanding of PCI DSS requirements<\/li><li>Managing vulnerabilities in third party components<\/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 any programming language<\/li><li>Going beyond the low hanging fruits<\/li><li>Understanding how cryptography supports security<\/li><li>Getting familiar with security testing techniques and tools<\/li><\/ul>","essentials":"<p>None for plenary, general Web development for secure coding<\/p>","audience":"<p>Managers and developers working on Web applications in finance<\/p>","contents":"<ul>\n<li>Cyber security basics<\/li><li>The OWASP Top Ten 2021<\/li><li>Security testing<\/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 &ndash; the CIA triad<\/li><li>Cyber security threat types &ndash; the STRIDE model<\/li><li>Consequences of insecure software<\/li><li>Constraints and the market<\/li><li>The dark side<\/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 Weaknesses<\/li><\/ul><\/li><li>Cyber security in the finance sector\n<ul>\n<li>Threats and trends in fintech<\/li><\/ul><\/li><li>PCI DSS\n<ul>\n<li>Overview<\/li><li>Requirements and secure coding (Requirements 1-5)<\/li><li>Req. 6 &ndash; Develop and maintain secure systems and applications<\/li><li>Requirement 6.5 &ndash; Address common coding vulnerabilities<\/li><li>Requirements and secure coding (Requirements 7-12)<\/li><\/ul><\/li><\/ul><p><strong>The OWASP Top Ten 2021<\/strong>\n<\/p>\n<ul>\n<li>A04 &ndash; Insecure Design\n<ul>\n<li>The STRIDE model of threats<\/li><li>Secure design principles of Saltzer and Schroeder<\/li><li>Client-side security\n<ul>\n<li>Frame sandboxing\n<ul>\n<li>Cross-Frame Scripting (XFS) attacks<\/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><\/li><li>A05 &ndash; Security Misconfiguration\n<ul>\n<li>Configuration principles<\/li><li>Server misconfiguration<\/li><li>Cookie security\n<ul>\n<li>Cookie security best practices<\/li><li>Cookie attributes<\/li><\/ul><\/li><li>XML entities\n<ul>\n<li>DTD and the entities<\/li><li>Attribute blowup<\/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 expansion<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>A06 &ndash; Vulnerable and Outdated Components\n<ul>\n<li>Using vulnerable components<\/li><li>Case study &ndash; The Equifax data breach<\/li><li>Assessing the environment<\/li><li>Hardening<\/li><li>Untrusted functionality import<\/li><li>Vulnerability management\n<ul>\n<li>Patch management<\/li><li>Vulnerability databases<\/li><li>Vulnerability rating &ndash; CVSS<\/li><li>Bug bounty programs<\/li><li>DevOps, the build process and CI \/ CD<\/li><\/ul><\/li><\/ul><\/li><li>A09 &ndash; Security Logging and Monitoring Failures\n<ul>\n<li>Logging and monitoring principles<\/li><li>Insufficient logging<\/li><li>Case study &ndash; Plaintext passwords at Facebook<\/li><li>Logging best practices<\/li><li>Monitoring best practices<\/li><li>Firewalls and Web Application Firewalls (WAF)<\/li><li>Intrusion detection and prevention<\/li><li>Case study &ndash; The Marriott Starwood data breach<\/li><\/ul><\/li><\/ul><p><strong>DAY 2<\/strong><\/p>\n<p><strong>The OWASP Top Ten 2021<\/strong>\n<\/p>\n<ul>\n<li>A01 &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><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><\/ul><\/li><li>A02 &ndash; Cryptographic Failures\n<ul>\n<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>Cryptography for developers\n<ul>\n<li>Cryptography basics<\/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>Lab &ndash; Using random numbers<\/li><li>Case study &ndash; Equifax credit account freeze<\/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>Lab &ndash; Symmetric encryption<\/li><\/ul><\/li><li>Asymmetric encryption<\/li><li>Combining symmetric and asymmetric algorithms<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>The OWASP Top Ten 2021<\/strong>\n<\/p>\n<ul>\n<li>A03 &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>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>Case study &ndash; Shellshock<\/li><li>Lab &ndash; Shellshock<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>DAY 3<\/strong><\/p>\n<p><strong>The OWASP Top Ten 2021<\/strong>\n<\/p>\n<ul>\n<li>A03 &ndash; Injection\n<ul>\n<li>HTML injection &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><\/ul><\/li><li>Lab &ndash; Stored XSS<\/li><li>Lab &ndash; Reflected XSS<\/li><li>Case study &ndash; XSS in Fortnite accounts<\/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 &ndash; defense in depth<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>The OWASP Top Ten 2021<\/strong>\n<\/p>\n<ul>\n<li>A07 &ndash; Identification and Authentication Failures\n<ul>\n<li>Authentication\n<ul>\n<li>Authentication basics<\/li><li>Multi-factor authentication<\/li><li>Time-based One Time Passwords (TOTP)<\/li><li>Authentication weaknesses<\/li><li>Spoofing on the Web<\/li><li>Case study &ndash; PayPal 2FA bypass<\/li><li>User interface best practices<\/li><li>Case study &ndash; Information disclosure in Simple Banking for Android<\/li><li>Lab &ndash; On-line password brute forcing<\/li><\/ul><\/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 hardening<\/li><li>Using passphrases<\/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><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><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>A08 &ndash; Software and Data Integrity Failures\n<ul>\n<li>Subresource integrity\n<ul>\n<li>Importing JavaScript<\/li><li>Lab &ndash; Importing JavaScript<\/li><li>Case study &ndash; The British Airways data breach<\/li><\/ul><\/li><li>Insecure deserialization\n<ul>\n<li>Serialization and deserialization challenges<\/li><li>Integrity &ndash; deserializing untrusted streams<\/li><li>Integrity &ndash; deserialization best practices<\/li><li>Property Oriented Programming (POP)\n<ul>\n<li>Creating payload<\/li><li>Lab &ndash; Creating a POP payload<\/li><li>Lab &ndash; Using the POP payload<\/li><li>Summary &ndash; POP best practices<\/li><\/ul><\/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>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><\/ul><\/li><li>Fuzzing<\/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><\/ul><\/li><li>And now what?\n<ul>\n<li>Software security sources and further reading<\/li><\/ul><\/li><\/ul>","summary":"<p>Your application written in any programming language 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&rsquo;s what the bad guys will do &ndash; and the list is far from complete.<\/p>\n<p>PCI DSS is a mandatory security standard for all companies developing or working with systems that handle credit cards. It does not only require following the secure coding guidelines out there, but also requires developers to train themselves on the latest best practices. But ticking the box annually is not enough.<\/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.<\/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>\n<p><em>Note: This course is customized for PCI DSS requirement 6.3 compliance, concerning both the content and the delivery structure.<\/em><\/p>\n<p><em>The course covers essential secure coding skills that are a must for all developers working with cardholder data and brings in a number of case studies from the financial sector.<\/em><\/p>\n<p><em>Aligned to the compliance requirements, the delivery of the training days can be done separately, breaking the course into two separate events that can span across year boundaries, aligned to your long-term compliance plans.<\/em><\/p>\n<p><em>Important: delivery of the 1-day initial plenary session can only be organized bundled (having at least two sessions batched).<\/em><\/p>","objective_plain":"- Getting familiar with essential cyber security concepts\n- Learning about security specialties of the finance sector\n- Having essential understanding of PCI DSS requirements\n- Managing vulnerabilities in third party components\n- Understanding Web application security issues\n- Detailed analysis of the OWASP Top Ten elements\n- Putting Web application security in the context of any programming language\n- Going beyond the low hanging fruits\n- Understanding how cryptography supports security\n- Getting familiar with security testing techniques and tools","essentials_plain":"None for plenary, general Web development for secure coding","audience_plain":"Managers and developers working on Web applications in finance","contents_plain":"- Cyber security basics\n- The OWASP Top Ten 2021\n- Security testing\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 \u2013 the CIA triad\n- Cyber security threat types \u2013 the STRIDE model\n- Consequences of insecure software\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 Weaknesses\n- Cyber security in the finance sector\n\n- Threats and trends in fintech\n- PCI DSS\n\n- Overview\n- Requirements and secure coding (Requirements 1-5)\n- Req. 6 \u2013 Develop and maintain secure systems and applications\n- Requirement 6.5 \u2013 Address common coding vulnerabilities\n- Requirements and secure coding (Requirements 7-12)\nThe OWASP Top Ten 2021\n\n\n\n- A04 \u2013 Insecure Design\n\n- The STRIDE model of threats\n- Secure design principles of Saltzer and Schroeder\n- Client-side security\n\n- Frame sandboxing\n\n- Cross-Frame Scripting (XFS) attacks\n- Lab \u2013 Clickjacking\n- Clickjacking beyond hijacking a click\n- Clickjacking protection best practices\n- Lab \u2013 Using CSP to prevent clickjacking\n- A05 \u2013 Security Misconfiguration\n\n- Configuration principles\n- Server misconfiguration\n- Cookie security\n\n- Cookie security best practices\n- Cookie attributes\n- XML entities\n\n- DTD and the entities\n- Attribute blowup\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 expansion\n- A06 \u2013 Vulnerable and Outdated Components\n\n- Using vulnerable components\n- Case study \u2013 The Equifax data breach\n- Assessing the environment\n- Hardening\n- Untrusted functionality import\n- Vulnerability management\n\n- Patch management\n- Vulnerability databases\n- Vulnerability rating \u2013 CVSS\n- Bug bounty programs\n- DevOps, the build process and CI \/ CD\n- A09 \u2013 Security Logging and Monitoring Failures\n\n- Logging and monitoring principles\n- Insufficient logging\n- Case study \u2013 Plaintext passwords at Facebook\n- Logging best practices\n- Monitoring best practices\n- Firewalls and Web Application Firewalls (WAF)\n- Intrusion detection and prevention\n- Case study \u2013 The Marriott Starwood data breach\nDAY 2\n\nThe OWASP Top Ten 2021\n\n\n\n- A01 \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- 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- A02 \u2013 Cryptographic Failures\n\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- Cryptography for developers\n\n- Cryptography basics\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- Lab \u2013 Using random numbers\n- Case study \u2013 Equifax credit account freeze\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- Lab \u2013 Symmetric encryption\n- Asymmetric encryption\n- Combining symmetric and asymmetric algorithms\nThe OWASP Top Ten 2021\n\n\n\n- A03 \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- 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- Case study \u2013 Shellshock\n- Lab \u2013 Shellshock\nDAY 3\n\nThe OWASP Top Ten 2021\n\n\n\n- A03 \u2013 Injection\n\n- HTML injection \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- Lab \u2013 XSS fix \/ stored\n- Lab \u2013 XSS fix \/ reflected\n- Additional protection layers \u2013 defense in depth\nThe OWASP Top Ten 2021\n\n\n\n- A07 \u2013 Identification and Authentication Failures\n\n- Authentication\n\n- Authentication basics\n- Multi-factor authentication\n- Time-based One Time Passwords (TOTP)\n- Authentication weaknesses\n- Spoofing on the Web\n- Case study \u2013 PayPal 2FA bypass\n- User interface best practices\n- Case study \u2013 Information disclosure in Simple Banking for Android\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 hardening\n- Using passphrases\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\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- A08 \u2013 Software and Data Integrity Failures\n\n- Subresource integrity\n\n- Importing JavaScript\n- Lab \u2013 Importing JavaScript\n- Case study \u2013 The British Airways data breach\n- Insecure deserialization\n\n- Serialization and deserialization challenges\n- Integrity \u2013 deserializing untrusted streams\n- Integrity \u2013 deserialization best practices\n- Property Oriented Programming (POP)\n\n- Creating payload\n- Lab \u2013 Creating a POP payload\n- Lab \u2013 Using the POP payload\n- Summary \u2013 POP best practices\nSecurity testing\n\n\n\n- Security testing techniques and tools\n\n- Code analysis\n\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- Fuzzing\nWrap up\n\n\n\n- Secure coding principles\n\n- Principles of robust programming by Matt Bishop\n- And now what?\n\n- Software security sources and further reading","summary_plain":"Your application written in any programming language 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\u2019s what the bad guys will do \u2013 and the list is far from complete.\n\nPCI DSS is a mandatory security standard for all companies developing or working with systems that handle credit cards. It does not only require following the secure coding guidelines out there, but also requires developers to train themselves on the latest best practices. But ticking the box annually is not enough.\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.\n\nSo that you are prepared for the forces of the dark side.\n\nSo that nothing unexpected happens.\n\nNothing.\n\nNote: This course is customized for PCI DSS requirement 6.3 compliance, concerning both the content and the delivery structure.\n\nThe course covers essential secure coding skills that are a must for all developers working with cardholder data and brings in a number of case studies from the financial sector.\n\nAligned to the compliance requirements, the delivery of the training days can be done separately, breaking the course into two separate events that can span across year boundaries, aligned to your long-term compliance plans.\n\nImportant: delivery of the 1-day initial plenary session can only be organized bundled (having at least two sessions batched).","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},"GB":{"country":"GB","currency":"EUR","taxrate":20,"price":2250},"DE":{"country":"DE","currency":"EUR","taxrate":19,"price":2250},"AT":{"country":"AT","currency":"EUR","taxrate":20,"price":2250},"SE":{"country":"SE","currency":"EUR","taxrate":25,"price":2250},"IT":{"country":"IT","currency":"EUR","taxrate":20,"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:32:39+01:00","parenturl":"https:\/\/portal.flane.ch\/swisscom\/json-courses","nexturl_course_schedule":"https:\/\/portal.flane.ch\/swisscom\/json-course-schedule\/26251","source_lang":"de","source":"https:\/\/portal.flane.ch\/swisscom\/json-course\/cydrill-wasec-pcidss"}}