Security and Data Protection¶
We prioritize top-notch data security and safeguard your intellectual property, adhering to GDPR compliance and utilizing ISO 27001 certified data centers. All data is handled and stored securely within Europe.
Visit https://trust.verda.com/ for more information about security at Verda.
This page gives an overview of how security works on Verda and links to the pages that cover each topic in full.
Data residency¶
Our data centers are located in Finland, and your data stays in the location you deploy to. Storage you attach to an instance must be in the same location as the instance.
See Locations and sustainability for the list of locations.
Shared responsibility¶
Security on Verda is shared between Verda and you. Verda operates and protects the infrastructure: the facilities, hardware, networking, and the software that runs our services. You are responsible for what runs inside your resources, such as the operating system, firewall, access management, data encryption, and your backups.
See Shared responsibility model for the full breakdown per service type.
Account and access¶
- Sign-in. Sign in with email and password, or link a Google, GitHub, or Microsoft Entra ID account under My Account > Linked accounts and sign in with it.
- Team roles. Each project member has a role: Owner, Admin, or Developer. Only the owner can edit billing details, transfer funds, or delete the project. See Role permissions.
- API credentials. Cloud API credentials are scoped to a single project and to the documented Public API endpoints. They are tied to the team member who created them and are deleted automatically if that member is removed from the project. See API credentials.
- Audit logs. Each project keeps a 90-day audit log of who did what, when, and from where, including sign-ins and two-factor changes. The project owner and admins can read and export it. See Audit logs.
Isolating your workloads¶
- Confidential Computing. Confidential VMs run inside a hardware-enforced Trusted Execution Environment that encrypts CPU and GPU memory while it is in use, and isolates your workload from the hypervisor and from Verda's own infrastructure. You can verify the full stack with attestation before running a workload. See Confidential Computing.
- Private Networks. Each private network runs on its own isolated overlay, scoped to a single project. Other customers cannot reach your instances by their private address, even when they use the same address ranges. See Security model.
- Bare metal. Bare metal customers are the sole tenant on their physical server. See Services overview.
- GPU memory on Instant Clusters. When a GPU is reset between allocations, its entire memory is zeroed, so no data from a previous workload can resurface. See Instant Cluster release notes.
Securing your instance¶
Your instance is yours to secure. Use SSH keys rather than passwords, set up a firewall, and keep services such as JupyterLab off the public internet.
- Securing your instance walks through
fail2ban,ufw, and extra hardening. - Manage SSH keys covers adding and removing keys.
- Recover SSH access helps if you lose access to an instance.
Deleting your data¶
Deleted block volumes and shared filesystems stay in the trash for 96 hours, during which they can be restored. To remove the data straight away, delete it permanently from Deleted volumes in the console, or through the API. This cannot be undone.
See Deleting storage for details.