DLP/AV configuration parameters

Sets active Spring profiles. For DLP/AV Connector, the value of this parameter can be dlp or avs (lower-case letters). Enter the two values, separated by a comma, if you want to activate both DLP and AV.

NOTE: For DLP Connector 1.2.x, only DLP can be activated if the value as set as DLP (capital letters).

syncplicity.crypto.keyStore.enforced

syncplicity.crypto.keyStore.file

syncplicity.crypto.keyStore.password

syncplicity.crypto.keyStore.type

The URL of the ActionMQ instance.

For companies in the US PrivacyRegion, enter https://amq.syncplicity.com/api/v1/

For companies in the EU PrivacyRegion, enter https://amq.eu.syncplicity.com/api/v1/

The name of the queue for getting messages. The queue is created once the DLP feature is enabled for the StorageVault.

The queue name is constructed using the following pattern: "1.file.<storagevault_id>". The <storagevault_id> portion of this string is what you collected in Step 4, and should be entered without the dashes in the string.

Time (in seconds) before the token expires and a new token is generated. For example, if the token is valid until 10:15:27 with skew parameter = 10, it is replaced with a new token at 10:15:17. This is needed to eliminate request rejections because of token expiration.

This parameter specifies the number of worker threads in the pool that are processing incoming messages in parallel. The minimum value is 1 worker.

Disabled by default.

Enables and specifies the proxy to the DLP Engine for the preceding alias. This is necessary when there is no direct connection between the DLP Connector and the ICAP server for the DLP Engine, and network traffic is going through a proxy.

Example value: http://10.250.240.235:3128

For DLP/AV Connector 2.x, this setting is broken down into multiple ones (see directly below).

Enables the proxy to the DLP Engine for the preceding alias. This is necessary when there is no direct connection between the DLP Connector and the ICAP server for the DLP/AV Engine, and network traffic is going through a proxy.

Text
(URL)

The header name in the response from the DLP server, where the ICAP client can get the reason of blocking. The value from selected header is saved as description of ScanResult.

Header names differ for different DLP engines. For example:

• DigitalGuardian: "X-Virus-ID" or "X-Infection-Found" or "X-Violations-Found"
• McAfee: "X-Infection-Found" or "X-Violations-Found"
• Symantec: "X-Infection-Found" or "X-Violations-Found"

The list above is not definitive, as these headers are also configurable for some of the DLP servers. Please check with your DLP server administrator which header to use.

Detailed description of each header can be found in ICAP specification: https://tools.ietf.org/html/draft-stecher-icap-subid-00

The URL of the ActionMQ instance.

For companies in the US PrivacyRegion, enter https://amq.syncplicity.com/api/v1/

For companies in the EU PrivacyRegion, enter https://amq.eu.syncplicity.com/api/v1/

The name of the queue for getting messages. The queue is created once the AVS feature is enabled for the StorageVault.

The queue name is constructed using the following pattern: "6.file.<storagevault_id>". The <storagevault_id> portion of this string is what you collected in Step 4, and should be entered without the dashes in the string.

Time (in seconds) before the token expires and a new token is generated. For example, if the token is valid until 10:15:27 with skew parameter = 10, it is replaced with a new token at 10:15:17. This is needed to eliminate request rejections because of token expiration.

This parameter specifies the number of worker threads in the pool that are processing incoming messages in parallel. The minimum value is 1 worker.

Enables the proxy to the DLP/AV Engine for the preceding alias. This is necessary when there is no direct connection between the DLP Connector and the ICAP server for the DLP/AV Engine, and network traffic is going through a proxy.

Text
(URL)

The header name in the response from the DLP/AV server, where the ICAP client can get the reason of blocking. The value from selected header is saved as description of ScanResult.

Header names differ for different DLP engines. For example:

• DigitalGuardian: "X-Virus-ID" or "X-Infection-Found" or "X-Violations-Found"
• McAfee: "X-Infection-Found" or "X-Violations-Found"
• Symantec: "X-Infection-Found" or "X-Violations-Found"

The list above is not definitive, as these headers are also configurable for some of the DLP servers. Please check with your DLP server administrator which header to use.

Detailed description of each header can be found in ICAP specification: https://tools.ietf.org/html/draft-stecher-icap-subid-00

• 26214400 for DLP 1.2.x
• 0 for DLP/AV 2.x

Indicates the size of the underlying buffers used by the platform for incoming network I/O. 

DLP 1.2.x - 30000

DLP/AV 2.x - 180000