Configuring Field Encryption
Learn how to activate and configure Field Encryption and manage migration from Encryption Support.
-
Learn how to active either Field Encryption or Field Encryption Enterprise.
Roles Required for Configuring Field Encryption
Learn about the roles required to configure Field Encryption.
Migration from encryption support
Use Scheduled jobs to migrate your keys and encrypted data from legacy Encryption Support to Field Encryption Enterprise. See details for this process at Migrating to Field Encryption
Change attachment encryption settings
Improve security by preventing users from attaching unencrypted files. For details, see Prevent users from attaching unencrypted files.
- Activate Field Encryption
Activate either Field Encryption Starter or Field Encryption Enterprise. - Role requirements for Field Encryption
Learn about the roles required to configure Field Encryption. - Configure Field Encryption modules
Learn how to configure Field Encryption modules. - Cryptographic specifications for Field Encryption
Use cryptographic specifications to define the purpose, algorithm, key length, mode, and origin of your encryption key. - Module keys for Field Encryption
The Module Keys tab shows you summary level information about your Field Encryption Data Encryption Key(s). You can view the Key alias, Key type, Algorithm, Key lifecycle state, and Key version. - Module lifecycle policy exceptions for Field Encryption
Use module lifecycle policy exceptions to customize the lifecycle of your module keys. - Configure Customer-supplied keys for Field Encryption Enterprise
Bring your own data encryption key to the platform instead of using the one that ServiceNow generates. - Configure encrypted field configurations for fields or attachments
Create an encrypted field configuration to specify which fields are encrypted on a table, and whether that table's attachments are encrypted. - Configure multi-module encrypted field configurations
Create an encrypted field configuration that uses more than one encryption module. - Configure module access policies for Field Encryption
Create a module access policy to control which users, scripts, or system processes can encrypt or decrypt data encrypted by a field encryption module. - Migrating to Field Encryption
Scheduled jobs migrate your keys and encrypted data from Encryption Support to Field Encryption. - Migrate from Edge Encryption to Field Encryption
Migrate from Edge Encryption to Field Encryption to take advantage of the latest security features. - Field Encryption and system clones
Cloning an instance with Field Encryption installed automatically generates new field encryption module encryption keys on the target clone instance. - Prevent users from attaching unencrypted files
Modify the com.glide.encryption.enable_attachment_key_ui property to prevent your users with access to an encryption module key from attaching unencrypted attachments.
Parent Topic:Field Encryption