We know how important security is to our customers and that’s why we follow security best practices and have strict processes to keep your data safe. We work with the industry leading cybersecurity team at Cure53.de to undertake regular penetration tests and source code audits of our software and infrastructure.
Source Code Protection
All access to Github, Bitbucket and CircleCI are performed over encrypted connections. We never write data to these services. Our analysis is performed on ephemeral Kubernetes pods and the raw data is purged after running. We store only metadata about your processes, but we never store source code, commit messages, pull request descriptions, titles or comments. Buildtrakr only gathers data for projects and repositories which you follow in CircleCI.
Protection of your access tokens
All access tokens which we hold are encrypted with Google Key Management Service.
Employee access to customer data
No Buildtrakr employees will access your data unless it is necessary to resolve a support issue or to resolve an incident. We also respect the privacy of our customers, so when it is necessary to access your data in Buildtrakr, we will only view the minimum amount of data necessary to resolve the issue.
We limit the number of employees who have the ability to access customer data or production infrastructure to the minimum necessary to maintain and run the systems. We also require that employees with access to customer data are based in the EEA. All employees are also vetted before employment commences, and all contracts contain confidentiality clauses.
Buildtrakr employees do not have access to your source code.
Buildtrakr only supports authentication via Github and Bitbucket.com SSO. Our authentication system is built using Auth0. You can read more about Auth0’s security here: https://auth0.com/security/
Buildtrakr users automatically inherit the repository permissions that are stored in Github and Bitbucket.
The Buildtrakr platform is designed for performance and resilience and our systems maintain over 99% uptime.
Our platform is hosted on Google Cloud Platform in Belgium. We follow Google’s best practices for configuration and security. Our infrastructure and software is audited and pentested by Cure53 on a regular basis and any issues that are identified are rapidly resolved.
To read more about Google Cloud’s security see: https://cloud.google.com/security
Only our web application is exposed on the internet, all other resources are firewalled and only accessible via Google Cloud Identity-Aware Proxy or our VPN.
The Buildtrakr web application is only available via HTTPS, protected by TLS.
Our production database is Elasticsearch hosted by Elastic in Google Cloud Belgium. Elastic have an exemplary security model and we trust their ability to keep your data safe. See more about Elastic’s security here: https://www.elastic.co/cloud/security .
We store our metadata cache in Google Cloud Storage using customer supplied encryption keys and configuration in Postgres, encrypted at rest.
We never store or transmit data unencrypted.
Backups and Disaster Recovery
Our infrastructure covers multiple availability zones, and our databases are backed up and tested automatically daily.
All access to internal systems and tools are only possible through either a VPN or Google Cloud Identity Aware Proxy and all employee devices are encrypted. We also mandate strong passwords and 2FA for employee accounts.
Pentests and Vulnerability scanning
We undertake a white box source code audit and penetration test annually with Cure53. This covers our web applications and backend services and the underlying infrastructure.
We also run automated vulnerability scans to identify risks and weaknesses in our stack on a continuous basis.
Buildtrakr has a comprehensive and robust incident response plan for handling security incidents, from identification, to rapid mitigation to the post-mortem process.
When you purchase a paid Buildtrakr subscription, your payments are performed by Stripe, Buildtrakr never has access to your card details. Stripe is certified as a PCI Level 1 Service Provider. This is the most stringent level of certification available in the payments industry. You can read more about Stripe’s security here: https://stripe.com/docs/security
Reporting an issue
If you believe you have identified a security issue, please contact firstname.lastname@example.org and the team will be in touch to learn more about it and work with you to reproduce and resolve the issue.
Any other questions
If you have any other questions or concerns about our approach to security, please get in touch at email@example.com and we will be happy to answer any questions.