Ecommerce protection, checkout, edge and traffic you can name
Opselis
Carding, stuffing and a jump during a campaign. WAF on the cart, origin hidden, and ntopng says whether these are customers or a scan. Before the peak we test the checkout path, not the homepage.
A store fails either on bots or on its own peak. Carding and stuffing hit /login and payment. Scraping cleans stock levels. Magecart waits for a script on origin. A marketing campaign adds traffic nobody will tell from an attack if there is no baseline map of flows.
At the edge: Cloudflare on the store hostname and API. Rate limit on login and checkout. Bot score on paths that are not a payment webhook. Origin without a public IP. WAF does not replace patching Magento or a custom checkout, it only cuts the mass before it reaches PHP and the database.
On the network: ntopng shows hosts, flows and applications. TLS, HTTP and DNS are visible without guessing whether the jump is customers or a scan. The same picture goes to on-call together with Cloudflare and Wazuh on store, database and panel hosts.
Before the peak we load-test the cart path, not the homepage. Then change windows are closed, dual-path backup is checked, and the playbook says who raises the challenge, who scales, who stops the campaign. Ecommerce protection is these three layers together, not a TLS certificate on the storefront.