An online store looks special because money moves through it, but a web application firewall still sees ordinary HTTP. Search boxes, login forms, cart updates, and staff consoles are requests that can carry SQL injection, cross-site scripting, path traversal, or automated abuse. Protecting that traffic starts with placement and a short checklist, not with a promise that a firewall understands your catalog software.
SafeLine is a self-hosted WAF. Deployed in front of a web application, it acts as a reverse proxy: clients reach SafeLine first, it filters and monitors HTTP and HTTPS, and it forwards traffic that its policies allow to the origin. The introduction describes that arrangement as a shield that blocks malicious requests and can stop unauthorized data from leaving the app, based on policy. That description is in the SafeLine introduction at https://docs.waf.chaitin.com/en/home.
Decide placement before you tune rules
The supplied guides do not describe a connector for a named shopping cart, payment gateway, or hosted storefront platform. If you cannot put your own reverse proxy in front of the origin, do not assume an integration exists. Treat protection as proxy placement for hostnames you control.
For each application, the console asks for a domain, hostname, or IP, the port SafeLine will listen on, and the upstream address of the real app. HTTPS applications use the SSL option. After saving, resolve that domain to the SafeLine server so visitors hit the proxy instead of the origin directly. Those fields and the DNS step are documented in the application guide at https://docs.waf.chaitin.com/en/GetStarted/AddApplication.
Use this checklist before you cut over DNS:
- List every name that should pass through the proxy: storefront, API, and admin. Skip names you cannot point at SafeLine.
- Write down the upstream address and port. SafeLine forwards cleaned traffic there. It does not become the store.
- Keep customer hostnames separate from staff hostnames so a strict control does not land on shoppers.
- Keep a rollback. If a legitimate checkout request is blocked, you need a way to restore the previous DNS target.
- Confirm the machine meets the install baseline before a sale depends on it.
The deploy guide requires Linux, x86_64 or arm64, Docker 20.10.14 or above, Docker Compose 2.0.0 or above, and a minimum of 1 CPU core, 1 GB of memory, and 5 GB of disk. The CPU must support ssse3. An ARM install requires a Pro license. The Personal Edition is not supported on ARM. See https://docs.waf.chaitin.com/en/GetStarted/Deploy.
Apply only the controls the docs name
The introduction lists five core capabilities: defenses for web attacks, proactive defense against bot abuse, HTML and JS code encryption, IP-based rate limiting, and a web access control list. The feature list adds rate limiting, a CAPTCHA challenge, an authentication challenge, and dynamic protection. Map those onto store paths. Do not invent a checkout plugin around them.
Attack blocking is the broad filter. The docs name SQL injection, XSS, code injection, OS command injection, CRLF injection, LDAP injection, XPath injection, RCE, XXE, SSRF, path traversal, backdoor, brute force, HTTP flood, and bot abuse. Catalog search, account forms, and any URL that reflects input are the first paths to verify. A stopped request should show the blocking page. Open the console attack list and click detail to inspect it.
Rate limiting throttles traffic above limits you define. The stated reasons are DoS attacks, brute-force attempts, traffic surges, and other abuse. On a store, login, password reset, coupon checks, and inventory lookups are sensible places to consider it. The docs do not give a cart-size or checkout number, so choose a limit from your own traffic, not from a copied example.
CAPTCHA is documented as a challenge that allows human users and blocks crawlers and bots. It can fit account creation and repeated login. It is a weak default for every product page, because casual browsing should not stop for a puzzle. Enable it on abuse-prone paths, then place a real order and confirm the flow still completes.
The authentication challenge is different. Visitors must enter the password or they are blocked. That is not a customer login. Use it on a private admin hostname, not on the catalog and not on checkout.
Dynamic protection, when turned on, encrypts HTML and JS from the origin on each visit. Treat it as an extra layer, not as a patch for an injection bug in your templates. After enabling it, reload the storefront and confirm images, scripts, and the cart still behave.
IP-based rate limiting and the access control list can narrow who reaches admin, or how fast one address retries a password. The introduction names both, but it does not provide a sample rule for stores. Write down who must still reach the console, test from an allowed address, and test from an address that should fail.
Rehearse the block and the purchase
The application guide includes sample queries for SQL injection, XSS, path traversal, code injection, and XXE. Swap in your domain. A blocking page means that case was stopped. Then use detail in the console so the event is not just a guess.
Attack samples are not enough for a store. Walk a customer path: open a product, search, sign in, change the cart, and reach checkout. If a safe request is blocked, fix the policy before a campaign. Removing the proxy and hoping the origin is fine is not a test result.
A WAF is not coverage for card handling, warehouse rules, or bugs in application code. It filters and monitors HTTP between the internet and the app. Blocked requests do not reach the origin. Allowed requests still have to be handled safely by the store.
Does a WAF replace checkout validation?
No. SafeLine filters and monitors HTTP and HTTPS in front of the application and forwards allowed traffic to the upstream. Price checks, session handling, and payment flows stay in the application.
Should the admin panel and the catalog share one policy?
Not by default. Add each hostname you control with its own domain, port, and upstream. Keep the authentication challenge and tighter access control on staff entry points. Keep the public catalog on controls a shopper can pass.
Will bot controls interrupt a sale?
They can if you enable them on every page. CAPTCHA is for separating humans from crawlers and bots. The authentication challenge blocks anyone who does not enter its password. Retest login and checkout after each change.
How do I confirm an attack was blocked?
Send the documented sample cases to your own domain. Expect the blocking page, then open the attack list and click detail. In the same window of time, repeat a normal browse and cart flow.
What must be true before store DNS points at SafeLine?
The server should meet the published minimum: Linux, a supported architecture, Docker and Compose at the stated versions, ssse3, and the stated CPU, memory, and disk floor. On ARM, plan for a Pro license, because the Personal Edition is not supported there.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.