Skip to main content

At Dashwave, we take the security of our users' information and data as a top priority. We strive to put in the best practices and systems for protecting confidential user data and ensuring data privacy. In this document, we aim to provide an overview of the security measures we have in place to maintain the safety and privacy of our users' data.

Data Encryption in Transit

We use industry-standard encryption protocols to protect our users' data in transit. Our systems are equipped with TLS encryption, ensuring HTTPS and WSS protocols are being utilised for all kinds of data transfer along with mTLS and gRPCS (gRPC with SSL/TLS) for inter-services communication, preventing Man-in-the-Middle attacks and eavesdropping on all surface areas.

Data Encryption at Rest

We leverage the respective cloud providers’ storage security solutions to store the users’ or organizations’ confidential data and artefacts. The storage systems are encrypted with best-in-class algorithms delivered by the cloud provider, like 256-bit AES encryption, which is FIPS 140-2 compliant. This also lends us the benefit of the regular audits and assessments undertaken by the providers for keeping them aligned to industry standards. Read more about them here: AWS Key Management Service - AWS cryptography services (amazon.com), Azure Storage encryption for data at rest | Microsoft Learn, Google-managed encryption keys  |  Cloud Storage  |  Google Cloud.

Prevention of Unsolicited Remote Execution

Dashwave utilises cloud compute to facilitate Remote Execution of various jobs. Infrastructures of these kind, if not properly reinforced, expose a possibility of a Remote Code Execution breach, a severe attack vector. We try to fundamentally minimise the possibility of this happening by using application kernels, preventing container escapes and undue privilege escalations.

Access Control

Access to our systems and databases is strictly controlled and limited to authorized personnel only. We regularly review our access control policies and procedures to ensure that only those who require access are granted it.

Regular Backups

We perform regular backups of our data to ensure that in the event of a breach or data loss, we can quickly restore our systems to their previous state. Backups are encrypted and stored securely offsite.

Data Deletion

Logs generated by various events taking place on Dashwave are retained for a certain period of time and then periodically removed to maintain privacy and resource utilization. In any event, if you would like your data on Dashwave to be deleted, please feel free to contact us at security@dashwave.io.

Conclusion

At Dashwave, we are committed to maintaining the highest levels of security and privacy for our users and their data. We continuously review and update our security measures to stay ahead of potential threats and ensure that our users' information remains safe and secure. If you have any questions or concerns about our security practices, please do not hesitate to contact us at security@dashwave.io.

Dashwave is now live in public beta

Make builds faster using remote caching and collaborate with shareable emulators