<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Challenge on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/challenge/</link>
    <description>Recent content in Challenge on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/challenge/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Challenge-response Authentication Module for HTTP/HTTPS</title>
      <link>https://docs.mitigator.ru/v26.04/en/integrate/web-challenger/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/integrate/web-challenger/</guid>
      <description>Web Challenger (WebC) is a Docker container containing NGINX and an HTTP/HTTPS request processing module that works in tandem with the HCA countermeasure in MITIGATOR.
Possibilities The HCA countermeasure redirects HTTP/HTTPS requests from unauthenticated IP addresses to WebC, where the sender is verified. If the verification is successful, the source IP address is added to the HCA&amp;rsquo;s authenticated table. HCA can also work with third-party L7 protection devices.
Multiple packet processors can work with one WebC when working in a cluster.</description>
    </item>
    <item>
      <title>MITIGATOR Challenge Response</title>
      <link>https://docs.mitigator.ru/v26.04/en/integrate/mcr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/integrate/mcr/</guid>
      <description>Tip This describes the MITIGATOR Challenge Response (MCR) protocol for developers of external systems. The MCR countermeasure is described in the built-in help.
MITIGATOR Challenge Response (MCR) is a protocol for IP authentication on MITIGATOR. The protocol can be implemented both by a protected application and separately, for example, when a game launcher is being checked, and game traffic is passed. The program that implements the protocol and passes the test is called the client (in the example above, the client is the launcher).</description>
    </item>
    <item>
      <title>TCP Protection with ISN Synchronization</title>
      <link>https://docs.mitigator.ru/v26.04/en/integrate/syncookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/integrate/syncookie/</guid>
      <description>MITIGATOR has a TCP protection mode with ISN synchronization, in which after checking the client, the connection is not interrupted, filtering is transparent and convenient. To do this, you need to install a kernel module on the protected server, that will provide the necessary information, and a synchronization agent that will be polled by the MITIGATOR system.
Protection mode with ISN synchronization is supported in countermeasures TCP, MINE, ATLS, DNS and BPF.</description>
    </item>
  </channel>
</rss>