Site Protection Netlify Edge Function Enforcer
HUMAN protects against malicious bot behavior. The Netlify Edge Function is deployed to your content delivery network (CDN) and dictates how traffic should be handled per your organization's policies.
Details
- Need Help? Contact HUMAN Security
We recommend you deploy HUMAN’s Enforcer integration on the Netlify CDN Edge. The Enforcer is a component of the HUMAN Defense Platform that protects advertisers, publishers, and end users from these threats.
- Account Takeover
- Credential stuffing
- Scraping
- Fake Account Takeover
- Inventory Hoarding
- Transaction abuse
- Malvertising
- Ad Quality
The following describes the three main HUMAN Defense Platform components employed by this integration: the Sensor, the Detector, and the Enforcer. Together, these components protect your web and mobile applications and APIs from malicious attacks, ensuring the security of your online assets and protecting the user journey.
-
Sensor: The Sensor is a JavaScript snippet that is inserted into your website. It collects data on user and device behavior, as well as network activities. This data helps in analyzing the authenticity of the device and application, and tracks user behavior and interaction. The Sensor collects various metrics using methods like DOM API, BOM API, and WebAssembly. It captures non-PII data about the running environment, device features, and user interactions, which are then used to detect whether a session is automated or not.
-
Detector: The Detector is a cloud-based component that processes the data collected by the Sensor and the Enforcer. It uses machine learning and behavioral analytics to evaluate this data in real-time and generate a risk score. This risk score helps in identifying whether a user is malicious. The Detector sends this information back to the user's device in a secure and encrypted token.
-
Enforcer: The Enforcer is a lightweight module that can be installed on your web application, load balancer, or Netlify CDN (recommended). It is responsible for enforcing the decisions made by the Detector. The Enforcer reads the token from the Detector and takes appropriate actions such as allowing, blocking, or challenging a request based on the risk score. It also acts as a backup sensor if there is no sensor data or if the token is malformed, relaying network telemetry to the Detector.