Website Security Test of
med.emory.edu

Test Results Summary for med.emory.edu

• Web Software Security Test
  No third-party web software dependancies were identified. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Cookie Disclaimer. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Website Security. 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 header missing Content-Security-Policy. An optional HTTP header may not be properly configured: Access-Control-Allow-Origin. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy headers are not present. Show details.
• Cookies Privacy and Security Test
  7 cookies detected; stg_returning_visitor, stg_last_interaction, _pk_ses.600727ad-ac9b-4d49-b15f-e066a8e5aae0.04b7, _pk_id.600727ad-ac9b-4d49-b15f-e066a8e5aae0.04b7, stg_traffic_source_priority have security or privacy-related configuration issues. Show details.
• External Content Security Test
  17 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. Show details.
• DNSSEC Configuration Test
  2 DNS A records detected; DNSSEC signatures are not present. Show details.

Compliance Summary for med.emory.edu

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Website Security.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.