---
title: AES-256-GCM encryption for email attachments
slug: docsatwork/guide/ios/aes-256-gcm-encryption-for-email-attachments
createdAt: 2026-09-07T12:22:25.971Z
---

You can configure Ivanti Docs\@Work to use 256-bit encryption. If you already have Ivanti Docs\@Work (original) enabled and are now enabling Ivanti Docs\@Work, the system continues to use 128-bit encryption for email attachments. To use 256-bit encryption with Ivanti Docs\@Work, you must first disable Ivanti Docs\@Work (Original) and then regenerate the attachment encryption key. A 256-bit key is only generated if Ivanti Docs\@Work (Original) is disabled and all Standalone Sentrys are at least at version 6.1.0.

| Ivanti Docs\@Work (Original) | Ivanti Docs\@Work | Sentry Version                                         | Encryption key generated |
| ---------------------------- | ----------------- | ------------------------------------------------------ | ------------------------ |
| Enabled                      | Enabled           | -                                                      | AES-128-ECB              |
| Disabled                     | Enabled           | Some Standalone Sentrys are at least at version 6.1.0. | AES-128-ECB              |
| Disabled                     | Enabled           | All Sentrys are at least at version 6.1.0.             | AES-256-GCM              |

- Key regeneration causes a restart for all Standalone Sentrys that use encryption for attachment control. A restart can cause a brief interruption in email service to device users.
- After regenerating the encryption key, iOS device users who use the iOS native email client cannot read previously received attachments. If device users need to read previously received attachments, re-push the Exchange setting to the devices. Ivanti advises caution when re-pushing the Exchange setting. Re-pushing the Exchange setting increases the load on the Exchange server.

:::hint{type="success"}
After you upgrade Standalone Sentry, in the Ivanti EPMM Admin Portal, go to <font color="#323232">Services &gt; Overview</font>, and click <font color="#323232">Verify</font> for the Standalone Sentry. This action immediately updates the Standalone Sentry version in Ivanti EPMM. Otherwise, the Standalone Sentry version in Ivanti EPMM is updated at the next sync. All Standalone Sentry versions in Ivanti EPMM must be at least at Sentry 6.1.0 release to generate a 256-bit key.
:::

## Configuring 256-bit encryption

You will need to enable 256-bit encryption, if you previously had Ivanti Docs\@Work (Original) enabled.

**Procedure**

1. Ensure that all Sentrys configured on Ivanti EPMM are at least at Sentry 6.1.0.
2. In the Admin Portal, go to <font color="#323232">Settings &gt; System Settings</font>.
3. <font color="#000000">Scroll down to the </font><font color="#323232">Additional Products</font><font color="#000000"> section.</font>
4. Click on <font color="#323232">Licensed Products</font>.
5. De-select <font color="#323232">Enable Docs\@Work (Original)</font>.
6. Ensure that <font color="#323232">Enable Docs\@Work</font> is enabled.
7. Click on <font color="#323232">Save</font>.
8. Go to <font color="#323232">Settings &gt; Sentry</font>, and click <font color="#323232">Preferences</font>.
9. In the <font color="#323232">Standalone Sentry</font> section, click <font color="#323232">Regenerate Key</font>.

Related topics 

For information about regenerating the encryption key, see “Regenerating the encryption key” in the Ivanti Standalone Sentry Guide for EPMM

## Configuring certificate pinning

To use Certificate Pinning, in Docs\@Work configuration enable Client TLS option and select the configured Client TLS configuration listed to provide more security between Ivanti Docs\@Work and enterprise server communication. For more information to configure Client TLS see, *Creating a Client TLS configuration* section in the Ivanti AppConnect Guide for EPMM and Ivanti Tunnel for iOS Guide.
