Exploring Database Encryption

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Exploring Database Encryption

    ServiceNow provides database encryption (DBE) and full-disk encryption options to help customers meet data protection requirements for data at rest. DBE uses AES-256 symmetric encryption to secure all stored data both online and offline without impacting functionality or user experience. Full-disk encryption protects data if physical disks are lost or stolen.

    Show full answer Show less

    Starting with the Washington DC release, Database Encryption is being phased out and replaced by Cloud Encryption with Key Management for data at rest encryption.

    Key Features

    • Encrypts all stored data in real time using AES-256 encryption, including new and modified data and associated activity logs.
    • Data is decrypted only in memory during access, ensuring security without interfering with platform operations.
    • Encryption is transparent to users and supports encryption of instances, replication traffic, and backups.
    • Minor performance impact of up to 5% during instance cloning when using database encryption.
    • Supports both new and existing instances on supported ServiceNow AI Platform releases.
    • Utilizes a three-level key hierarchy for enhanced security:
      • Customer-specific AES-256 key encrypts data.
      • Second customer-specific AES-256 key protects the first-level key.
      • Third AES-256 key, stored in FIPS 140 validated key management appliances at ServiceNow datacenters, protects the second-level key uniquely per customer instance.
    • Supports Database Encryption with Customer-Controlled Switch (DBE with CCS) for encrypting all data-at-rest using customer-supplied keys, maintaining industry-standard AES encryption without functionality loss.
    • Encryption and decryption processes occur as data is written to and read from disk, ensuring applications always work with unencrypted data in memory.

    Important Considerations

    • Database Encryption is not available for on-premise instances.
    • Customers using their own keys should refer to DBE with Customer-Controlled Switch documentation.
    • Cloud Encryption with Key Management is the recommended replacement for Database Encryption from the Washington DC release onward.

    ServiceNow® offers database encryption (DBE) and full-disk encryption methods for customers with statutory obligations for data protection which may require at-rest protection for all data.

    Important:
    Starting with the Washington DC release, Database Encryption is being prepared for future deprecation. Cloud Encryption is the replacement solution for data at rest encryption. For details, see Cloud Encryption with Key Management

    Database Encryption enables all data to be protected with symmetric AES-256 encryption, whether the database is online or offline. From the ServiceNow AI Platform perspective, all data flows in decrypted.

    • Database Encryption supports all stored data to be encrypted in real time providing protection for data online and offline with no loss of functionality.
    • Full disk encryption protects offline data if there is disk loss or theft.

    Database Encryption

    With Database Encryption, all stored data is encrypted and individual records or tables are decrypted in memory while being accessed. New or changed data is encrypted as it is entered into a table and associated activity log files (bin, redo, undo, and error) are also encrypted.

    Database Encryption is transparent to users, with no loss of functionality. When using this feature, all instances are encrypted, along with replication traffic and backups. Instance cloning is still available with a minor performance impact for using Database Encryption of up to 5%. Both new and existing instances on supported releases of the ServiceNow AI Platform can take advantage of database encryption.

    As illustrated, ServiceNow stores and manages keys using a three-level key hierarchy:

    Key management

    1. A customer specific AES-256 key is created by the database engine and is used to encrypt the data.
    2. A second customer specific AES-256 key is created by the database engine and is used to protect the first-level key.
    3. A third AES-256 key is created by and stored within FIPS 140 validated key management appliances in the ServiceNow datacenters. This key protects the second-level key and is unique per customer instance.

    The ServiceNow AI Platform also supports database encryption with a customer supplied switch, DBE with CCS. This is an encryption solution that encrypts all data-at-rest when not in use in the database. It uses industry standard AES encryption with no impact to functionality. The database encrypts data as it is written to the disk, and decrypts data as it is read from the disk. That means that applications always have the data in an unencrypted state to perform the necessary logic and functions without impact.

    Note:
    Database Encryption is not supported for on-premise instances.

    If you are using your own keys for database encryption, see Database Encryption with Customer-Controlled Switch.