Hi team,
Recently, Adobe and New Relic introduced support for Fastly signals in request headers, which provides an additional layer for bot protection.
In particular, we’re interested in the Sigsci_Tags header passed from Fastly to Adobe Commerce Cloud, where values correspond to applied signals, as outlined in Fastly’s documentation:
https://www.fastly.com/documentation/guides/next-gen-waf/using-ngwaf/signals/using-system-signals/
Could you please review the feasibility of enabling signal-based rule configuration (e.g., for SUSPECTED-BAD-BOT) directly through the Magento Fastly module to block incoming traffic based on bot signal?
Regards,
Eugene
Hi team,
Recently, Adobe and New Relic introduced support for Fastly signals in request headers, which provides an additional layer for bot protection.
In particular, we’re interested in the Sigsci_Tags header passed from Fastly to Adobe Commerce Cloud, where values correspond to applied signals, as outlined in Fastly’s documentation:
https://www.fastly.com/documentation/guides/next-gen-waf/using-ngwaf/signals/using-system-signals/
Could you please review the feasibility of enabling signal-based rule configuration (e.g., for SUSPECTED-BAD-BOT) directly through the Magento Fastly module to block incoming traffic based on bot signal?
Regards,
Eugene