Website Security Test of
eeg.qa.ceribell.com

Test Results Summary for eeg.qa.ceribell.com

• Web Software Security Test
  3 third-party web software dependancies were identified, including 2 outdated dependancies. No known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: core-js, react, lodash. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Privacy Policy, 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 headers: missing Strict-Transport-Security; misconfigured Content-Security-Policy. An optional HTTP header may not be properly configured: Content-Security-Policy-Report-Only. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors, overly permissive directives. The report-only Content-Security-Policy contains issues: directive errors, overly permissive directives, deprecated directives. Show details.
• Cookies Privacy and Security Test
  One cookie detected; _dd_s has security or privacy-related configuration issues. Show details.
• External Content Security Test
  8 external requests detected; all requests completed successfully. SRI is not used for 5 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.
• DNSSEC Configuration Test
  DNS CNAME record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for eeg.qa.ceribell.com

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.