Enrichment
Data Enrichment
The HUMAN NGINX plugin stores the data enrichment payload on the request context. The data enrichment payload can also be processed with additional_activity_handler
.
Only requests that are not blocked will reach the backend server, so specific logic must be applied to the processing function.
The following example includes the pre-condition checks required to process the data enrichment payload and enrich the request headers.
For more information and the available fields in the JSON, refer to the Data Enrichment documentation.
Log Enrichment
Access logs can be enriched with the HUMAN bot information by creating an NGINX variable with the proper name. To configure this variable, use the NGINX map directive in the HTTP section of your NGINX configuration file. This should be added before additional configuration files are added.
The following variables are enabled:
- Request UUID:
pxuuid
- Request VID:
pxvid
- Risk Round Trip:
pxrtt
- Risk Score:
pxscore
- Pass Reason:
pxpass
- Block Reason:
pxblock
- Cookie Validity:
pxcookiets
- Risk Call Reason:
pxcall