---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure Field Encryption for your Edge Encrypted fields

# Configure Field Encryption for your Edge Encrypted fields {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Before migrating your existing edge encrypted fields to Field Encryption, you must configure field encryption for these fields.

## Vorbereitungen

Role required: admin

This process assumes you have existing edge encrypted fields that you want to migrate to Field Encryption.

## Prozedur

1. Navigate to AllKey ManagementCryptographic ModulesAll.
2. In the Cryptographic Modules list, select New.
3. In the form, fill in these fields.  
   {#migrate-ee-to-fe-1__table_vgv_b1s_mdc__entry__2}

   | Field | Value |
   |-|-|
   | Name | Select descriptive name |
   | Crypto spec template | Default template |
   | Crypto module lifecycle state | Published |
   | Parent crypto module | column_level_encryption |
   [ ]

   {#migrate-ee-to-fe-1__table_vgv_b1s_mdc}
4. Right-click the form header and select Save.
5. In the Crypto Specifications related list, open the record on the list.
6. In the Crypto Specification record, select Next three times to complete the algorithm definition, lifecycle definition, and key origin sections.  
   You don't need to modify any fields in these sections.
7. In the Generate Key field, select the Generate Key link to generate a key.
8. Navigate to AllSystem SecurityField EncryptionEncrypted Field Configuration.
9. In the encrypted field configuration list, select New.
10. In the form, fill in these fields.  
    {#migrate-ee-to-fe-1__table_sf3_zhg_pdc__entry__2}

    | Field | Value |
    |-|-|
    | Type | Select Column or Attachment, depending on what you want to encrypt. |
    | Crypto module | Select the cryptographic module that you created in earlier steps. |
    | Table | Select the table containing the data that you want encrypted. |
    | Method | Select <kbd class="ph userinput">Single Module</kbd> |
    | Column | Select the column (field) on the table that you want to be encrypted. |
    [ ]

    {#migrate-ee-to-fe-1__table_sf3_zhg_pdc}  
    Hinweis:  
    The data to encrypt is determined by the Table and Column fields. These fields should be the table and column (field) where you're currently using Edge Encryption.
11. Select Submit.
12. Navigate to AllKey ManagementModule Access PoliciesAll.
13. Select New.
14. In the form, fill in these fields.  
    {#migrate-ee-to-fe-1__table_hf4_vfm_pdc__entry__2}

    | Field | Value |
    |-|-|
    | Policy name | Select descriptive name |
    | Crypto module | Select the cryptographic module that you created in earlier steps. |
    | Type | Select <kbd class="ph userinput">Role</kbd> |
    | Target role | Select a role to be used. This role must be able to encrypt and decrypt data in the column. |
    | Result | Select the desired action. |
    [ ]

    {#migrate-ee-to-fe-1__table_hf4_vfm_pdc}
15. Select Submit.
16. To verify your configuration, navigate to the table you want encrypted with Field Encryption, and open a record.  
    For example, to access the User \[sys_user\] table, enter <kbd class="ph userinput">sys_user.list</kbd> into the navigation filter.

    The field you have selected for encryption in the previous steps now has a lock icon next to the field label.

## Ergebnisse

You edge encrypted field is ready to be migrated to field encryption. To configure more fields, repeat the preceding steps for each of those fields.