13. Vulnerability disclosure

Scoutship is committed to ensuring the safety and security of our customers. We hope to foster an open partnership with the security community, and we recognize that the work the community does is important in continuing to ensure safety and security for all of our customers. We have developed this policy to both reflect our corporate values and to uphold our legal responsibility to good-faith security researchers that are providing us with their expertise.

We will not take legal action if

Scoutship will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting Disclosure Process. We openly accept reports for the currently listed products. We agree not to pursue legal action against individuals who:

• Engage in testing of systems/research without harming Scoutship or its customers.

• Engage in vulnerability testing within the scope of our vulnerability disclosure program.

• Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software, etc.

• Adhere to the laws of their location and the location of Scoutship. For example, violating laws that would only result in a claim by Scoutship (and not a criminal claim) may be acceptable as Scoutship is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.

• Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.

How to submit a vulnerability

To submit a vulnerability report to Scoutship's Product Security Team, please contact us with the subject "Vulnerability Disclosure".

Preference, prioritization and acceptance criteria

We will use the following criteria to prioritize and triage submissions. What we would like to see from you:

• Well-written reports in English will have a higher chance of resolution.

• Reports that include proof-of-concept code equip us to better triage.

• Reports that include only crash dumps or other automated tool output may receive lower priority.

• Please include how you found the bug, the impact, and any potential remediation.

• Please include any plans or intentions for public disclosure.

What you can expect from us:

• A timely response to your email.

• After triage, we will send an expected timeline, and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.

• An open dialog to discuss issues.

• Notification when the vulnerability analysis has completed each stage of our review.

• Credit after the vulnerability has been validated and fixed.

• If we are unable to resolve communication issues or other problems, may bring in a neutral third party (such as CERT/CC, ICS-CERT, or the relevant regulator) to assist in determining how best to handle the vulnerability.

Credit for vulnerability reports

Scoutship appreciates timely vulnerability reporting and assistance from these individuals:

• Kunal M.

• Sakshi P.