Trellix DLP Endpoint sends two types of messages to communicate with end users: notifications and user justification messages.
Notifications support Rich Text (HTML) messages. Notification and justification definitions can specify Locales (languages), and add placeholders that are replaced by their real values. When locales are defined, the messages and option buttons (for business justifications) appear in the default language of the endpoint computer. The following locales are supported:
English (US)
English (UK)
French
German
Spanish
Polish
Portuguese
Russian
Japanese
Korean
Chinese (simplified)
Chinese (traditional)
English (US) is the standard default locale, but any supported locale can be set as the default in the definition. The default locale is used when other defined locales are not available as the endpoint computer default language. Trellix DLP Network Prevent attempts to detect the user's preferred language from request headers.
Note
Trellix DLP Network Prevent does not fully support Korean, Russian, or Chinese (Simplified) locales.
User notification
Trellix DLP Endpoint user notifications are pop-up messages that notify the user of a policy violation.
Note
When a rule triggers multiple events, the pop-up message states: There are new DLP events in your DLP console, rather than displaying multiple messages.
You can include Rich Text in the pop-up by including HTML tags embedded in a <DIV>.
When Trellix DLP Network Prevent blocks a web request, it sends the user notification as an HTML document that appears in the user's browser. The notification text that you configure can contain embedded HTML tags, such as <p>, <ul>, or <li>. The alert that the user sees also shows Access Denied.
Business justification
(For Trellix DLP Endpoint only) Business justification is a form of policy bypass. When Request Justification is specified as the action in a rule, the user can enter the justification to continue without being blocked.
Placeholders
Placeholders are a way of entering variable text in messages, based on what triggered the end-user message. The available placeholders are:
%cfor classifications found in the data%rfor rule-set name%vfor data loss threat vector (for example, Email Protection, Web Protection, DLP Network Prevent)%afor action (for example, Block)%sfor context value (for example, file name, device name, email subject, URL)%ffor context value in Trellix DLP Network Prevent for Email (for example, file name, email subject, email body), for context value in Trellix DLP Network Prevent for Web and Trellix DLP Endpoint (for example, full path, URL)%tfor matched attachments (for example, Email Protection)%efor matched email addresses (for example, Email Protection)%mfor the domain threshold value of the To field%nfor the domain threshold value of the Cc field%ofor the domain threshold value of the Bcc field%pfor the domain threshold value of Cumulative field%qfor the domain threshold value of Cumulative (Ignored Bcc) field%hfor the email recipient threshold value of the To field%ifor the email recipient threshold value of the Cc field%jfor the email recipient threshold value of the Bcc field%kfor the email recipient threshold value of Cumulative field%lfor the email recipient threshold value of Cumulative (Ignored Bcc) field
Note
m, n, o, p, q, h, i, j, k, and l are placeholders for the recipient threshold values. Placeholders e and t are not applicable for email threshold rule.