Security & Compliance

Encryption (At-Rest & In-Transit)

Updated Nov 10, 2026 · 4 min read
Quick answer

Encryption is the process of converting readable data into coded form that can only be read with the correct key. In a virtual data room, encryption in transit protects files as they travel between the user and the server, and encryption at rest protects them while they sit in storage.

Why encryption matters in a data room

A data room holds the most sensitive records a company owns: financial statements, customer lists, employee data, and intellectual property. Encryption means that someone who intercepts a transfer or gains access to the underlying storage sees unreadable data, not documents. It is a baseline control that buyers, lawyers, and regulators expect to find.

The two states of encrypted data

Encryption in transit

Data moving between a browser or app and the data room’s servers is protected with Transport Layer Security (TLS). Current practice is TLS 1.2 or 1.3. Older protocols such as SSL and TLS 1.0 are deprecated and should not be accepted.

Encryption at rest

Files, database records, and backups stored by the provider are encrypted on disk. The common standard is AES-256, a symmetric cipher with a 256-bit key. Encrypting backups matters as much as encrypting primary storage.

Key management

Encryption is only as strong as the handling of its keys. Three questions separate a thorough setup from a basic one:

  • Who holds the keys? Provider-managed keys are standard. Some platforms offer customer-managed keys, which let the client control or revoke them.
  • Where are the keys stored? Keys should sit apart from the data, ideally in a dedicated key management service or hardware security module.
  • How often are they rotated? Regular rotation limits the damage if a key is exposed.

Some products advertise end-to-end or zero-knowledge encryption, where even the provider cannot read the files. The trade-off is that server-side features such as full-text search and OCR cannot work on content the server cannot read.

What to check when evaluating a provider

  • Encryption in transit and at rest for all content, including backups and previews
  • The cipher and protocol versions in use, stated in the security documentation
  • Key management practices and whether customer-managed keys are available
  • Independent verification, such as ISO 27001 certification or a SOC 2 Type II report that covers encryption controls

Real-world example

A biotech company prepares a data room for a licensing deal with an EU partner. The partner’s security team asks for written confirmation of encryption standards. The provider’s documentation states TLS 1.3 for connections, AES-256 for stored files and backups, and keys held in a separate key management service with annual rotation. The partner’s team also requests a copy of the provider’s latest SOC 2 Type II report to confirm that the controls were tested over time.

Common mistakes

  • Treating encryption as access control. Encryption protects against interception and storage theft. It does not decide which users may open which files. That is the job of granular permissions.
  • Sending the link in plain email. A strongly encrypted data room still depends on how credentials and invitations are shared.
  • Accepting marketing language. Phrases such as “bank-grade encryption” mean nothing without a named cipher and protocol.
  • Ignoring exports. Files downloaded from the data room leave its encryption. Restrict downloads for sensitive material.

Browse more terms

Audit Trail

Security & Compliance

Clean Room

Security & Compliance

Digital Rights Management (DRM)

Security & Compliance

Dynamic Watermarking

Security & Compliance
See all terms →

Ready to run your own diligence?

Compare leading VDR providers in one place.

See top VDR providers
To make sure you have the best possible experience on our site, we use cookies. By continuing to use this website, you consent to the use of cookies.
Learn more
To top