Skip to main content
Aegister Cloud Defender secures web applications by analyzing inbound traffic in real time. The process has several stages: How It Works

​
Connection and Integration

  • The domain secure.aegister.com connects to Cloud Defender through the Cloud_External_IP_Address.
  • The system combines Cloud WAF and OneFirewall Threat Prevention for layered protection.

​
Request Handling

  • When a client sends a request, for example to client1.domain1.com:
    • client1.domain1.com is set up as a CNAME for secure.aegister.com.
    • The request carries the originating IP address and the X-Forwarded-For header, which trace the traffic’s path.

​
Traffic Analysis

  • Client traffic flows through Cloud Defender (the “blue tunnel” in the diagram), where two checks run:
    • Threat Intelligence: requests from sources already known for attacking other targets are refused, using a continuously updated blocklist.
    • Reachability checks: the system periodically queries the client’s domain and endpoint to confirm the origin is responding. The result is shown on the Cloud Defender status page.

​
Decision and Action

Every request gets a decision before it reaches your application. Requests that pass the checks continue to the endpoint behind client1.domain1.com, with nothing for the user to notice. Refused are those from a source already known for attacking other targets and those trying to reach the origin while bypassing Cloud Defender. Every block is recorded with its time, source and request, and stays available on the status page.