---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/platform-security

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Using multiple encryption modules

# Using multiple encryption modules {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Multiple encryption modules enable data to be encrypted with more than one encryption module. If each module has its own access policy based on a role, for example, users with different roles can encrypt data on the same table
but used to help prevent them from viewing each other's encrypted data.

There are two ways to encrypt data using multiple encryption modules in the platform: Row Conditions and multiple module.

## Row Conditions {#using-multiple-encryption-modules__section_nmq_vtd_rgc}

Enables admins to define the encryption crypto module to be used. This option provides a deterministic approach and permits multiple Encryption Field Configurations (EFCs) to a single column. You can encrypt different records for a
field or attachment by configuring distinct encryption keys to specific fields. This is achieved by assigning multiple Encryption Field Configurations (EFCs). Row Conditions is the preferred method of encrypting data with multiple
modules. See [Encrypt data using Row Conditions](https://www.servicenow.com/docs/vUnqM15Q~FaRbsjC7ZlUyA "Encrypt fields with multiple Field Encryption modules using Row Conditions to define the data being encrypted and the associated encryption keys. Row Conditions can also be used to define the users that have access using the condition builder.").

## Multiple module {#using-multiple-encryption-modules__section_mn3_xtd_rgc}

Enables users to the crypto module to use to encrypt data. Since multiple module depends on the user selecting the correct crypto module to encrypt the data, this configuration is nondeterministic and is considered legacy and not
preferred, even though the feature is still currently available. See [Encrypt data using the Multiple Modules feature](https://www.servicenow.com/docs/eGnQc5qPwK34QT64BNO8~Q "Encrypt data with more than one encryption module permitting the user to determine which keys are used for specific rows within the encrypted data.").
* **[Encrypt data using Row Conditions](https://www.servicenow.com/docs/vUnqM15Q~FaRbsjC7ZlUyA)**   
  Encrypt fields with multiple Field Encryption modules using Row Conditions to define the data being encrypted and the associated encryption keys. Row Conditions can also be used to define the users that have access using the condition builder.
* **[Encrypt data using the Multiple Modules feature](https://www.servicenow.com/docs/eGnQc5qPwK34QT64BNO8~Q)**   
  Encrypt data with more than one encryption module permitting the user to determine which keys are used for specific rows within the encrypted data.