> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://mezmo.ferndocs.com/encrypt-fields-processor/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mezmo.ferndocs.com/_mcp/server.

# Encrypt Field Processor

## [Description](https://docs.mezmo.com/docs/encrypt-field-pipeline-processor#description)

You can use the Encrypt processor to apply an encryption algorithm and key to a specified field.

## [Use](https://docs.mezmo.com/docs/encrypt-field-pipeline-processor#use)

The Encrypt processor is useful when you need to send sensitive log data to storage, for example when you want to retain log data that may contain account names and passwords.

## [Configuration](https://docs.mezmo.com/docs/encrypt-field-pipeline-processor#configuration)

There are four options you need to set for this processor.

| **Option**                           | **Description**                                                                                                                              | **Example**                                        |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| **Field**                            | The field you want to apply encryption to.                                                                                                   | `.foo`                                             |
| **Encryption algorithm**             | The encryption algorithm to apply. These options also determine how many characters to use for the encryption key and initialization vector. | `AES-256-CFB (key=32 characters, iv=16characters)` |
| **Encryption key**                   | The key used by the algorithm to encrypt the field.                                                                                          | `6B58703273357638792F423F4528482B`                 |
| **Initialization vector (IV) field** | This field is added by the pipeline to the JSON and is used by the algorithm as the initialization key.                                      | .`encrypt_iv`                                      |

## Interactive Demo

Check out an interactive demo of the Encrypt Processor as a component in [a Compliance group](https://docs.mezmo.com/2.8/practioner-guide-data-optimization/pipeline-module--security-and-compliance), as well as instructions for building a version of the Pipette with your own sample data.

## Example

### Before

```json
{
  "foo": "bar"
}
```

| **Option**                       | **Value**                                        |
| -------------------------------- | ------------------------------------------------ |
| Field                            | .foo                                             |
| Encryption algorithm             | AES-256-CFB (key=32 characters, iv=16characters) |
| Encryption key                   | 6B58703273357638792F423F4528482B                 |
| Initialization vector (IV) field | .encrypt\_iv                                     |

### After

```json
{
  "encrypt_iv": "FmXUb0OPOWm1A2kw6diKYw==",
  "foo": "vFza"
}
```