We understand that security is critical, and we follow best practices and strict procedures to keep our systems, and your data, safe.
All access to source code repositories is performed using encrypted connections, either via SSH or TLS. Depending on the version control system, access to private repositories is obtained via an SSH deploy key or a token. Haystack never writes to repositories.
Haystack does not persist source code files. At the point our system executes code analysis of source code files, it is performed on ephemeral instances and source code content is immediately purged after processing. We only persist file names and metrics to our database.
No Haystack staff will access private source code unless required for support reasons, or responding to an incident. In cases where staff must access source code in order to perform support, we will get your explicit consent each time, except when responding to a security issue or suspected abuse.
When working a support issue we do our best to respect your privacy as much as possible, we only access the minimum files and settings needed to resolve your issue.
Our products support single sign on (SSO) via GitHub.com for authentication.
Haystack enforces a password complexity standard and credentials are salted and encrypted using BCrypt.
Our systems have uptime of 99% or higher, and we proactively post status updates for production incidents.
Haystack hosts its infrastructure and data in Digital Ocean. We follow Digital Ocean's best practices which allows us to take advantage from their secured, distributed, fault tolerant environment. To find out more information about Digital Ocean security practices, see: https://www.digitalocean.com/legal/data-security/.
Our systems were designed and built with disaster recovery in mind. Our systems will continue to work should any one of those data centers fail.
All of our servers are within our own virtual private cloud (VPC) with network access controls that prevent unauthorized connections to internal resources.
Haystack uses automation to backup all datastores that contain customer data. On an application level, we produce audit logs for all activity.
Access to customer data is limited to authorized employees who require it for their job. All access to the Haystack websites is restricted to HTTPS encrypted connections.
Haystack enforces policies that requires strong password policies on GitHub, Google and Digital Ocean to ensure access to cloud services are protected.
All data sent to or from Haystack systems is encrypted in transit using 256 bit encryption. Sensitive data such as tokens and credentials are stored in a secured database, salted and encrypted.
Haystack implements an Incident Response Policy for handling security events which includes escalation procedures, rapid mitigation and post mortem. All employees are informed of our policies.
Haystack has developed a comprehensive set of security policies covering a range of topics. These policies are updated frequently and shared with all employees.
Haystack performs background checks on all new employees in accordance with local laws. The background check includes employment verification and criminal checks for US employees.
All employee contracts include a confidentiality agreement.
When you purchase a paid Haystack subscription, your credit card data is not transmitted through nor stored on our systems. Instead, we depend on Stripe, a company dedicated to this task. Stripe is certified to PCI Service Provider Level 1, the most stringent level of certification available. Stripe's security information is available online.
Your input and feedback on our security as well as responsible disclosure is always appreciated. If you've discovered a security concern, please email us at firstname.lastname@example.org. We'll work with you to make sure we understand the issue and address it. We consider security correspondence and vulnerabilities our highest priorities and will work to promptly address any issues that arise.
Thank you for helping us keep Haystack safe. We'd also like to specially thank the following people who have worked with us to resolve vulnerabilities in the past:
Note: We appreciate reports for any and all security issues, but we reserve listing on this page for people who have disclosed unknown vulnerabilities of high or critical severity, or have helped us in an ongoing manner.