<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webc on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/webc/</link>
    <description>Recent content in Webc on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/webc/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>
  </channel>
</rss>