Glossary/Security, Access & Deployment

Encryption (At Rest / In Transit)

Encryption is a cryptographic process that converts readable data into ciphertext to protect confidentiality, with data at rest referring to stored information and data in transit referring to information moving across networks.

Encryption at rest protects stored data in databases, file systems, or backup repositories by rendering it unreadable without the correct decryption key. Common implementations include transparent data encryption (TDE) that encrypts entire databases automatically, file-level encryption at the operating system, and field-level encryption where specific columns are encrypted. Encryption in transit protects data moving across networks using protocols like TLS/SSL for HTTP communication, encrypted VPN tunnels for network traffic, and encrypted protocols for database connections. Together, these mechanisms ensure data remains protected throughout its lifecycle.

The effectiveness of encryption depends on key management: storing keys separately from encrypted data, rotating keys regularly, and controlling access to keys through strong authentication. Modern analytics platforms typically implement encryption both at rest and in transit by default, though organizations must still manage encryption keys, key rotation policies, and ensuring keys are not lost or compromised. Encryption adds computational overhead, particularly when large datasets are frequently decrypted for analysis, making key performance considerations important in high-volume analytics environments.

Key Characteristics

  • At rest encryption: protects stored data in databases, files, or backups
  • In transit encryption: protects data moving across networks using protocols like TLS
  • Requires separate key management distinct from encrypted data storage
  • Adds computational overhead for encryption/decryption operations
  • Keys must be rotated regularly and stored securely
  • Encryption transparency varies: some implementations are automatic while others require application changes

Why It Matters

  • Prevents data exposure if storage media or network traffic are compromised
  • Meets regulatory requirements for data protection in GDPR, HIPAA, PCI-DSS, and similar standards
  • Ensures data confidentiality even if systems are physically stolen
  • Reduces liability in breach scenarios by rendering compromised data unusable
  • Protects intellectual property and trade secrets from interception or theft
  • Enables secure transmission of sensitive data to external partners and cloud platforms

Example

A pharmaceutical company encrypts research data in transit using TLS when transmitting between clinical sites and their central analytics platform. Databases containing genetic information are encrypted at rest using transparent database encryption. Keys are stored in a separate hardware security module (HSM) with access restricted to database administrators. Daily key rotation automatically generates new keys while maintaining ability to decrypt historical data.

Coginiti Perspective

Coginiti enforces encryption in transit through TLS/SSL for all platform communications and ODBC connections, and encryption at rest on connected platforms like Snowflake, BigQuery, Redshift, and cloud storage. Organizations can configure key management policies on each connected platform; Coginiti's semantic layer operates transparently over encrypted data, enabling consistent analytics without requiring application-level encryption logic.

See Semantic Intelligence in Action

Coginiti operationalizes business meaning across your entire data estate.