Switchboard Visual Technologies, Inc., a leading vendor of remote collaboration software, is committed to ensuring the safety and security of our customers. Toward this end, Switchboard is now formalizing our policy for accepting vulnerability reports in our products. 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.
Switchboard’s Vulnerability Disclosure Program initially covers the following products:
While Switchboard may develop a number of other products, we ask that all security researchers submit vulnerability reports only for the stated product list. We intend to increase our scope as we build capacity and experience with this process.
Researchers who submit a vulnerability report to us will be given full credit on our website once the submission has been accepted and validated by our product security team. Switchboard may choose to provide a reward at Switchboard’s sole discretion based on the severity of the bug and the quality of the report.
Switchboard will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting Process. We openly accept reports for the currently listed Switchboard products. We agree not to pursue legal action against individuals who:
To submit a vulnerability report to Switchboard’s Product Security Team, please send an email to firstname.lastname@example.org.
We will use the following criteria to prioritize and triage submissions.
What we would like to see from you:
What you can expect from us:
If we are unable to resolve communication issues or other problems, Switchboard 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.
This document Version 1.0 was created 2022-02-04. We periodically update or renew this policy according to relevant compliance policies. Any updates will be noted below in the version notes.