Who it is for
Any organisation whose application, portal or website is reachable on the public internet. Login pages, password resets, search and forms attract automated traffic from the day they go live, and those are the paths this service is built around.
It suits government agencies that must stay online when hostile traffic arrives, and conglomerates and software providers that serve many customer domains and want the same protection on every one of them.
What it does
- Protection profiles (Standard, Strict, Government, and custom), so each domain carries a level of protection that fits its audience.
- Fair-use limits on how often a client can send requests, which is what most teams call rate limiting. One source cannot exhaust the application on its own.
- Blocking of hosting-network traffic and fake bots, so automation running from data-centre networks, or posing as a legitimate crawler, is turned away at the edge.
- Managed rules that inspect requests for common web attack patterns before they reach your application.
- Human verification, a check that asks a visitor to show they are a person before continuing.
- An “under attack” mode, a stricter posture for periods of active attack.
How it works
The firewall and traffic limits sit on the same path as the domain itself.
- The domain is approved. Each domain is added and manually approved, then pointed at BrandPort with one DNS record.
- Traffic arrives at the edge. Requests reach the nearest of 300+ edge locations worldwide on a global CDN.
- Protection is applied. The domain’s protection profile, fair-use limits, bot blocking and managed rules are applied there, before anything reaches your application.
- Your application receives the rest. Requests that pass continue to your existing application, served with automatic HTTPS.
Edge controls reduce how much of your application attackers can reach and how hard they can push it. They do not replace patching, multi-factor authentication or monitoring. Our article Bots are scanning your website right now: how governments and enterprises stop defacement and downtime explains how the two fit together.
Frequently asked questions
Is this a web application firewall?
Yes, in the sense that matters to most teams: managed rules inspect requests at the edge before they reach your application, alongside traffic limits and bot blocking. It complements secure code and timely patching rather than replacing them.
What is rate limiting, and how does BrandPort apply it?
Rate limiting caps how many requests a client can make in a given period. In BrandPort it takes the form of fair-use limits, applied at the edge for each domain, so a single source cannot overwhelm login, search or form pages.
Does it work with our existing application?
Yes. BrandPort works with any web app, whether no-code, low-code or custom-built. It does not host your application. It sits in front of it on a global CDN.
How do we start?
Request a briefing. BrandPort is offered by invitation. Tell us about the application, the domains and the traffic you are concerned about.
Request a briefing
By invitation. Tell us about the application, the domains it serves and the traffic you are concerned about, and we will follow up.
Request a briefing