XBOW USA, INC.
Disclosure Policy
XBOW builds autonomous offensive security, so our own security is a core priority.
At XBOW, we’re grateful to work alongside the security community to identify and address vulnerabilities that could affect our services and customers. We genuinely appreciate every contribution and take each security report seriously.
If you believe you’ve found a vulnerability in an XBOW system, we want to hear from you. This policy explains what’s in scope, how to report, what you can expect from us, and how we protect researchers who act in good faith.
Thanks for working with us to keep our environment safe and secure.
In short: report to security@xbow.com. XBOW does not pay for vulnerability reports and does not operate a paid bug bounty program. Please read the full policy before you begin testing.
This policy is issued on behalf of XBOW USA, Inc., XBOW Malta Ltd and XBOW UK Operations Ltd (together, “XBOW”, “we” or “us”).Good faith research
We ask that all vulnerability research is conducted in good faith, with the primary goal of identifying, investigating or helping correct security flaws. Research is in good faith where it follows the policy below.
- Test only the XBOW assets listed as in scope below.
- Where you use the XBOW platform itself, point it only at assets you own or have explicit permission to test, and never at a third party.
- Report potential vulnerabilities promptly after discovery and initial validation.
- Keep reports clear and actionable.
- Validate your findings before reporting, and do not submit unvalidated AI-generated reports or large volumes of low-quality or low-impact automated-scanner output.
- Go only as far as necessary to establish that the vulnerability exists and to provide sufficient evidence of its potential impact. Don’t extract data, establish persistent access, or move into other systems.
- Respect the security and privacy of XBOW, our customers, and the public. Avoid service disruption, privacy violations, and changing or destroying data. Never knowingly or deliberately harm individuals or the public.
- Stop that line of testing and notify us immediately if you encounter sensitive information, including customer or personal data, financial or proprietary information, credentials, or another customer’s findings or scan results. Don’t access further information, or copy, use or share it. Retain only the minimum needed to describe the issue to us, and securely delete the remainder from all local systems and other storage once we confirm receipt.
- Treat all information gathered or created as part of your research and disclosure as sensitive, and handle it securely.
- Coordinate any public disclosure with us, as set out under Coordinated disclosure below.
- No stunt hacking, extortion, or harassment.
- Do not target XBOW employees, contractors or customers, including by social engineering, phishing or physical means.
Safe Harbour
Where such research is conducted in Good Faith and in accordance with this policy, we consider this to be an authorised activity and those conducting such activities shall be protected from legal action by us. This means:
We consider such activity exempt from restrictions in our Terms of Use and Terms and Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis,
We shall not bring legal action against you in respect of security research conducted in accordance with this policy, or in respect of a report submitted under it; and
We shall take steps to inform others (as is necessary) if someone else brings a claim against you.
This safe harbor applies only to legal claims under XBOW’s control. It does not bind third parties, including our customers.
You are expected, as always, to comply with all applicable laws.
If at any time you have concerns or are unsure whether your research is consistent with this policy, stop and email security@xbow.com before going any further.
Scope
In scope:
- xbow.com and its subdomains operated by XBOW
- The XBOW platform or publicly accessible pages only
Out of scope:
Assets not authorised for testing
- Deliberately vulnerable test, training, benchmark or interview environments that we operate
- Third-party services we use (please report these to the vendor)
- Targeting XBOW Customer assets or data
Prohibited testing methods
- Any testing that disrupts, degrades or impairs XBOW services or business operations
- Denial of service, volumetric testing or resource exhaustion
- Social engineering, phishing and physical testing
- Knowingly posting, transmitting, uploading, linking to, or sending malware
- Pursuing vulnerabilities which send unsolicited bulk messages (spam)
Findings generally not actionable without demonstrated impact
- Automated-scanner output with no demonstrated impact
- Missing security headers, cookie flags, TLS configuration, SPF or DMARC observations, version disclosure, self-XSS, and clickjacking on non-sensitive pages, absent a demonstrated attack chain
How to report a vulnerability
Email security@xbow.com with:
- The affected asset or URL, and the endpoint and parameters where applicable
- A description of the issue and its potential impact
- Steps to reproduce, with proof-of-concept code, screenshots or a short video where you can (do not copy or include any sensitive data, customer data or personal data, credentials, or another customer’s findings or scan results - descriptions may be provided as an alternative for the purposes of the proof).
- The name or handle you’d like us to credit, if any. You may report using a pseudonymous email address and we can still follow up and credit you. If you give us no way to reply, we cannot ask questions or offer credit.
Helpful Tips
- Make it reproducible. Include a clear description and detailed steps to reproduce the vulnerability. If we cannot reproduce it, we’ll ask for more information before marking it as triaged.
- Submit one vulnerability per report, unless a chain is needed to demonstrate impact.
- We review every report. Where an issue has already been reported, we will action the first report received that includes enough information to fully reproduce it.
- Vulnerabilities that share a single root cause will be treated as one valid report.
What you can expect from us
- We’ll triage your report within 5 business days.
- We’ll let you know whether we can reproduce the issue, keep you updated as we work on it, and tell you when it’s fixed.
- We won’t share your name or contact details without your permission.
- If a report suggests customer data may be affected, we’ll handle it under our incident response process and may limit what we can share while we investigate.
Coordinated disclosure
Please coordinate any public disclosure with us. We ask that you do not publish before we have confirmed a fix, and in any event not within 90 days of your report. Where remediation needs longer we will explain why and agree a revised date with you. We will not use this policy to delay disclosure unreasonably, and we are happy to be credited or quoted in your write-up.
Recognition
XBOW doesn’t run a paid bug bounty program, and submitting a report creates no expectation of payment. To say thank you, we’ll credit researchers who report valid, in-scope vulnerabilities on our upcoming Security Acknowledgments page, with your permission and under the name or handle you choose. For significant findings, we may also send XBOW swag as a thank-you.
Where the same issue is reported more than once, we credit the first report we receive that contains enough information to reproduce it. Later reports of the same issue are reviewed but are not separately credited.
We can only assess reports that include enough detail to reproduce the issue, and we do not require a call, a non-disclosure agreement or payment terms before receiving those details.
Questions
Send questions or suggestions about this policy to security@xbow.com.
Last updated: Friday November 20, 2026. Version 1.0.