Introduction
Orbus Software is committed to protecting our customers and their information. This policy provides security researchers with clear guidelines for conducting vulnerability discovery and sets out our preferences for submitting findings.
It explains which systems and research activities are covered, how to report vulnerabilities to us, and the timeframe we request before any public disclosure.
We encourage you to contact us to report potential vulnerabilities in our systems.
Authorisation
If you make a good-faith effort to follow this policy during your security research, we will consider your research authorised. We will work with you to understand and resolve issues quickly, and Orbus Software will not recommend or pursue legal action related to your research. If a third party initiates legal action for activities conducted in accordance with this policy, we will make this authorisation known.
Guidelines
Under this policy, “research” includes activities where you:
- Notify us as soon as possible after discovering 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.
- Use exploits only to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent access, or pivot to other systems.
- Provide us with a reasonable amount of time to resolve the issue before publicly disclosing it.
- Avoid submitting a high volume of low-quality reports.
- Immediately stop testing, notify us, and refrain from disclosing any sensitive data if you encounter it (including personally identifiable information, financial information, or proprietary information or trade secrets).
Test methods
The following test methods are not authorised:
- Network denial of service (DoS or DDoS) tests or any tests that impair access to or damage a system or data.
- Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing.
Scope
This policy applies to Orbus Software-owned systems and services that we explicitly designate as in scope for testing. Any service not expressly identified as in scope, including connected services, is excluded and not authorised for testing. Vulnerabilities in systems belonging to our vendors or customers fall outside this policy and should be reported directly to the respective party according to their disclosure policy (if any). If you are unsure whether a system is in scope, please contact us before starting your research.
Although we develop and maintain other internet-accessible systems and services, we ask that active research and testing only be conducted on systems and services that we have confirmed as in scope. If you believe a particular system merits testing, please contact us to discuss it first. We will update and expand the scope of this policy over time.
Reporting a vulnerability
Information submitted under this policy will be used for defensive purposes only, to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect users beyond Orbus Software, we may share relevant details with appropriate coordination bodies under a responsible disclosure process. We will not share your name or contact information without your express permission.
Please submit vulnerability reports via email to infosec@orbussoftware.com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 5 business days.
What we would like to see from you
To help us triage and prioritise submissions, please include:
- The location of the vulnerability and the potential impact of exploitation.
- A detailed description of the steps required to reproduce the issue (proof-of-concept scripts or screenshots are helpful).
- Reports in English, if possible.
What you can expect from us
When you provide contact information, we commit to coordinating with you as openly and quickly as possible.
- Within 5 business days, we will acknowledge receipt of your report.
- We will, to the best of our ability, confirm the existence of the vulnerability and be as transparent as possible about remediation steps, including any issues or challenges that may delay resolution.
Questions
Questions regarding this policy may be sent to infosec@orbussoftware.com. We also welcome suggestions for improving this policy.