<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Protection on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.06/en/tags/protection/</link>
    <description>Recent content in Protection on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.06/en/tags/protection/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MITIGATOR Protection Quick Setup</title>
      <link>https://docs.mitigator.ru/v26.06/en/kb/quick-setup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.06/en/kb/quick-setup/</guid>
      <description>The materials in this article are intended to facilitate understanding of the protection organizing basic principles using MITIGATOR. Below is an example of setting up the system in the first iteration.
First, all packets are processed in &amp;ldquo;General Protection&amp;rdquo;, then 5-tuple routing rules distribute traffic to protection policies, and after the policies, the traffic returns to &amp;ldquo;General Protection&amp;rdquo; for the remaining countermeasures.
Processing of back traffic from the protected resource is not considered in this article.</description>
    </item>
    <item>
      <title>Checklist for Initial System Setup</title>
      <link>https://docs.mitigator.ru/v26.06/en/kb/system-checklist/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.06/en/kb/system-checklist/</guid>
      <description>List of steps Set up network integration. Specify a license key and set limits. Set up interaction via BGP. Upload GeoIP databases into the system. Set up delivery channels for system event notifications. Set up notifications via syslog. Enable protection. (Optional) Upload logos and background images for various interface themes. (Optional) Select the interface theme type and graph display style. Details 1. Set up network integration. The configuration is performed independently for each instance of the system and is based on the composition of the network infrastructure and the tasks to be solved.</description>
    </item>
    <item>
      <title>Checklist for Initial Configuration of the Protection Policy</title>
      <link>https://docs.mitigator.ru/v26.06/en/kb/policy-checklist/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.06/en/kb/policy-checklist/</guid>
      <description>List of steps Make sure the routing rules for the policy are set. Configure the policy to display only the necessary countermeasures. Set up countermeasures. Set up automatic packet capture. Set up autodetection. (Optional) Check the effect on legitimate traffic via the test mode. Enable protection policy. (Optional) Configure the log analyzer. (Optional) Pin countermeasure graphs. Details 1. Make sure the routing rules for the policy are set. Make sure that the routing rules are set for the policy on the &amp;ldquo;Policy Setup&amp;rdquo; tab of the &amp;ldquo;Protection policy&amp;rdquo; page.</description>
    </item>
    <item>
      <title>Reputational Lists From the Analytics Service</title>
      <link>https://docs.mitigator.ru/v26.06/en/kb/ss-feeds/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.06/en/kb/ss-feeds/</guid>
      <description>The MITIGATOR team generates regularly updated reputational lists of IP addresses, autonomous systems and JA3 fingerprints (hereinafter referred to as “feeds”).
Feeds can be imported into MITIGATOR as named lists and used in countermeasures and routing rules. To do this you need to specify Mitigator feeds as a source type. To do this, specify Mitigator feeds as the named list source type and select the required feed.
Feeds cannot be downloaded or viewed, even through the MITIGATOR Web interface.</description>
    </item>
  </channel>
</rss>