If you've identified a potential security flaw in our infrastructure or software, please let us know within 24 hours using GPG encryption. We'll triage the issue and get back to you within three business days.
Prior to reporting, please review the following information including our responsible disclosure policy, scope, reward information, and other guidelines.
Responsible Disclosure Policy
Palantir is proud to base our responsible disclosure policy on the https://disclose.io/ vulnerability disclosure framework. Security is one of our core tenets at Palantir, and we value the input of security professionals 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:
- Extend Safe Harbor for your vulnerability research that is related to this policy.
- Work with you to understand and validate your report, including a timely initial response to the submission.
- Work to remediate discovered vulnerabilities in a timely manner.
- 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. This recognition may result in award of financial compensation (see “Rewards”) at Palantir’s discretion if allowable under regulatory, compliance, and legal requirements.
To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you:
- Play by the rules. This includes following this policy, as well as any other relevant agreements.
- Politely report any vulnerability you’ve discovered promptly to the Palantir information security team. We reserve the right to disqualify individuals from the program for malicious, disrespectful or disruptive behavior.
- Include detailed information, including the process of replication, for the security issue in question.
- Do not engage in repeated submission of rejected, low-quality, or automated vulnerability reports.
- Do not access, modify, destroy, save, transmit, alter, transfer, use or view data belonging to anyone other than yourself. If a vulnerability provides unintended access to data, please cease testing, purge local information, and submit a report immediately.
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience.
- Keep the details of any discovered vulnerabilities confidential, according to the Disclosure Policy. Uncoordinated public disclosure of a vulnerability may result in disqualification from this program.
- Use only the official channels designated (see “Reporting”) to discuss vulnerability information with us.
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
- Do not engage in extortion, threats, or other tactics designed to elicit a response under duress. Palantir will not allow safe harbor or award rewards for vulnerability disclosure conducted under threat of full disclosure, exposure of data, or withholding of vulnerability information.
When conducting genuine in scope vulnerability research according to this policy, we consider this research to be:
- Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy when conducting genuine vulnerability research.
- Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls when conducting genuine vulnerability research according to this policy.
- Exempt from restrictions in our Terms & Conditions that would interfere with conducting genuine vulnerability security research, and we waive those restrictions on a limited basis for genuine vulnerability research done under this policy.
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
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 Reporting channels before going any further.
At this time, the following services and applications are in-scope:
- The palantir.com website and infrastructure.
- The Palantir Foundry bug bounty infrastructure.
- Any public (Internet-facing) infrastructure owned and operated by Palantir.
- Examples include firewalls, networking devices, compute instances, proxies, etc.
- Any public cloud (e.g. Amazon AWS, Microsoft Azure) resource or infrastructure operated and managed by Palantir.
- Public cloud storage accounts. (e.g. AWS S3 buckets, Azure data blobs)
- Public cloud compute servers. (e.g. AWS EC2 instances, Azure Virtual Machines)
- Anything with significant impact across our entire security posture or infrastructure.
Out Of Scope
- Attacks designed or likely to degrade, deny, or adversely impact services or user experience (e.g., Denial of Service, Distributed Denial of Service, Brute Force, Password Spraying, Spam...).
- Attacks designed or likely to destroy, corrupt, make unreadable (or attempts therein) data or information that does not belong to you.
- Attacks designed or likely to validate stolen credentials, credential reuse, account takeover (ATO), hijacking, or other credential-based techniques.
- Intentionally accessing data or information that does not belong to you beyond the minimum viable access necessary to demonstrate the vulnerability.
- Performing physical, social engineering, or electronic attacks against Palantir personnel, offices, wireless networks, or property.
- Security issues in third-party applications, services, or dependencies that integrate with Palantir products or infrastructure that do not have a demonstrable proof of concept for the vulnerability (e.g., libraries, SAAS services).
- Security issues or vulnerabilities created or introduced by the reporter (e.g., modifying a library we rely on to include a vulnerability for the sole purpose of receiving a reward).
- Attacks performed on any systems not explicitly mentioned as authorized and in-scope.
- Reports generated from automated vulnerability assessment tools.
- Reports of missing “best practices” or other guidelines which do not indicate a security issue.
- Attacks related to email servers, email protocols, email security (e.g., SPF, DMARC, DKIM), or email spam.
- Missing cookie flags on non-sensitive cookies.
- Reports of insecure SSL/TLS ciphers (unless accompanied with working proof of concept).
- Reports of how you can learn whether a given client can authenticate to a Palantir product or service.
- Reports of mappings between code names and client names.
- Reports of simple IP or port scanning.
- Reports of publicly resolvable or accessible DNS records for internal hosts or infrastructure.
- Reports of user-provided remote code execution in sandboxed environments (e.g., Product Features).
- Domain-based phishing, typosquatting, punycodes, bitflips, or other techniques.
- Violating any laws or breaching any agreements (or any reports of the same).
Palantir provides rewards to vulnerability reporters at its discretion. Our minimum reward is $250 USD. There is no maximum reward. Reward amounts may vary depending upon the severity of the vulnerability reported and quality of the report.
Palantir will only reward the first reporter of a vulnerability and only if a discovered vulnerability is deemed to be in scope and discovered and reported in compliance with this Policy.
To report a potential security issue or vulnerability, please follow this reporting process:
- Compile as much technical information as possible, including steps to reproduce and validate the issue.
- Encrypt the email contents using our GPG key.
- Notify the Palantir Computer Incident Response Team (CIRT) within 24 hours of discovery by emailing email@example.com. Please provide the best means of return communication.
- Allow up to 3 business days for confirmation of the reported issue.