A description of the available integration modes you can choose for your integration and what each means.
Ingest Mode is known as setting the integration to passive. The integration will set the Netacea Cookie & assign Unique User IDs to visitor requests, this is used to improve efficacy and aid in Data model analysis of websites traffic.
The Protector API will not be utilised whilst in Ingest, however network requests will be made by the integration in the case of solutions that utilise Kinesis or HTTP logging for recording of request logs.
Ingest Mode is most commonly used during Offline Bot Audit & when the integration needs to be placed into a passive mode by customers whilst other site maintenance is carried out.
Mitigate Mode is also known as setting the integration to active. The integration will make requests to the Protector API for recommendations, these recommendations will be actioned by the integration causing requests to be allowed, challenged or hard blocked. In the case of solutions that utilise Kinesis or HTTP logging for recording of request logs, this also takes place.
Mitigate mode is the most common setting for in-line POCs & solutions, it ensures customer sites are protected from malicious actors highlighted by Netacea's data models.
Inject Mode is also known as setting the integration to a hybrid between Inject & Mitigate. The integration will make requests to the Protector API for recommendation actions, and the API will respond with several headers that include the recommendation. The integration will not act on these recommendations.
The following headers are added, indicating the recommended action:
Inject Mode is commonly used by customers that prefer to provide custom mitigation and blocking methods aligned with business methodologies such as custom challenge types, tarpits, no response & more. The customer will be responsible for developing and maintaining the custom methods.