Mitigation

Deflect protects your website from a multitude of cyber attacks, including distributed denial of service (DDoS), brute force attacks against your login password, connection hijacking and much else. To achieve this level of protection we employ sensitive monitoring tools and various mitigation methods.

  • Banjax is responsible for early stage filtering, challenging and banning of bots, identified via regular expression (regex) matching, in conjunction with the Swabber module.
  • Swabber is a daemon for banning and unbanning IP addresses.
  • Edgemanage monitors Deflect edges health and rotates them in and out of our clients” DNS records.
  • Opsdash is an ElasticSearch cluster where the majority of Deflect’s traffic data is stored and queried.
  • Baskerville is a network traffic anomaly detector, for use in identifying and characterising malicious IP behaviour.

We’ve developed and pieced together these tools in order for our clients and the Deflect network to be resilient to any type of brute force attacks. They also help us gather, store and analyze information on attacks and attachers, building historical profiles and improving behaviour analysis of network traffic.

Herein we describe, in brief, how the Deflect network can be resilient to web attacks and how users can secure their own website behind Deflect.

  • Deflect infrastructure
  • Monitoring
  • Authentication
  • Challenger

Deflect infrastructure

Deflect is built on decentralization, with rented infrastructure in dozens of datacenters around the world. This approach offers flexibility and avoids central points of failure. Over the years we have worked with many providers and select the best among them by hardware specifications and network access, as well as their internal operating policies. We are keen to reduce the carbon footprint of our infrastructure and are continuously looking for datacenters powered by sustainable energy sources.

Due to our dynamic infrastructure model, we provision all machines with filesystem-level encryption.

Provider HQ Country Datacenters Countries
Hetzner Alemania FSN1-DC10, FSN1-DC6 Alemania
Limestone U.S.A. L.A., Dallas U.S.A.
OneProvider Canadá Amsterdam, Dusseldorf, London, New York Germany, Netherlands, U.K., U.S.A.
OVH Francia ERI1 U.K.
SeFlow Italy Milan Italy
SoYouStart Francia BHS2, ERI1, RBX4, RBX2 France, U.K., Canada
Veeble Netherlands NL, U.K. Netherlands, U.K.

Monitoring

At its core, the Deflect network is capable of logging information about any and all aspects of web traffic destined for our clients” websites (this includes traffic over SSL). This means that for each visitor accessing the Deflect network it is possible to record or otherwise ascertain:

  • Site accessed
  • Browser user agent
  • Deflect server queried
  • Time of request
  • Response code to the request
  • Cache status of the request
  • IP address, ASN of the requester
  • User device

This information is fed into Opsdash and Baskerville. It allows our clients to see traffic statistics in their dashboard profile, including detailed information on legitimate and banned requests.

Authentication

When your website is behind Deflect, requests for a new page will come from our caching servers. This means that they may be several minutes old and may not have the very latest updates. This is not ideal for when you are editing the website and need to see updates immediately. Deflect provides a special way to authenticate yourself to the system and access your website without caching. We call this Banjax authentication. After you have created the password in the Dashboard, the login page to your website (e.g. /wp-admin, /login, /administrator, etc.) will appear like this:

Banjax Authentication

Autentificación Banjax

Only those in possession of the authentication password will be able to proceed. This has an extra side effect of protecting your website’s editorial login from password brute-force attacks.

Challenger

Cuando un ataque DDoS no es mitigado automáticamente por las reglas de Deflect y comienza a tener un impacto negativo en su servidor, puede habilitar el filtro Challeger (retador). Ayudará a Deflect a distinguir los lectores reales del sitio web (quienes están usando un navegador web) de los bots automáticos. Challeger realiza esto sirviendo a todos los que acceden al sitio web un reto matemático en JavaScript. El usuario de navegador soluciona el reto y envía de vuelta su respuesta. El bot no puede hacer esto. Cuando se ha resuelto un reto, Deflect devuelve una cookie al navegador del lector. No se requiere la solución de retos adicionales de este lector durante las siguientes 24 horas.

_images/deflect_challenge.gif

Información para lectores del sitio web

Para recibir y procesar con éxito un reto, su navegador necesita tener habilitado JavaScript. Si está usando un bloqueador de JavaScript como p.e. «NoScript» , resultará en un mensaje de error diciéndole que JavaScript está bloqueado y se debe habilitar.

NoScript blocking JavaScript on the Black Lives Matter website

NoScript bloqueando JavaScript en el sitio web de Black Lives Matter

Información para clientes de Deflect

Challenger es una medida de defensa fuerte. No sólo bloqueará todo el tráfico malicioso, sino también el tráfico legítimo. Esto puede resultar en que los rastreadores web no sean capaces de acceder a su sitio web. Use Challenger como último recurso. Tenemos en lista blanca los siguientes rastreadores web y rangos de direcciones IPv4 para asegurar que los sitios web detrás de challenger aún se pueden indexar:

# Rastreador de Google

# Servidores IPN de PayPal

# Facebook

# En pruebas

¿Sitio web o rastreador excluido?

Si el filtro challenger (retador) bloquea su sitio web o rastreador web, podemos añadir su dirección IP a la lista blanca. Por favor, presente un ticket al equipo de Deflect y proporcione la siguiente información:

  • Nombre de su organización y una breve descripción del trabajo
  • Enlace o dirección/rangos de IP

Si su petición es legítima añadiremos su sitio web o rastreador a la lista blanca.

Código del Challenger de Banjax

`Aquí tiene un enlace <https://github.com/equalitie/banjax/blob/master/config/solver.html>`_al código servido por el Challenger (retador). A su computadora o smartphone sólo les debe llevar un segundo o dos resolver el reto.

Para más información acerca de BotnetDBP, Banjax, el filtrado en etapa temprana, y el retado y exclusión de bots, puede dirigirse hacia esta página