Cube Dev Security Statement

As a company that takes data security and privacy very seriously, we recognize that Cube’s information security practices are important to you. While we don’t like to expose too much detail around our practices (as it can empower the very people we are protecting ourselves against), we have provided some general information below to give you confidence in how we secure the data entrusted to us.

Data Center Security

Cube's applications and platforms, including Cube Cloud, are built using open-source technologies and deployed through Amazon's AWS, Google GCP, and Microsoft Azure cloud providers. The control plane of the Cube Cloud is located in the GCP us-central1 region, and our users have a choice over where their Cube Deployments will physically run. We maintain data encryption at rest, implement data filtration at the API level, and all of our APIs require token-based security. Cube employees cannot physically access data centers. Access is strictly limited to authorized personnel of the underlying cloud providers.

Protection from Data Loss or Corruption

Our databases are maintained on the Google Cloud SQL platform and are designed for disaster recovery and automatic failover. Account data is backed up at regular intervals throughout the day to multiple off-site locations.

Application Level Security

Cube Cloud supports multiple ways of user authentication, including password authentication as well as authentication through identity providers supporting SAML 2.0 and OAuth 2.0 protocols. Cube Cloud never stores plain-text passwords and always encrypts its databases at rest. All application communication is encrypted over SSL TLS 1.2 channels. We perform regular external security penetration tests throughout the year using different vendors. The tests involve high-level server penetration tests, in-depth testing for vulnerabilities inside the application, and social engineering drills.

Internal Protocol and Education

We continuously train employees on best security practices, including how to identify social engineering, phishing scams, and hackers. Employees on teams that have access to customer data (such as tech support and our engineers) undergo criminal history and credit background checks prior to employment. All employees sign a Privacy Safeguard Agreement outlining their responsibility in protecting customer data. All employees receive data privacy training. In order to protect our company from a variety of different losses, Cube has established a comprehensive insurance program. Coverage includes, but is not exclusive to: coverage for cyber incidents, data privacy incidents (including regulatory expenses), general error and omission liability coverage, excess cyber liability coverage, property and business interruption coverage, as well as international commercial general liability coverage.

Responsible Disclosure

If you’ve discovered a vulnerability in any Cube service, please don’t share it publicly. Instead, please submit a report to us at security@cube.dev. We review all security concerns brought to our attention, and we take a proactive approach to emerging security issues. Every day, new security issues and attack vectors are created. Cube strives to stay on top of the latest security developments both internally and by working with external security researchers and companies. We appreciate the community’s efforts in creating a more secure web. If you believe your account has been compromised or you see suspicious activity on your account, please email security@cube.dev.