Athenian Vulnerability Disclosure Policy


Effective Date: March 4, 2021

Effective Date: March 4, 2021

Athenian Vulnerability Disclosure Policy

We take the security of our systems seriously, and we value the security community. The disclosure of security vulnerabilities helps us ensure the security and privacy of our users help us to continuously improve.

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing mentioning "Vulnerability Disclosure" in the subject. Please include the following details with your report:

  • Description of the location and potential impact of the vulnerability;
  • A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
  • Your name/handle and a link for recognition in our Hall of Fame.


We require that all researchers:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
  • Perform research only within the scope set out below;
  • Use the identified communication channels to report vulnerability information to us; and
  • Keep information about any vulnerabilities you’ve discovered confidential between yourself and Athenian until we have had 90 days to resolve the issue.

If you follow these guidelines when reporting an issue to us, we commit to:

  • Not pursue or support any legal action related to your research;
  • Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 7 days of submission);
  • Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.
  • Keep information about any vulnerabilities you’ve discovered confidential between yourself and Athenian until we have had 90 days to resolve the issue.


In Scope:


Outside Scope:

  • Anything not listed "In Scope", including services hosted by third-party providers and services are excluded from scope.

In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:

  • Findings from physical testing (e.g. locations and devices)
  • Findings derived primarily from social engineering (e.g. phishing, vishing)
  • Findings from applications or systems not listed in the ‘Scope’ section
  • UI and UX bugs and spelling mistakes
  • Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive:

  • Personally identifiable information (PII)
  • Confidential information from third-parties
  • Credit card holder data

Policy Violation

If in violation of these terms at the Company's sole determination, the Company may suspend or terminate the Subscriber access to the Services without prior notice to the Subscriber and the Company will have no liability to the Subscriber regarding the deletion, blocking or removal of content or the suspension or termination of SaaS Services, and in certain cases prompting further legal action.

This policy was elaborated observing the best practices of the Open Source Vulnerability Disclosure Framework.