For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • General
    • About Enforcers
    • Support first-party HUMAN calls
    • Troubleshoot Enforcer configurations
  • Enforcer frameworks
    • Akamai ESI
    • Apache - C Module
    • ASP.NET
    • Callout Enforcer
    • Envoy Proxy
    • F5 BIGIP
    • Fastly JavaScript Compute@Edge
    • Google Cloud Platform (GCP) Callout Enforcer
      • Integrate the GCP Callout Enforcer
    • Kong Plugin
    • NGINX - C Module
    • NGINX - LUA Module
    • PHP
    • Python
    • Ruby
    • Salesforce Commerce Cloud Cartridge
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
Enforcer frameworks

Google Cloud Platform (GCP) Callout Enforcer

Was this page helpful?
Previous

Integrate the GCP Callout Enforcer

Next
Built with

The Google Cloud Platform (GCP) Callout Enforcer works with your organization’s Google Cloud Load Balancers to detect and manage malicious bot activity, account takeover attempts, and other fraudulent behavior. As traffic flows through your application, these Load Balancers send callouts to the HUMAN Enforcer for analysis. When the Enforcer detects suspicious activity, it’s blocked from your site and keeps malicious activity away from your web servers. This also enhances your users’ experience, since the decreased web server traffic means faster load times.

Specifically, the GCP Callout Enforcer uses Google Service Extensions on your application’s Load Balancer. These traffic extensions then send callouts to HUMAN’s Enforcer service to block and manage bot behavior. HUMAN provides this service via Google Private Service Connect (PSC).