Managed WAF for multi-site teams

Campus and agency teams run many sites — departmental CMS installs, shared logins, and not enough people to babysit a firewall. We put a managed WAF in front of each one and run it.

The multi-site problem

Departmental CMS installs lag on patches. Shared login pages take floods. DIY rules throw false positives on real forms. And if origin IPs stay on the public internet, a flood can bypass the edge.

Central IT and agency leads cannot staff another console per property.

How we run it

Onboard is typically about a day. Rules start in count. After 24 hours, your dashboard shows what's safe to block — one click.

$150/site/mo, 14-day trial for a single site or a small shop. Campus teams: Campus Estate — quote on request.

Campus Estate for campus teams

Campus Estate includes concierge DNS, named support (Mac / support@wafcybersecurity.com), quarterly threat/tuning review, priority virtual-patch / count→promote, and Promote Copilot.

Talk to sales team — we invoice. This is not the $150 Stripe checkout.

Estate Brain is coming

Promote Copilot is live today — per site, and you still click once.

Estate Brain will roll risk across the campus estate so you can see which sites need a human. It is not live.

Count mode before you block

Nothing is blocked on day one. Watch traffic for about 24 hours, then promote what's safe.

Promote Copilot is included on self-serve and Campus Estate — you still click once.

Read the count-mode explainer if you want the operators-first version of observe, then one-click promote.

Related