Encryption

The process of converting data into an unreadable format using cryptographic algorithms, protecting it from unauthorized access.

On this page

What is Encryption?

Encryption protects data confidentiality using symmetric (AES-256) or asymmetric (RSA, ECC) algorithms. Key considerations include encryption at rest (stored data), in transit (TLS 1.2/1.3), and in use (homomorphic encryption, secure enclaves). Key management is critical, including generation, storage, rotation, and destruction of encryption keys. Standards include FIPS 140-2/3 for cryptographic modules and NIST SP 800-57 for key management.

Application to Vendor Screening

Verify that vendors encrypt your data both at rest and in transit using industry-standard algorithms. Assess their key management practices: Who has access to encryption keys? Are keys rotated regularly? Does the vendor use customer-managed keys (CMEK) or bring-your-own-key (BYOK) options?

Practical Examples

  • Verifying that a vendor uses AES-256 encryption for data at rest
  • Confirming TLS 1.2 or higher for data in transit to vendor systems
  • Evaluating a vendor's encryption key management and rotation practices

Frequently Asked Questions

What encryption standards should vendors meet?

Vendors should use AES-256 for data at rest and TLS 1.2 or 1.3 for data in transit. Cryptographic modules should be FIPS 140-2 or 140-3 validated for regulated industries.

What is the difference between encryption at rest and in transit?

Encryption at rest protects stored data on disk, databases, or backups. Encryption in transit protects data moving between systems over networks. Both are essential; data should never be unencrypted in either state.

Check the vendor. Keep the evidence.

Start free