A web application firewall is usually quoted as a monthly plan with a managed rule set attached. That line is easy to compare across vendors. The number that decides what you actually spend is quieter: how many request paths you protect, how often legitimate traffic looks hostile, and who is available when a rule blocks a paying customer.
This guide sets out a cost model for a finance committee and a calculator you can build before any quote arrives. It publishes no market rates: the same firewall can be a modest configuration job or a small operations programme, depending on the application behind it.
Five lines make up the bill
Proposals often price the subscription and leave the rest implicit. Ask for all five lines separately:
- Platform and rule subscription. Plan tier, number of domains or applications, request volume band, managed rule sets, bot features and the support level attached to the account.
- Implementation. DNS and certificate work, logging, origin protection, baseline policy, and the first deployment in detection mode rather than blocking mode.
- Tuning. Exception rules, custom rules for login, admin, API and checkout paths, and regression testing against real traffic.
- Integration and change work. Ordering with a CDN, application authentication, payment callbacks, log export to a SIEM, and keeping staging and production policies aligned.
- Operation. Monthly rule review, provider updates, incident response, change control and the evidence a client or auditor asks for.
A subscription without tuning produces noise or outages. A tuning project without an operating owner drifts out of date within two releases.
A formula that survives procurement
Ask every bidder to express the estimate in the same structure, then apply your own blended rate to the effort lines:
Annual cost = platform fees + implementation effort + (monthly tuning hours × 12 × blended rate) + change requests + internal review time + contingency
Implementation effort should be quoted in person-days by role, not a lump sum, so you can see whether the work is senior engineering or routine configuration. The blended rate should include salary overhead, or the comparison will flatter the vendor. Internal review time belongs in the budget: someone must read blocked-request samples, approve exceptions and test checkout after each change.
Contingency is not padding. A campaign, a new payment method or an application release can change traffic enough to require new rules. A reserve of roughly a tenth of first-year effort is a reasonable starting discipline, adjusted for how much your product team ships.
Where the effort hides
Detection mode takes time. Running managed rules in log-only mode for two to four weeks is the cheapest way to learn which rules your application cannot tolerate. Skipping it transfers the discovery cost to customers as blocked forms and failed payments.
Machine clients behave differently. Mobile apps, partner APIs and monitoring probes do not solve JavaScript challenges. If the WAF cannot distinguish them from bots, the integration work grows.
A calculator with eight inputs
Score each input from 1 (simple) to 5 (complex). The total is a scope indicator, not a price.
- Public applications and domains: one site scores 1; several brands, portals and APIs score 5.
- API surface: browser-only traffic scores 1; partner and mobile APIs with their own authentication score 5.
- Authentication and payment paths: a simple contact form scores 1; login, password reset, checkout and gateway callbacks score 5.
- Traffic variability: steady traffic scores 1; campaign peaks and seasonal spikes score 5.
- Application stack: a standard CMS with maintained plugins scores 1; a custom application with file uploads and rich input scores 5.
- Compliance and evidence: no external requirement scores 1; card payments or a regulated client audit scores 5.
- Environments: production only scores 1; production, staging and a demo environment score 5.
- Internal ownership: a named security owner scores 1; nobody owns the rule set scores 5.
Use the total to shape the engagement:
- 8–14: a single application, managed rules with light tuning and a documented monthly review.
- 15–22: multiple environments, custom rules and a staged enforcement plan.
- 23–30: several applications or APIs, dedicated tuning time and formal change control.
- 31–40: a regulated or multi-brand estate that needs an operating routine, not a configuration task.
Bangladesh details that change the estimate
- Payment gateway callback URLs and provider IP ranges must be allowed explicitly, or confirmations fail silently.
- Many mobile users share carrier-grade NAT addresses, so aggressive rate limits can punish real customers.
- Bangla content, transliterated search terms and emoji in reviews increase the exception workload.
- Shared hosting may not allow origin locking or custom header checks, which pushes work to the DNS and edge layer.
- Seasonal campaigns compress traffic into short windows, which is exactly when a new rule is most dangerous.
Budget worksheet
| Cost line | One-off | Recurring | Owner | Evidence |
|---|---|---|---|---|
| Platform and rule plan | Setup | Monthly or annual | IT lead | Invoice and plan limits |
| Implementation | Person-days | — | Vendor | Signed design and cutover record |
| Rule tuning | Person-days | Hours per month | Security owner | Exception register |
| Integration | Person-days | Change requests | Application owner | Tested callback list |
| Testing | Person-days | Per release | QA lead | Checkout and login test log |
| Training | Workshop | Annual refresh | Operations | Attendance and runbook |
| Review and reporting | — | Hours per month | Security owner | Monthly report |
| Contingency | Reserve | — | Finance | Approved change log |
Questions to ask before signing
- Which applications and request paths are in scope, and which are explicitly excluded?
- How long will rules run in detection mode before enforcement?
- Who writes and approves exceptions, and how quickly can one be removed?
- How are mobile apps and partner APIs identified without a browser challenge?
- Which logs are retained, where, and for how long?
- How is a rule change tested against checkout and login before release?
- What does the monthly review include, and who receives it?
A 90-day rollout you can price
Weeks 1–2: inventory public endpoints, confirm DNS control, enable logging and agree the exception owner.
Weeks 3–4: deploy managed rules in detection mode and collect a representative sample of blocked requests.
Weeks 5–6: build the exception register, tune the noisiest rules and test login, search, upload and checkout.
Weeks 7–8: enforce on low-risk paths first, keeping a documented bypass for the payment flow until it passes.
Weeks 9–10: enforce on authentication and checkout, then run a failed-payment and password-reset test.
Weeks 11–12: publish the runbook, set the monthly review and hand over the change log.
Each phase needs an acceptance record: a logged test of the five highest-value paths.
Metrics that show whether the money worked
Track false positives per hundred blocked requests, open exceptions and their age, time to deploy a rule change, challenged versus blocked traffic, origin error rate and checkout success. Add one commercial measure, such as completed orders or support tickets about access problems, so the security report does not float free of the business.
Where this fits in our work
WAF configuration sits inside Managed Technology & Cybersecurity, alongside website hardening and monitoring. The pricing page explains how assessment, implementation and monthly care are scoped separately. For the failure modes this work is designed to prevent, read the WAF configuration risk guide.
Sources
- OWASP, ModSecurity Core Rule Set project, accessed 17 November 2026.
- OWASP, Top 10 Web Application Security Risks, accessed 17 November 2026.
- NIST, SP 800-41 Rev. 1: Guidelines on Firewalls and Firewall Policy, accessed 17 November 2026.
- Cloudflare, Web Application Firewall documentation, accessed 17 November 2026.
- PCI Security Standards Council, PCI DSS resources, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.