Website Security Test of
www.contrastsecurity.com

Test Results Summary for www.contrastsecurity.com

• Web Software Security Test
  3 third-party web software dependancies were identified, including 3 outdated dependancies. A total of 4 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: jquery, lit-html, jquery-migrate. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.4, while being non-compliant with Requirement 6.3. Show details.
• HTTP Headers Security Test
  Issues were identified with key security header misconfigured Content-Security-Policy. An optional HTTP header may not be properly configured: Report-To. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  16 cookies detected; __q_state_PK6AWFzWvCM5V41V, _uetvid, sliguid, osano_consentmanager_uuid, _ga_LVG2KS7RHZ, slireg, _zitok, osano_consentmanager, _hjSession_2245678, _hjSessionUser_2245678, _ga, _gcl_au, slirequested, _uetsid have security or privacy-related configuration issues. Show details.
• External Content Security Test
  92 external requests detected; 15 requests failed. SRI is not used for 36 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Show details.

Compliance Summary for www.contrastsecurity.com

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