This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting related to the domain or any website owned by Iress that has a published security.txt file that references this policy. Therefore, websites published without a link to this policy are considered out of scope for this policy.

We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always complying with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.


If you believe you have found a security vulnerability relating to any Iress system, please submit a vulnerability report.

In your report, please include details of:

  • The website, IP or page where the vulnerability exists.
  • A brief description of the type of vulnerability, for example, “XSS vulnerability”.
  • The steps required to reproduce. These should be benign, non-destructive, proof of concept. It helps to ensure Iress can triage the report quickly and accurately. It also reduces the likelihood of duplicate reporting of vulnerabilities or malicious exploitation of some vulnerabilities.

Please direct your report to the address defined in the CONTACT field of the security.txt file of the domain in question.

If your submission contains sensitive information, please encrypt using the PGP public key located at:

Fingerprint 15317D31DD4580E9EE12A6BC8A2CDCEB40C341CC.

What to expect

After submitting your report, we will aim to respond to your report within five working days and aim to triage your report within ten working days. We'll also aim to keep you informed of our progress.

Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.

We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify our guidance, so please do continue to coordinate public release with us.


You must NOT:

  • Break any applicable law or regulations.
  • Access unnecessary, excessive or significant amounts of data.
  • Modify data in any Iress systems or services.
  • Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
  • Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
  • Disrupt any Iress services or systems.
  • Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with "best practice", for example missing security headers.
  • Submit reports detailing TLS configuration weaknesses, for example "weak" cipher suite support or the presence of TLS1.0 support.
  • Submit reports detailing DMARC configuration weaknesses, for example "No DMARC Record found" or "No DMARC Reject Policy".
  • Submit reports detailing Sender Policy Framework (SPF) configuration weakness, for example "No SPF Record Found" or "SPF record ends with ~all".
  • Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
  • Social engineer, 'phish' or physically attack any Iress staff or infrastructure.
  • Demand financial compensation in order to disclose any vulnerabilities.

You must:

  • Always consider the data protection requirements of the region(s) in question and comply with these rules - do not violate the privacy of any data Iress holds. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
  • Securely delete all data retrieved during your research as soon as it is no longer required, instructed by Iress or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).


This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with regional laws, or which might cause Iress or partner organisations to be in breach of any legal obligations in the territories Iress operate.