Security and trust

Security

No AWS keys needed, secrets encrypted with per-customer keys, and downloads that never pass through StorHelm's servers.

01 — How it is built

Built so the files stay where they are.

StorHelm manages your storage without becoming a copy of it. These are the controls in the product today.

  • No AWS keys needed

    StorHelm assumes a cross-account IAM role in your AWS account, protected by a unique External ID. No customer keys are stored.

  • Per-customer encryption keys

    Stored secrets are encrypted with AWS KMS envelope encryption, using a separate key for each customer, and are never shown after entry.

  • Least privilege

    StorHelm needs only list, read, write and delete on the buckets you connect.

  • Files never pass through us

    Downloads and Azure transfers use short-lived signed links that expire after 15 minutes.

  • Tenant isolation

    Every organization's connections, jobs and scheduled tasks are scoped to that organization.

  • Role-based access

    Owner, Admin and Member roles decide who can connect buckets, invite people and change settings.

  • Every change is logged

    Each file-changing operation is recorded in Jobs, with who started it and what it touched.

  • HTTPS only

    StorHelm is hosted on AWS and is reachable only over HTTPS.

02 — Connecting with a role

How the IAM role connection works.

  1. StorHelm gives you a template

    The Credentials page provides a CloudFormation and trust-policy template with your organization's unique External ID.

  2. Your cloud team applies it

    The role is created in your own AWS account, limited to the bucket you choose.

  3. StorHelm assumes the role

    Access is granted through the role and can be withdrawn by you at any time by removing it.

03 — Questions

Security questions.

Do you store my files?

No. Files stay in your own bucket. StorHelm stores only file names, sizes, dates and storage classes, so it can search them.

Do you need my AWS keys?

No, not with an IAM role. StorHelm assumes a role in your AWS account using a unique External ID, so no keys are stored. Access keys are available as a quick start, and are encrypted at rest.

Which storage is supported?

Amazon S3 as the source. Azure Storage as a destination for copying or moving files.

See it on your own bucket.

Book a demo and we will connect a bucket together, index it, and walk through search, bulk operations and scheduling.