The “Journaling” architecture in Trustifi allows users to scan their outgoing emails for sensitive content with minimal intervention to their mail flow and architecture.
This architecture works by creating a journaling rule in your Exchange environment, which sends journaled copies of outgoing emails to Trustifi’s endpoint.
The original emails are left untouched and arrive to their intended recipient without delay, while Trustifi receives the journaled copy on which all scans and tests are performed to check for content that is deemed sensitive, or relevant to different compliances.
Trustifi users can utilize the scanning aspect by themselves to get an understanding of how Trustifi’s outbound scanning works without interrupting mail flow or to gauge Trustifi’s outbound scanning abilities in a Proof of Concept setting.
Limitations and Constraints
When using the “Journaling” architecture, there are some differences in mail flow behavior and handling when compared to the Email Relay architecture.
Some of these differences are expected due to the nature of journaling, and some are currently due to technical constraints.
With the journal architecture, functions related to modification of the email body are not available. These functions include applying encryption, footers/headers, link and email tracking, and more.
Emails sent to recipients in bcc are not scanned by the journal flow.
Policies intended to block or quarantine specific emails will not apply, as Trustifi only handles journaled copies of emails and not the original.