NEW RESEARCH: WHY SHIELDIFY MOVED TO AWS.Read the report Sign in

A Managed Web Application Firewall in Front of Your Code.

Shieldify runs the OWASP Core Rule Set in front of every website, blocks exploit attempts at the edge and shows every decision together with the rule that made it.

OWASP CRSthe open, industry-standard rule set behind most managed WAFs.
JSON & XMLAPI and app request bodies are inspected, not only forms.
8 app profilesWordPress, XenForo, Nextcloud and more, one switch each.
Every blocklisted with the request, the rule and the time.
What it blocks

The attacks that target your application

A web application firewall (WAF) reads each HTTP request and stops the ones that try to exploit the software behind your website. Shieldify inspects requests at the edge, so an exploit attempt is blocked before it reaches your CMS, framework or database.

AttackExample requestResult
SQL injection/search?q=' OR 1=1--Blocked
Injection in JSON or XML APIs{"id": "1' UNION SELECT ..."}Blocked
Cross-site scripting (XSS)/?name=<script>Blocked
Path traversal and file inclusion/../../etc/passwdBlocked
Remote command execution/?cmd=;cat /etc/shadowBlocked
Sensitive file probes/.env, /.git/configBlocked
Vulnerability scannersKnown scanner signaturesBlocked
Protocol abuseMalformed or unexpected requestsBlocked
How it works

The OWASP Core Rule Set, managed for you

Shieldify uses the OWASP Core Rule Set (CRS), the open rule set maintained by the OWASP community and used by many commercial WAFs. Each request is checked against the rules; when the evidence adds up to an attack, the request is stopped at the edge and recorded with the rule that matched.

The query string, headers, cookies and the request body are all inspected: form fields, file upload names, and JSON and XML sent by APIs and apps, up to 1 MB per request, and file uploads up to 32 MB. A larger request is refused unless you allow large request bodies for the website; then it passes without inspection.

You do not install or update anything on your server, and there is no module to compile. The firewall runs in the same layer that handles DDoS protection and bot protection, so one request passes all three checks in one place.

Protection profiles

Pick how strict each website should be

Every website has its own profile. Websites start on Low; choose Medium or High when a website needs stricter checks.

Low

The recommended default. Blocks common exploits with the fewest false positives.

Medium

Wider detection for websites that want stricter checks. Test your forms and APIs after switching.

High

More aggressive detection for high-risk websites and periods of active abuse. Review the security events after switching.

Application profiles

Fewer false positives for popular applications

Admin and editor pages of popular applications send requests that can look like attacks, such as a post body full of HTML or a database query typed into phpMyAdmin. Shieldify includes the OWASP rule exclusion profiles for WordPress, XenForo, phpBB, Drupal, Nextcloud, phpMyAdmin, cPanel and DokuWiki.

  • One switch per application. Turn on the profiles for the software your website runs under Firewall > Applications.
  • Narrow by design. Each profile relaxes only the checks its own application is known to trip, and only on that application's pages.
Rule control

Turn off one rule, not the whole firewall

Some applications legitimately send requests that look unusual, for example a page builder that posts HTML or a search box that accepts code. When one rule gets in the way, open Firewall rules for that website, find the rule by name or category and switch it off. Everything else stays active, and you can turn all rules back on in one click.

  • Categories and single rules can be switched per website, for request and response checks.
  • Security events show each blocked request with its path, the rule that matched and the time, so you can see what a rule actually stops before you change it.
  • Changes apply live without downtime for your website.
Private pages

Keep admin areas out of reach

Login and admin pages are where most exploit attempts land. With Zero Trust private pages you can protect paths such as /admin or /wp-admin/* behind an email access request. Approved people receive a time-limited code; everyone else stays out, and the request never reaches your application. No plugin or code change is needed.

Trusted traffic

Narrow exceptions for machines you trust

Payment callbacks, uptime monitors and office tools sometimes need a direct path. An Allow rule under Custom rules on specific IP addresses or exact paths such as /api/payment/callback lets them skip the DDoS checks; the firewall still inspects them. Keep these rules narrow: a single path or address is safer than a wildcard.

FAQ

Questions, Answered.

Something else on your mind? Write to contact@shieldify.ee and a person will answer.

Is the WAF included in the price?

Yes. Every website gets the firewall, DDoS protection and bot protection in the same subscription. There are no add-ons. See pricing.

Does it work with WordPress, Laravel, Magento or my custom app?

Yes. The firewall works in front of the application, so it does not depend on the language, framework or host. Nothing is installed on your server. Built-in application profiles for WordPress, XenForo, phpBB, Drupal, Nextcloud, phpMyAdmin, cPanel and DokuWiki keep their admin and editor pages working without false positives.

What happens when a rule blocks a real user?

The blocked request appears in security events with the rule that matched. Turn on the application profile for the software you run, switch off that single rule for the website, or lower the profile, and the change applies live.

Does a WAF replace keeping my software up to date?

No. A WAF blocks known attack patterns and buys time, but updates fix the vulnerability itself. Use both.

Can I see what the firewall blocked?

Yes. Security events list every blocked request with its path, rule and time, and the dashboard shows blocked traffic over time.

Block Exploits BeforeThey Reach Your Code.

Put the OWASP Core Rule Set in front of your website with one DNS change.