Firewall
Elephant Firewall supersedes the previous security blocking system, by adding two extremely fast layers running at Application Server scope.
The main advantages over the previous system are:
- Container-wide vs app-wide, preventing malicious attacks before they get into the application.
- Two layers vs one layer, it tracks IP and sub-net until either of them is punished, or expires. Then shifts to the blocking layer.
- Auto expire vs positive tracking, takes the burden out of the tracking system with a much lighter blocking layer.
- Small footprint, less use of memory and processing.
Monitoring server usage
| Main issues | Desciption |
|---|---|
| Volumetric DoS or rate-limit violation | Checks upper and lower usage and applies a block when exceeded, based on lapsed-time |
| Application server access violation | Allows a minimum error margin and applies a block when exceeded, based on lapsed-time |
| Excessive usage of obfuscation | Checks upper and lower usage and applies a block when exceeded, based on lapsed-time |
| Automated resource-scrapers | Checks upper and lower usage and applies a block when exceeded, based on lapsed-time |
| Unregistered or aggressive crawler subnet | Checks upper and lower usage and applies a block when exceeded, based on lapsed-time |
White-listing
Elephant Firewall recognizes in-app work actions, allowing visitors to have a big load of working data.
White-listing is completely automated and non-permanent.
Status
Firewall status is included in BaaS Console -> Tools -> Settings -> System Status.
| English | 10/07/26 20:54 | Lluís Turró Cutiller |
