Website Security Test of
www.visa.ca

Test Results Summary for www.visa.ca

• Web Software Security Test
  4 third-party web software dependancies were identified, including 2 outdated dependancies. A total of 4 known vulnerabilities were detected. 2 identified third-party web software dependancies have unknown versions. The CMS (PHP-Fusion) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: jquery-ui, jquery, Geeklog. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Website Security. 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. Optional HTTP headers appear to be properly configured: Server, Referrer-Policy, Cache-Control. 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, overly permissive directives. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  3 cookies detected; utag_main, languagecookie have security or privacy-related configuration issues. Show details.
• External Content Security Test
  18 external requests detected; all requests completed successfully. SRI is not used for 11 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.

Compliance Summary for www.visa.ca

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