Encrypt fields using encryption configurations
-
- UpdatedJan 30, 2025
- 6 minutes to read
- Yokohama
- Edge Encryption
Encrypt fields by creating encryption configurations.
To configure Edge Encryption, you must be connected to the instance through the proxy. Test all changes on a non-production instance before applying them to the production instance.
Define encryption keys
After setting up one or more proxies and configuring a default encryption key, the instance verifies that the keys are available to all proxies. You can’t make an encryption key the default key unless all proxies have the key. After a default key is defined, you can create encryption configurations.
Assign fields and attachments to be encrypted
- Determine what system features might be impacted.
- Examine all scripts for use of the field.
- Make any desired adjustments to the field size. After a field has been configured for encryption, the field size can’t be changed.
Marking a field to be encrypted expands the field size to store the encrypted data. The process of expanding the field size can take a long time, depending on the number of records in the table.
API support
Field Encryption updates the setDisplayValue()
and setValue()
APIs so they can insert encrypted data for encrypted fields. It also enables getDisplayValue()
and getValue()
to return cleartext values.
The following script illustrates these API changes when the Incident short description is encrypted:
When using getValue()
to get encrypted text, your script no longer returns the ciphertext. Your script returns the plaintext, assuming that the user has access to the cryptographic module.
getValue()
returns the ciphertext if the user doesn’t have access to the cryptographic module.
Create a field encryption configuration
Select the fields to be encrypted and identify the encryption type.
Before you begin
Role required: security_admin
Procedure
What to do next
After you add the encryption configuration record, you can create an encryption job to encrypt existing data. If you do not run an encryption job, Edge encrypts the existing data the next time the data changes. For details, see Schedule an encryption job.
Create a variable encryption configuration
Select service catalog variables to be encrypted and identify the encryption type.
Before you begin
Role required: security_admin
Procedure
What to do next
After you add the encryption configuration record, you can create an encryption job to encrypt existing data. If you do not run an encryption job, Edge encrypts the existing data the next time the data changes. For details, see Schedule an encryption job.
Deactivate an encryption configuration
After configuring a field or a table's attachments to be encrypted, you can stop encryption by deactivating the encryption configuration. After deactivating encryption, you can run a Decryption job for fields or an Attachment Decryption job for attachments to remove the encrypted data from the instance.
Before you begin
Role required: security_admin
About this task
Procedure
What to do next
You can run a Decryption or Attachment Decryption job to decrypt data on the instance. If you do not run a job, the encrypted data is decrypted the next time it is changed.
Schedule an encryption job
You can schedule a job to find and encrypt any unencrypted data in a specified field, using the default encryption key configured for the field. If you do not create an encryption job after configuring a field for encryption, only new values are encrypted.
Before you begin
Role required: security_admin
Procedure
Schedule a decryption job
You can schedule a job to decrypt data in an encrypted field, to store clear data in the instance.
Before you begin
Role required: security_admin
Procedure