How can I show destination in CAP custom notification template?

What version are you using? (OS, client, server, etc.)

  • We are currently using Windows and macOS.

What error messages or unexpected behavior are you seeing?

We are trying to modify the notification template in Content Aware Protection. However, in the custom notification parameters, the destination parameter used in our Content Aware Protection policies is not available.Because of this, when we use a custom notification, it is difficult for users to identify where the blocking occurred (destination).Is there any way to include the destination parameter in the custom notification, even though it is not listed in the manual or among the predefined variables?

Dear Ji-won Kim,

Although there is no dedicated variable for the destination, the template below still includes the destination information:

{threatMatch} was detected in {fileName} and the upload was {type}.

As a result, the message shown to the user would look like this:

Hello,

Thank you for the clarification.

If we want to create a fully custom notification message and include the destination information, it seems that there is currently no dedicated variable available for the destination.

In that case, would it be correct that we need to submit a feature request to support a destination variable in custom notifications?

Thank you.

Hi Ji-won Kim,

The {fileName} parameter also displays the destination information by default. As a quick test, I only defined {fileName} under System Parameters → Device Types and Notifications → Custom Content Aware Protection Notifications, and the notification I received included the destination.

dlptest.com is the destination in this case.

If you need the actual application used for the file transfer attempt, that information is currently not available. Supporting this would require a feature request in the Ideas section of the Netwrix Community. You are welcome to submit it.

Best regards,

Zoran

Hello,

Thank you for your confirmation.
At the moment, we need the information about the actual application used for the file transfer attempt, so we plan to submit a feature request in the Ideas section.

Thank you for your assistance.