Vulnerability Disclosure Policy

Intelligent RelationsSeptember 29, 2022 IntroductionIntelligent Relations is committed to maintaining the security of our systems and protecting sensitive information from unauthorized disclosure. Thi...

  • Home
  • Vulnerability Disclosure Policy

Intelligent Relations
September 29, 2022

Intelligent Relations is committed to maintaining the security of our systems and protecting sensitive information from unauthorized disclosure. This policy describes what systems and types of security research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems.

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Intelligent Relations will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Under this policy, “research” means activities in which you:

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Test Methods
Security researchers must not:

  • Test any system other than the systems set forth in the ‘Scope’ section below;
  • disclose vulnerability information, including any personally identifiable information, except as set forth in the ‘Reporting a Vulnerability’ and ‘Disclosure’ sections below;
  • engage in physical testing of facilities or resources;
  • engage in social engineering;
  • send unsolicited electronic mail to Intelligent Relations users, including, but not limited to, “phishing” messages;
  • execute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks;
  • introduce malicious software or code;
  • test in a manner which could degrade the operation of Intelligent Relations; or intentionally impair,
  • disrupt, or disable Intelligent Relations systems;
  • test third-party applications, websites, or services that integrate with or link to or from Intelligent Relations;
  • delete, alter, share, retain, or destroy Intelligent Relations data, or render Intelligent Relations data inaccessible; or,
  • use an exploit to exfiltrate data, establish command line access, establish a persistent presence on Intelligent Relations systems, or “pivot” to other Intelligent Relations systems.

The following systems / services are in scope:


Any services not explicitly listed above are excluded from scope. Additionally, vulnerabilities found in systems operated by a vendor fall outside of this policy’s scope and should be reported directly to the vendor according to the vendor’s disclosure policy (if any). Though we may develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.

Reporting a Vulnerability
Reports are accepted via electronic mail in English, preferably, to [email protected]. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.

What we would like to see from you:

In order to help us triage and prioritize submissions, we recommend that your reports:

  • Describe the location the vulnerability was discovered and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
  • Be in English, if possible.

What you can expect from us:

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

  • Within 3 business days, we will acknowledge that your report has been received.
  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
  • We will maintain an open dialogue to discuss issues.

Questions regarding this policy may be sent to [email protected]. We also invite you to contact us with suggestions for improving this policy.

1.029/09/2022First issuance.