Vulnerability Disclosure Program Policy

ION Group looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

ION Group will make a best effort to meet the following response targets for hackers participating in our program:

We'll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

• Follow HackerOne's disclosure guidelines.

Authorization and Safe Harbor

Security research activities conducted in good faith, and in a manner consistent with this policy, will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Adheres to Gold Standard Safe Harbor.

Program Rules

The program scope includes any public-facing system owned, operated, or controlled by ION Group, including web applications hosted on those sites. The assets specifically stated as in scope may be subject to change throughout the lifetime of this program. Your activities under this program include:

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.

• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.

• When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).

• Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.

• Social engineering (e.g. phishing, vishing, smishing) is prohibited.

• Physical attacks are prohibited.

• Denial of Service attacks are prohibited.

• Large scale automated attacks using penetration testing software is prohibited.

• Avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder. Respect the availability and integrity of the analysis target.

• Upon conclusion of engagement, all records resulting from the engagement should be destroyed.

• Session Layer: HTTP Headers -- Researchers should add headers to requests such as: "X-HackerOne-Research: [H1 username]"

Vulnerabilities found in systems from our vendors fall outside of this policy's scope and should be reported directly to the vendor according to their disclosure policy (if any).

ION Group does not authorize, permit, or otherwise allow (expressly or impliedly) any person, including any individual, group of individuals, consortium, partnership, or any other business or legal entity to engage in any security research or vulnerability or threat disclosure activity that is inconsistent with this policy or the law. If you engage in any activities that are inconsistent with this policy or the law, you may be subject to criminal and/or civil liabilities.

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Clickjacking on pages with no sensitive actions

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Rate limiting or bruteforce issues on non-authentication endpoints

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies

• Configuration of or missing security headers.

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

• Tabnabbing

• Issues that require unlikely user interaction

• Improper logout functionality and improper session timeout.

• CORS misconfiguration without an exploitation scenario

• Broken link hijacking

• Lack of jailbreak detection in mobile apps.

• Lack of SSL Pinning

Thank you for helping keep ION and our users safe!