x | close
Plandek is designed to collate & surface meta-data that does not contain sensitive client IP
Plandek data is sourced from the underlying tools used across the software delivery process. Key data sources are:
Plandek only stores metadata about the software development process and avoids storage of data which may hold sensitive IP (as such Plandek does NOT store data such as ticket descriptions, source code, commit messages, attachments or comments). Examples of metadata which Plandek may store includes information such as transitions of issues, the time of commits and pull requests and the person who performed the actions. For an exhaustive listing of data gathered, see Data Stored Per Gatherer document.
All access to tools such as Jira, Github, Bitbucket and CircleCI are performed over encrypted connections. Plandek uses read-only accounts and will never change data in the source systems. Our analysis is performed on short-lived Kubernetes pods and the raw data is purged once analysis is complete. For customers with specific privacy requirements, the gathering stage of the process can be run on the customer side so your intellectual property is never on Plandek servers. All data that Plandek holds is encrypted at rest and in transit.
All access credentials which are held are encrypted with Google Key Management Service, giving us the ability to monitor decryptions, revoke and rotate keys regularly.
The Plandek cloud platform is multi-tenant and as a consequence, we devote considerable resources to ensuring that your data can only be accessed by your team. We employ a variety of technical measures to ensure this separation including fine-grained role based permissions which are a key focus of our annual penetration tests. To date, our penetration tests have not found any weaknesses in our separation between customers.
Plandek has been architected to offer cloud and on-premise data-gatherer solutions.
Plandek holds all data in the Google Cloud Platform Belgium region. Metric data is stored in Elastic Cloud in the same Google Cloud region.
Plandek’s gatherers run on clients’ servers and connect to the APIs exposed by client services. They fetch raw data, which is stripped down to the minimal amount of metadata required to power the product. This metadata is then sent encrypted to Plandek’s API to be processed. This part of the system can run on-premise or in our cloud.
Processing runs on Plandek’s servers and converts the metadata into events which are used to generate the metrics that power the Plandek Web Application.
Metrics runs on Plandek’s servers and consumes the processed data from processing and generates metric data based on it.
Plandek’s web application is built in React, over a high performance Node.js backend. We conduct an external white box penetration test and security audit on our infrastructure and externally accessible services at least annually.
Plandek offers clients the option of an on-premise data gatherer. This option ensures that sensitive data (received automatically via the connected APIs and not required by Plandek) are removed from the dataset before its encrypted export into the cloud – and therefore such data never leaves the client’s network.
The Plandek data collection process is separated into several stages to ensure that your source code does not leave your network and to put minimal strain on your services.
The on-premise gatherers are designed to run on a kubernetes cluster and are packaged as a docker container. This comprises of a long-running orchestrating component which communicates with Plandek’s systems and launches short-lived gathering pods on the Kubernetes cluster.
Plandek is a highly secure environment
The Plandek platform is hosted on Google Cloud Platform in Belgium. Plandek follows Google’s best practices for configuration and security. The Plandek 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 the Plandek 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 Plandek web application is only available via HTTPS, protected by TLS.
Plandek 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.
Plandek undertakes 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 systems on a continuous basis using intruder.io
Plandek’s business processes are built around the security requirements of our enterprise clients
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.
Plandek supports authentication via Auth0, either with a username and password or via your own single sign on service. Our authentication system is built using Auth0. You can read more about Auth0’s security here: https://auth0.com/security. Plandek supports fine grained role based authentication.
All access credentials which we hold are encrypted with Google Key Management Service.
Plandek infrastructure covers multiple availability zones, and our databases are backed up and tested automatically daily.
Plandek has a comprehensive and robust incident response plan for handling security incidents, from identification, to rapid mitigation to the post-mortem process.
If clients believe that they have identified a security issue, they contact email@example.com and the team will be in touch (within a tight SLA) to learn more about it and work with the client to reproduce and resolve the issue.
Plandek is GDPR compliant
Covers the key questions about how Plandek handles data protection, access to data, incident management, backups & DR and pen testing.
Data stored by gatherer
Details of data stored by gatherer including: Github/Bitbucket/Gitlab, JIRA, Harvest, Tempo, Forecast and CI services.
On-premise data gathering
An overview of the Plandek data collection process covering: gathering, processing, metrics, and how this is deployed and managed.
Information security summary
An overview of Plandek’s information security covering all the topics on this page.
Details how Plandek uses personal data in compliance with GDPR.