Firewall
Every app on Apply.Build sits behind a web application firewall (WAF). It's on for every app and every plan, and there is nothing to configure.
How it works
Every request to your app passes through the firewall before it reaches the app. The firewall runs the OWASP Core Rule Set together with Apply.Build's own rules, and blocks requests that match known attack patterns, such as:
- looking for secret files like
/.envor/.git/config - injecting database queries
- guessing passwords on login forms
- probing for backdoors and path traversal
Request bodies, including file uploads, are inspected too.
Bans
A client that keeps sending attacks is banned. A banned client is shut out of every app on Apply.Build, not just the one it attacked.
Viewing blocked traffic
Open Security in the dashboard. The Security Stats tab shows blocked threats and banned clients, where they come from, and which attacks were tried most.
Custom rules
You can't add your own rules or block IP addresses yourself. Rules and bans are managed by Apply.Build, and new rules are added for every app when a new attack appears.
Blocked by mistake
If you think legitimate requests to your app are being blocked, contact support with your app ID and an example of the request.