Vulnerability Disclosure Policy
Security is core to our values, and we value the input of security researchers acting in good faith to help us maintain a high standard for the security and privacy of our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.
When working with us according to this policy, you can expect us to:
- Work with you to understand and validate your report, including an initial response to the report within 72 hours of submission;
- Work to remediate discovered vulnerabilities in a timely manner; and
- Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
It is generally our practice not to prosecute security researchers who conduct vulnerability research in good faith and according to this policy.
You are expected, as always, to comply with all applicable laws.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
To encourage vulnerability research and to avoid any confusion between good-faith research and malicious attack, we ask that you:
- Play by the rules. This includes following this policy, as well as any other relevant agreements.
- Report any vulnerability you’ve discovered promptly;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- Keep the details of any discovered vulnerabilities confidential until they are fixed, according to the Disclosure Terms in this policy;
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- You should only interact with test accounts you own or with explicit permission from the account holder;
- Don’t perform high volume and/or distributed security scans; and
- Do not engage in extortion.
To help us receive vulnerability submissions we use the following official reporting channels:
If you think you’ve found a vulnerability, please include the following details with your report and be as descriptive as possible:
- The location and nature of the vulnerability;
- A detailed description of the steps required to reproduce the vulnerability (screenshots, compressed screen recordings, and proof-of-concept scripts are all helpful); and
- Your name/handle and a link for recognition.
If you’d like to encrypt the information, please use our PGP key
We may modify the terms of this program or terminate this program at any time.
We do not currently offer monetary rewards. If we accept your submission and it results in a code change, we offer company swag as a token of our appreciation along with recognition on our wall of fame.
The following Qualtrics web properties are in scope for the program.
The following conditions are out of scope for the vulnerability disclosure program. Any of these activities will result in disqualification from the program:
- Community forums (https://community.qualtrics.com/)
- Job board (www.qualtrics.com/careers)
- Physical attacks against Qualtrics employees, offices, or data centers
- Social engineering of Qualtrics employees, contractors, vendors, or service providers
- Knowingly posting, transmitting, uploading, linking to, or sending malware
- Pursuing vulnerabilities that send unsolicited bulk messages (spam) or unauthorized messages
- Any vulnerability obtained through compromise of a Qualtrics customer or employee account
- Being an individual on, or residing in any country on, any US sanctions lists
- Denial of Service attacks
- Missing HTTP headers (X-XSS-Protection, X-Frame-Options, CSP, etc.). This includes reports for clickjacking vulnerabilities.
- SSL/TLS cipher configuration
- Self XSS – Any cross-site scripting reports must include evidence of how it could be delivered to another user
Vulnerability details may not be disclosed without explicit permission from Qualtrics.