The "Journaling" architecture in Trustifi allows users to scan their outgoing emails for sensitive content with minimal changes to their mail flow and email architecture.
This architecture works by creating a journaling rule in your Google 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 compliance requirements.
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 evaluate 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.
Email Modification Functions Are Not Available: With the journal architecture, functions related to the modification of the email body are not available. These functions include applying encryption, footers or headers, link tracking, email tracking, and other modification features.
Blind Carbon Copy Recipients Are Not Scanned: Emails sent to recipients in blind carbon copy (BCC) are not scanned by the journal flow.
Blocking and Quarantine Policies Do Not Apply: Policies intended to block or quarantine specific emails will not apply, as Trustifi only handles journaled copies of emails and not the original messages.