Threat Protection Policies part of Security Shared Flow or Proxy ?

Hi

JSON ThreatProtection and XML Threat protection should they be part of a common security shared flow or applied at the proxy level.

The concern is continuous development these values will keep changing based on new API request payloads being added.

If they are part of common shared flow then we need to track these values for different payloads on the platform, and keep these values to maximum range so as not to run in to trouble for any of them.

If they are proxy basis then these values can be contextualized for the proxy but it just distributes policies and makes tracking difficult.

How they have been implemented if someone can share some thoughts.

thanks,

Aakash

0 1 91
1 REPLY 1

Not applicable

I would suggest the way we have implemented in our organisation.

Create a shared flow of the threat protection policies and configure those in the flowhook, so that for all proxies the same will be implemented.