Website Security Test of
atozworkforce.idprism-auth.amazon.com

Test Results Summary for atozworkforce.idprism-auth.amazon.com

• Web Software Security Test
  2 third-party web software dependancies were identified. All appear to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: core-js, react. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Privacy Policy. Show details.
• PCI DSS Compliance Test
  No obvious PCI DSS compliance issues were detected for Requirements 6.3 and 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options; misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors, deprecated directives, overly permissive directives, unknown directives. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  5 cookies detected; cwr_s, cwr_u, VIEWER_COUNTRY, USER_REGION, Cloudfront-Nonce have security or privacy-related configuration issues. Show details.
• External Content Security Test
  6 external requests detected; all requests completed successfully. Show details.
• Protection from Data Scraping Test
  11 User-Agent blocks and 10 bot protection mechanisms detected. No protection detected via robots.txt rules or meta restrictions. Show details.
• DNSSEC Configuration Test
  DNS CNAME record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for atozworkforce.idprism-auth.amazon.com

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Privacy Policy.
• PCI DSS Compliance Passed: No obvious PCI DSS compliance issues were detected for Requirements 6.3 and 6.4.