Custom headers

In Enterprise Threat Protector (ETP), you can configure custom headers to control access to your enterprise SaaS applications. For example, you can use custom headers to restrict user access to only your organization's application account.

You configure custom headers in a policy configuration. As part of this configuration, you provide the domain of the application or the website that users access. You then enter the header name and value. The header name is inserted into the request and used to control access. The header name is usually defined by the provider of the application, while the header value is specific for your enterprise. For example, the header value may be an ID associated with your organization’s application account.
Note: To use this feature, your organization must be licensed for ETP Advanced Threat and configure ETP Proxy as a full web proxy
After custom headers are used to grant user access to an application, you can use other ETP features to scan content that is downloaded or uploaded. These features include:
  • Data loss prevention (DLP). You can use DLP to scan uploaded files. For more information about DLP, see Data loss prevention.
  • Inline payload analysis. You can use inline payload analysis to scan downloaded content with ETP Proxy. For more information about inline payload analysis, see Inline payload analysis.

You can add a maximum of 1,000 headers.