Website Security Test of
abl.bme.unc.edu

Test Results Summary for abl.bme.unc.edu

• Web Software Security Test
  4 third-party web software dependancies were identified, including 3 outdated dependancies. No known vulnerabilities were detected. One identified third-party web software dependancy has an unknown version. The CMS (WordPress) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: jquery, modernizr, jquery-migrate. 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 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
  2 cookies detected; _ga_20PXKDCWVF, _ga have security or privacy-related configuration issues. Show details.
• External Content Security Test
  23 external requests detected; 3 requests failed. SRI is not used for 13 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  9 robots.txt rules, 1 User-Agent block and 7 bot protection mechanisms detected. No protection detected via meta restrictions. Show details.
• DNSSEC Configuration Test
  DNS A record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for abl.bme.unc.edu

• 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.