Website Security Test of
www.lahars.gly.bristol.ac.uk

Test Results Summary for www.lahars.gly.bristol.ac.uk

• Web Software Security Test
  1 third-party web software dependancies were identified, including 1 outdated dependancies. A total of 3 known vulnerabilities were detected. No Content Management System (CMS) was identified. One CMS component, JS-library or framework was identified: jquery. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Privacy Policy, Website Security. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. Optional HTTP headers appear to be properly configured: Server, Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  One detected cookie appears to be properly configured from a security perspective. Show details.
• External Content Security Test
  7 external requests detected; all requests completed successfully. SRI is implemented for 1 out of 2 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.lahars.gly.bristol.ac.uk

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy, Website Security. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.