Website Security Test of
www.migrosbank.ch

Test Results Summary for www.migrosbank.ch

• Web Software Security Test
  The CMS (Magnolia) was identified, however, its version could not be determined. No CMS components, JS-libraries or frameworks were identified. Show details.
• GDPR Compliance Test
  No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security header misconfigured Content-Security-Policy. Some optional HTTP headers may not be properly configured: Content-Security-Policy-Report-Only, Permissions-Policy. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: overly permissive directives, directive errors, deprecated directives. The report-only Content-Security-Policy contains issues: directive errors, overly permissive directives, deprecated directives. Show details.
• Cookies Privacy and Security Test
  7 cookies detected; kameleoonVisitorCode, ASLBSA, ZX_2020AFX-S, OptanonConsent, JSESSIONID have security or privacy-related configuration issues. Show details.
• External Content Security Test
  44 external requests detected; all requests completed successfully. SRI is not used for 26 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  3 User-Agent blocks and 2 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.

Compliance Summary for www.migrosbank.ch

• GDPR Compliance Passed: No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.