Cloud Defender or a traditional WAF

A Web Application Firewall (WAF) can be installed in house, as an appliance or software, or used as a managed service. What changes for your sites and APIs.

In short

There is no right choice for everyone: it depends on where the applications are and who can look after them every day.

Cloud Defender

Makes sense when:

  • You protect sites and APIs exposed to the internet and nobody in the company has time to run a WAF.
  • You want DDoS protection and malicious IP blocking without installing hardware.
  • You want to see blocked attacks in Cyber Console, next to the other services.

In-house WAF

Makes sense when:

  • You need to protect internal applications that are not reachable from the internet.
  • Contractual or regulatory constraints prevent traffic from passing through an external service.
  • You need very specific rules and have a team that writes and maintains them.

Point by point

Comparison checked on 1 October 2026.3
Activation Cloud DefenderA DNS record pointing to secure.aegister.com, with no code changes In-house WAFInstallation, configuration and placement in the network
Maintenance Cloud DefenderUpdates and rules are on us In-house WAFUpdates, patches and capacity are on you
Rules against SQL injection and XSS Cloud DefenderDetection with the OWASP Core Rule Set on every request; you switch on blocking yourselves, site by site, in Cyber Console In-house WAFConfigured and maintained in house
Requests that are themselves an attack Cloud DefenderBlocked: hunting for files such as .env or .git, path traversal, Log4Shell strings In-house WAFDepends on the rules enabled
Rules for each site Cloud DefenderIn Cyber Console: blocked and always allowed addresses, restricted pages, refused or accepted countries; a 24 hour automatic block for sources that request attack URLs In-house WAFConfigured and maintained in house
Malicious IP addresses Cloud DefenderBlocked with our threat intelligence, list updated automatically In-house WAFIf the product has a feed and the licence includes it
Volumetric DDoS attacks Cloud DefenderHandled at the edge, before your line In-house WAFA device in house cannot stop an attack that saturates the connection
Direct access to the server Cloud DefenderThe server accepts only traffic that comes through Cloud Defender In-house WAFDepends on how the network is configured
TLS certificates Cloud DefenderHandled at the edge In-house WAFHandled by you
Internal applications Cloud DefenderNot covered: Cloud Defender protects what is exposed to the internet In-house WAFCovered, if the WAF sits in the internal network
Visibility Cloud DefenderIn Cyber Console: threats blocked, attacking IPs, origins and the layer that blocked In-house WAFIn the WAF's console

Getting started with Cloud Defender

Frequently asked questions

No. A DNS record is enough: the applications stay as they are.

A few minutes for the DNS record, once our side is ready. There is no tuning period: protection is active from the start.

Yes: to inspect HTTPS requests, Cloud Defender handles TLS at the edge and forwards only allowed traffic to your server.

No: it protects sites and APIs reachable from the internet. Internal applications need protection inside your network.

Not sure yet which fits you?

The Cyber Check-up returns your company's cyber profile and the priorities to start from.