Policies

Security

How EmpireVault Auctions protects operators, sellers and buyers. Every statement on this page was checked against the product's code and deployment before it was written. Stage 1 is built and running as a demonstration; it has not yet run a real sale.

Signing In

  • Staff sign in with an account held by WorkOS, an identity platform: the same one they use for EmpireVault, if they have one. WorkOS checks the password; Auctions stores no staff password.
  • Buyers have their own passwords, stored only as bcrypt hashes. A password needs at least twelve characters and is checked against Have I Been Pwned's list of passwords exposed in breaches. Only the first five characters of a hash of the password are sent; the password itself never leaves our servers.
  • A buyer must verify their email address before registering for an auction or placing a bid.
  • Password-reset links work once and expire after thirty minutes. Only a digest of each link is stored.
  • Sign-in, registration and password-reset pages answer the same way whether or not an address has an account.
  • Sessions use secure, HTTP-only cookies and are checked on the server on every request. A staff session ends after sixty minutes without use and after twelve hours at most.
  • Suspending a staff member or a buyer ends their sessions at once.
  • Sign-in, registration, password reset and bidding are rate-limited, and repeated wrong passwords lock a buyer's account.

Access Control

  • Staff hold one of six roles: administrator, auction manager, cataloguer, finance, site staff or read-only. Each staff page checks the role before it does anything.
  • The reserve price is shown only to administrators, auction managers and finance. The public sees whether a reserve has been met, never the figure.
  • Other buyers see a bidder as a paddle number, never a name.
  • A restricted document can be downloaded only by buyers whose registration for that auction is approved. Files are never handed out as direct storage links.
  • Photographs are served as re-encoded copies with their metadata removed.

Encryption

Data in Transit

Every page is served over HTTPS, and plain HTTP is redirected to it. Certificates are issued and renewed automatically through cert-manager with Let's Encrypt.

Data at Rest

The credentials Auctions holds for other systems, which are your EmpireVault API key and the password of a mail server you connect, are encrypted in the application with Rails ActiveRecord Encryption (AES-256-GCM). The API key is never shown again after it is saved.

Tenant Isolation

Auctions is a multi-tenant platform. Every record belongs to one operator, and every query is scoped to the operator whose site is being used.

  • Tenant scoping on every business record; a query with no operator set is refused
  • Records that refer to each other must belong to the same operator
  • Unique indexes include the operator, so one operator's data cannot collide with another's

Records That Cannot Be Changed

Auctions keeps an append-only audit log of sign-ins, registrations, bids, and changes to lots and documents.

  • The database itself refuses to update or delete audit records, bids and payment entries
  • Issued invoices and release documents are frozen: a correction is a new entry, not an edit
  • The account the application uses cannot switch these protections off

Bidding Integrity

Whether a bid arrived in time is decided by one clock on the server. A buyer's device, browser or email delay plays no part in it.

Payments

Auctions does not process card payments and holds no card data. Buyers pay by wire; your finance staff record each receipt, and a recorded receipt cannot be edited, only reversed by a new entry.

Deployment Security

  • Non-root containers: the application runs as an unprivileged user, with privilege escalation switched off
  • Multi-stage Docker builds: production images contain only what is needed to run
  • Kubernetes Secrets: credentials are stored in Kubernetes Secrets, never in the code
  • A strict content security policy limits which scripts a page may run

Checks on Every Change

Every code change is checked automatically before it is merged.

  • Brakeman: static security analysis for common Rails vulnerabilities
  • bundler-audit: Ruby dependencies checked against known vulnerabilities
  • importmap audit: JavaScript dependencies checked against known vulnerabilities
  • The full test suite, including tests that drive a browser

Other Services

Auctions sends data to a short list of outside services: WorkOS for staff sign-in, file storage for photographs and documents, your mail server or ours for email, Have I Been Pwned for the password check described above, and EmpireVault if you connect it. It uses no advertising or analytics services, and today it sends no data to any AI service.

Have Questions About Security?

We welcome security questions from operators. Write to security@empirevault.com.