Security

Security, for the team that reviews it

Z-Move, the agentless VM migration platform, reads your VMs through the cloud APIs and never logs in to them. This page answers what a security review asks: what Z-Move reads, where your keys go, what runs in your account, how data travels and who can see what.

In short

  • Your VMs are never stopped, changed or logged in to: Z-Move only reads snapshots through the cloud APIs.
  • Cloud keys are encrypted at rest, never written to logs, and deleted 30 days after the job ends.
  • Temporary workers accept no connections from the internet and are destroyed when the job ends.
  • TLS on every hop; relayed disks pass through memory and are never written to disk.
  • Administrators sign in with a second factor, and every change is recorded in an audit log.

What Z-Move reads, and what it never does

Z-Move works with snapshots and volumes through the cloud APIs. On AWS and Zadara it creates an image of the VM without rebooting it, which takes a snapshot of every disk; on Azure it snapshots each disk. It never installs anything in your VMs, never needs their passwords, and never stops or changes the source, so rolling back means carrying on with it.

The snapshots Z-Move creates are deleted after a completed migration. Snapshots and images you choose as the source are never deleted.

Your cloud keys

  • Encrypted at rest on the platform, never written to logs, and deleted 30 days after the job ends.
  • Never in a URL: the resource list is a POST, and the web server logs paths without query strings.
  • In the browser, the console remembers the keys you entered only during a sign-in session, for up to 12 hours, and forgets them at sign-out. A session left idle for 30 minutes signs out on its own, in every tab, and takes the remembered keys with it.
  • Endpoints you type (custom Zadara regions, export buckets) must use https and resolve only to public addresses, so they cannot point the platform at internal networks or the cloud metadata service.

The temporary workers in your account

The copy runs on temporary worker VMs that Z-Move launches in the clouds of the migration, tagged as Z-Move workers. When a worker starts, it carries only three things: its id, a random token valid for its own job, and the address of the Z-Move server. That is its whole configuration:

  • While its job runs, the worker receives the access key for its own side over TLS (source keys for the export worker, destination keys for the import worker) and keeps it in memory. That is why the permissions of the key are the real limit: see below.
  • A worker never reaches the platform's database, never gets the platform's encryption key and never sees another customer's data. Its token is refused for any other job.
  • Workers accept no connections from the internet. Their security group lets in only the Z-Move server, on the ports the boot test checks, and the workers open no service.
  • Workers are terminated when the job ends. Every 10 minutes a sweep terminates any worker left behind, and it reads the instance's tags first: an instance whose tags do not match is never touched.
WORKER_ID=ephemeral-<job>-export
WORKER_TOKEN=<random, valid for this job only>
BACKEND_URL=<the Z-Move server>
TMP_DIR=<scratch folder>

How your data travels

TLS on every hop. On the Zadara ↔ Zadara and AWS ↔ Zadara routes, the disks stream from the export worker to the import worker through the Z-Move relay, in memory, and are never written to disk on the way. Azure routes go straight between the clouds: a worker in Zadara reads the Azure snapshot itself, or uploads straight to an Azure managed disk.

With a private deployment, Z-Move runs inside your own infrastructure and every byte stays there.

Least privilege

Because the key reaches the workers, give it only what the migration needs:

  • AWS: EC2 permissions only, and no IAM role on any VM. A least-privilege IAM policy, which can only terminate instances Z-Move tagged and only touch the volumes it named, is available on request.
  • Zadara (zCompute): a dedicated user with the Member role only in the projects involved, with the AmazonEC2FullAccess policy in those projects. Tenant Admin is not needed.
  • Azure: a custom role with the disk and snapshot actions, or the built-in Contributor role, on the resource groups involved only, never on the whole subscription.
  • Encrypted EBS volumes keep their encryption. With a customer-managed KMS key, the key must allow the access key to use it through EBS.

Accounts, roles and the audit log

  • No public sign-up: accounts are created by administrators, with passwords of at least 12 characters.
  • Administrators sign in with a second factor, a code from an authenticator app.
  • Users see their own migrations; an administrator sees and manages only their own organisation.
  • Every change is recorded in an audit log: who, what, which resource, when and from which IP address. Passwords and secrets are never stored in it, and the code never changes or deletes its events.

The platform and this website

The platform sends HSTS, a strict Content Security Policy without inline scripts, and headers that forbid framing. It limits requests per IP, and an internal error shows only a short reference, never internal details. Dependencies are checked for known vulnerabilities, with updates proposed every week.

This website sets no cookies. Its statistics come from Plausible, without cookies, and its Content Security Policy allows no inline scripts. See the DPA, the subprocessors and the privacy policy.

FAQ

Security: questions

Something else? Write to hello [at] zmove.click

Do you store our cloud keys?

Only for the job: they are encrypted at rest, never written to logs, and deleted 30 days after the job ends, which leaves time for a retry.

Does our data pass through your servers?

On the Zadara ↔ Zadara and AWS ↔ Zadara routes, disks stream through the Z-Move relay over TLS, in memory, and are never written to disk. Azure routes go straight between the clouds. With a private deployment, everything stays in your infrastructure.

What can a worker VM do in our account?

Whatever the access key of its side allows, while its job runs. That is why we recommend a dedicated key with only the permissions the migration needs. Workers accept no connections from the internet and are terminated at the end.

Can a worker reach other customers' data?

No. Its token works only for its own job, and it never reaches the platform's database or another customer's data.

What if a worker is left running?

A sweep every 10 minutes terminates workers whose job has ended, after checking their tags. An instance whose tags do not match is never terminated.

Is there an audit trail?

Yes. Every change records who, what, which resource, when and from which IP address. Administrators see their own organisation's events.

Can we run Z-Move inside our own cloud?

Yes. With a private deployment, Z-Move and every byte it moves stay in your infrastructure.

Demo

See a full run, from wizard to boot test.

Book a demo and follow a complete migration: wizard, pre-checks, live session, boot test and cleanup.

Or write to hello [at] zmove.click

We only use these details to reply to you.