Website Security Test of
circlefin.okta.com

Test Results Summary for circlefin.okta.com

• Web Software Security Test
  5 third-party web software dependancies were identified, including 5 outdated dependancies. A total of 3 known vulnerabilities were detected. No Content Management System (CMS) was identified. The following CMS components, JS-libraries or frameworks were identified: dompurify, preact, core-js, and others. Show details.
• GDPR Compliance Test
  Potential GDPR compliance issues were identified related to Website Security, 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 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: overly permissive directives, directive errors. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  2 cookies detected; JSESSIONID have security or privacy-related configuration issues. Show details.
• External Content Security Test
  16 external requests detected; all requests completed successfully. SRI is implemented for 5 out of 7 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  3 robots.txt rules and 3 bot protection mechanisms detected. No protection detected via User-Agent blocks or meta restrictions. Show details.
• DNSSEC Configuration Test
  DNS CNAME record detected; DNSSEC signatures are not present. Show details.

Compliance Summary for circlefin.okta.com

• GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Website Security, Cookie Disclaimer.
• PCI DSS Compliance Failed: Potential PCI DSS compliance issues were identified related to Requirements 6.3 and 6.4.