{"id":32724,"date":"2019-10-31T21:48:35","date_gmt":"2019-10-31T18:48:35","guid":{"rendered":"https:\/\/prohoster.info\/blog\/chto-est-chto-i-kto-est-kto-na-rynke-zashhity-ot-ddos\/"},"modified":"2019-10-31T21:48:35","modified_gmt":"2019-10-31T18:48:35","slug":"chto-est-chto-i-kto-est-kto-na-rynke-zashhity-ot-ddos","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/chto-est-chto-i-kto-est-kto-na-rynke-zashhity-ot-ddos","title":{"rendered":"Ce este ce \u0219i cine este cine pe pia\u021ba protec\u021biei \u00eempotriva DDoS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\u201eB\u0103iatul care ne-a f\u0103cut site-ul a configurat deja protec\u021bia \u00eempotriva DDoS.\u201d
\n\u201eAvem protec\u021bie \u00eempotriva DDoS, de ce a c\u0103zut site-ul?\u201d
\n\u201eC\u00e2t de multe mii cere Qrator?\u201d<\/p>\n

Pentru a r\u0103spunde corect la astfel de \u00eentreb\u0103ri din partea clien\u021bilor \/ \u0219efilor, ar fi bine s\u0103 \u0219tii ce se ascunde \u00een spatele denumirii \u201eprotec\u021bie \u00eempotriva DDoS\u201d. Alegerea serviciilor de protec\u021bie mai aminte\u0219te de alegerea unui medicament de c\u0103tre un medic, dec\u00e2t de alegerea unei mese \u00een IKEA.<\/p>\n

Lucrez \u00een sus\u021binerea site-urilor de 11 ani, am supravie\u021buit unor sute de atacuri asupra serviciilor pe care le sus\u021bin \u0219i acum voi povesti pu\u021bin despre \u201ebuc\u0103t\u0103ria\u201d protec\u021biei.
\n\"Ce<\/a><\/noindex>
\nAtacuri regulate. 350k req total, 52k req legitime<\/i>
\n<\/a><\/noindex>
\nPrimele atacuri au ap\u0103rut practic odat\u0103 cu internetul. DDoS ca fenomen a devenit masiv la sf\u00e2r\u0219itul anilor 2000 (uit\u0103-te www.cloudflare.com\/learning\/ddos\/famous-ddos-attacks<\/noindex>).
\nAproape din 2015-2016, aproape to\u021bi furnizorii de hosting s-au pus sub protec\u021bia \u00eempotriva atacurilor DDoS, la fel ca majoritatea site-urilor notabile din domeniile concurente (f\u0103 un whois dup\u0103 IP-urile site-urilor eldorado.ru, leroymerlin.ru, tilda.ws, vei vedea re\u021belele operatorilor de protec\u021bie).<\/p>\n

Dac\u0103 acum 10-20 de ani majoritatea atacurilor puteau fi respinse pe server (evalueaz\u0103 recomand\u0103rile sistemului administrator Lenta.ru Maxim Mo\u0219kov din anii \u201890: lib.ru\/WEBMASTER\/sowetywww2.txt_with-big-pictures.html#10<\/a><\/noindex>), atunci acum sarcinile de protec\u021bie s-au complicat.<\/p>\n

Tipuri de atacuri DDoS din perspectiva alegerii operatorului de protec\u021bie<\/h2>\n

Atacuri la nivel L3 \/ L4 (dup\u0103 modelul OSI)<\/h4>\n

\u2014 UDP flood din botnet (direct de pe dispozitivele infectate, se trimit multe cereri c\u0103tre serviciul atacat, serverele suprasolicit\u0103 canalul);
\n \u2014 amplificare DNS\/NTP\/etc (de pe dispozitivele infectate se trimit multe cereri c\u0103tre DNS\/NTP\/etc vulnerabile, adresa expeditorului este falsificat\u0103, o multitudine de pachete cu r\u0103spunsuri la cereri inund\u0103 canalul celui atacat; astfel se realizeaz\u0103 cele mai masive atacuri \u00een internetul modern);
\n \u2014 SYN \/ ACK flood (se trimit multe cereri de stabilire a conexiunii c\u0103tre serverele atacate, se produce o dep\u0103\u0219ire a cozii de conexiuni);
\n \u2014 atacuri cu fragmentare a pachetelor, ping of death, ping flood (c\u0103ut\u0103 pe google te rog);
\n \u2014 \u0219i altele.<\/p>\n

Aceste atacuri au ca scop \u201einundarea\u201d canalului serverului sau \u201euciderea\u201d capacit\u0103\u021bii sale de a accepta noul trafic.
\nDe\u0219i SYN\/ACK flood \u0219i amplificarea se difer\u0103 semnificativ, multe companii lupt\u0103 \u00eempotriva lor la fel de bine. Problemele apar cu atacurile din urm\u0103toarea grup\u0103.<\/p>\n

Atacuri la nivel L7 (nivelul aplica\u021biei)<\/h4>\n

\u2014 atacuri HTTP flood (dac\u0103 este atacat un site web sau un API HTTP);
\n \u2014 atacuri asupra zonelor vulnerabile ale site-ului (f\u0103r\u0103 cache, care suprasolicit\u0103 foarte mult site-ul etc.).<\/p>\n

Scopul este de a for\u021ba serverul s\u0103 lucreze \u201edin greu\u201d, proces\u00e2nd multe \u201ecereri aparent reale\u201d \u0219i s\u0103 r\u0103m\u00e2n\u0103 f\u0103r\u0103 resurse pentru cererile reale.<\/p>\n

De\u0219i exist\u0103 \u0219i alte tipuri de atacuri, acestea sunt cele mai comune.<\/p>\n

Atacurile serioase la nivelul L7 sunt create \u00een mod unic pentru fiecare proiect atacat.<\/p>\n

De ce 2 grupe?<\/b>
\nPentru c\u0103 exist\u0103 mul\u021bi care \u0219tiu s\u0103 resping\u0103 bine atacurile la nivel L3 \/ L4, dar nu se ocup\u0103 deloc de protec\u021bia la nivel de aplica\u021bie (L7), sau momentan fac fa\u021b\u0103 mai slab comparativ cu alternativele.<\/p>\n

Cine este cine pe pia\u021ba protec\u021biei DDoS<\/h2>\n

\n(p\u0103rerea mea personal\u0103)<\/p>\n

Protec\u021bia la nivel L3 \/ L4<\/h4>\n

Pentru a respinge atacurile cu amplificare (\u201esupersolicitare\u201d a canalului serverului), sunt suficiente canale largi (multe dintre serviciile de protec\u021bie se conecteaz\u0103 la majoritatea providerilor mari de backbone din Rusia \u0219i dispun de canale cu capacitate teoretic\u0103 de peste 1 Tbps). Nu uita\u021bi c\u0103 atacurile foarte rare cu amplificare dureaz\u0103 mai pu\u021bin de o or\u0103. Dac\u0103 sunte\u021bi Spamhaus \u0219i nu sunte\u021bi simpatic pentru toat\u0103 lumea \u2014 da, v\u0103 pot \u00eencerca s\u0103 doboare canalele timp de c\u00e2teva zile, chiar cu riscul de a afecta supravie\u021buirea botnet-ului mondial utilizat. Dac\u0103 ave\u021bi doar un magazin online, chiar dac\u0103 este mvideo.ru \u2014 1 Tbps timp de c\u00e2teva zile nu ve\u021bi vedea foarte cur\u00e2nd (sper).<\/p>\n

Pentru a respinge atacurile cu flood SYN \/ ACK, fragmentarea pachetelor etc., sunt necesare echipamente sau sisteme software pentru detectarea \u0219i interceptarea acestor atacuri.
\nMulte companii produc astfel de echipamente (Arbor, solu\u021bii de la Cisco, Huawei, solu\u021bii software de la Wanguard etc.), mul\u021bi operatori de backbone au deja instalat acest echipament \u0219i v\u00e2nd servicii de protec\u021bie DDoS (\u0219tiu despre instal\u0103rile de la Rostelecom, Megafon, TTK, MTS, practic la to\u021bi marii furnizori, asta o fac \u0219i hostingurile cu protec\u021bia lor a-la OVH.com, Hetzner.de, am avut experien\u021b\u0103 personal\u0103 cu protec\u021bia la ihor.ru). Unele companii dezvolt\u0103 propriile solu\u021bii software (tehnologii de tip DPDK permit procesarea traficului de zeci de gigabi\u021bi pe o singur\u0103 ma\u0219in\u0103 fizic\u0103 x86).<\/p>\n

Dintre juc\u0103torii cunoscu\u021bi, to\u021bi \u0219tiu s\u0103 resping\u0103 DDoS-urile L3\/L4 \u00eentr-o oarecare m\u0103sur\u0103. Nu pot s\u0103 v\u0103 spun cine are cea mai mare capacitate maxim\u0103 a canalului (aceasta este informa\u021bie confiden\u021bial\u0103), dar de obicei nu este at\u00e2t de important, iar diferen\u021ba const\u0103 doar \u00een c\u00e2t de repede se activeaz\u0103 protec\u021bia (imediat sau dup\u0103 c\u00e2teva minute de timp de nefunc\u021bionare al proiectului, a\u0219a cum se \u00eent\u00e2mpl\u0103 \u00een cazul Hetzner).
\n\u00centrebarea este c\u00e2t de calitativ se face acest lucru: un atac cu amplificare poate fi respins prin blocarea traficului din \u021b\u0103rile cu cea mai mare cantitate de trafic d\u0103un\u0103tor, sau se poate elimina doar traficul cu adev\u0103rat \u00een exces.
\nDar, din experien\u021ba mea, to\u021bi juc\u0103torii serio\u0219i de pe pia\u021b\u0103 fac fa\u021b\u0103 acestui lucru f\u0103r\u0103 probleme: Qrator, DDoS-Guard, Kaspersky, G-Core Labs (fosta SkyParkCDN), ServicePipe, Stormwall, Voxility, etc.
\nNu am avut de-a face cu protec\u021bia operatorilor precum Rostelecom, Megafon, TTK, Beeline, dar din p\u0103rerile colegilor, ofer\u0103 aceste servicii destul de calitativ, dar periodic se resimte lipsa de experien\u021b\u0103: uneori trebuie s\u0103 ajustezi ceva prin suportul operatorului de protec\u021bie.
\nUnii operatori au un serviciu separat de \u201eprotec\u021bie \u00eempotriva atacurilor la nivel L3\/L4\u201d, sau \u201eprotec\u021bia canalelor\u201d, care cost\u0103 mult mai pu\u021bin dec\u00e2t protec\u021bia la toate nivelurile.<\/p>\n

Dar cum reu\u0219e\u0219te un provider non-magistral s\u0103 resping\u0103 atacuri de sute de Gbit? El nu are canale proprii?<\/b>Operatorul de protec\u021bie se poate conecta la oricare dintre marii furnizori \u0219i poate respinge atacurile \u201epe cheltuiala lui\u201d. Va trebui s\u0103 pl\u0103te\u0219ti pentru canal, dar toate aceste sute de Gbit nu vor fi \u00eentotdeauna utilizate, exist\u0103 op\u021biuni pentru reducerea semnificativ\u0103 a costurilor canalelor \u00een acest caz, a\u0219a c\u0103 schema r\u0103m\u00e2ne func\u021bional\u0103.
\n\"Ce<\/a><\/noindex>
\nAm primit astfel de rapoarte de la protec\u021bia L3\/L4 superioar\u0103 pe temelie regulat\u0103, sprijinind sistemele furnizorului de hosting.<\/i><\/p>\n

Protec\u021bia la nivel L7 (nivel de aplica\u021bie)<\/h4>\n

Atacurile la nivel L7 (nivel de aplica\u021bie) le resping cu regularitate \u0219i calitate doar c\u00e2\u021biva.
\nAm o experien\u021b\u0103 real\u0103 destul de larg\u0103 cu
\n \u2014 Qrator.net;
\n \u2014 DDoS-Guard;
\n \u2014 G-Core Labs;
\n \u2014 Kaspersky.<\/p>\n

Ei iau o tax\u0103 pentru fiecare megabit de trafic curat, un megabit cost\u00e2nd \u00een jur de c\u00e2teva mii de ruble. Dac\u0103 e\u0219ti cu cel pu\u021bin 100 de megabi\u021bi de trafic curat \u2014 oh. Protec\u021bia va fi foarte scump\u0103. Pot s\u0103 v\u0103 povestesc \u00een articolele urm\u0103toare cum s\u0103 proiecta\u021bi aplica\u021bii pentru a economisi foarte bine pe capacitatea canalelor de protec\u021bie.
\nRegele adev\u0103rat al v\u00e2rfului este Qrator.net, restul r\u0103m\u00e2n \u00een urm\u0103. Qrator este, p\u00e2n\u0103 \u00een prezent, singurii \u00een experien\u021ba mea care ofer\u0103 un procent aproape de zero al alarmelor false, dar pre\u021burile lor sunt de c\u00e2teva ori mai mari dec\u00e2t ale altor juc\u0103tori de pe pia\u021b\u0103.<\/p>\n

Al\u021bi operatori ofer\u0103, de asemenea, protec\u021bie de calitate \u0219i stabil\u0103. Multe servicii aflate sub suportul nostru (inclusiv foarte cunoscute \u00een \u021bar\u0103!) sunt protejate de DDoS-Guard, G-Core Labs \u0219i sunt complet mul\u021bumi\u021bi de rezultatele ob\u021binute.
\n\"Ce<\/a><\/noindex>
\nAtacuri respinse de Qrator<\/i><\/p>\n

Am avut \u0219i experien\u021be cu operatori de protec\u021bie mai mici, cum ar fi cloud-shield.ru, ddosa.net, mii dintre ei. Nu-i voi recomanda cu siguran\u021b\u0103, deoarece experien\u021ba nu este foarte mare; voi vorbi despre principiile lor de func\u021bionare. Costul protec\u021biei lor este adesea cu 1-2 ordine mai mic dec\u00e2t al marilor juc\u0103tori. De obicei, ei cump\u0103r\u0103 un serviciu de protec\u021bie par\u021bial\u0103 (L3\/L4) de la unul dintre juc\u0103torii mai mari \u0219i \u00ee\u0219i dezvolt\u0103 propria protec\u021bie \u00eempotriva atacurilor la niveluri mai ridicate. Aceasta poate fi destul de eficient\u0103 \u0219i pute\u021bi ob\u021bine un serviciu bun la un pre\u021b mai mic, dar sunt totu\u0219i companii mici cu personal redus, v\u0103 rog s\u0103 \u021bine\u021bi cont de acest lucru.<\/p>\n

Care este dificultatea de a respinge atacurile la nivelul L7?<\/h4>\n

Toate aplica\u021biile sunt unice, iar traficul util trebuie permis, \u00een timp ce traficul d\u0103un\u0103tor trebuie blocat. Este dificil s\u0103 identifici \u00eentotdeauna robo\u021bii, a\u0219a c\u0103 este necesar s\u0103 se foloseasc\u0103 multe, \u00eentr-adev\u0103r Multe, grade de filtrare a traficului.<\/p>\n

C\u00e2ndva, modul nginx-testcookie (https:\/\/github.com\/kyprizel\/testcookie-nginx-module<\/a><\/noindex>), era suficient pentru a respinge un num\u0103r mare de atacuri. C\u00e2nd lucram \u00een industria de hosting, protec\u021bia L7 era construit\u0103 folosind nginx-testcookie.
\nDin p\u0103cate, atacurile au devenit mai complexe. testcookie utilizeaz\u0103 verific\u0103ri ale robo\u021bilor pe baza JS, iar mul\u021bi dintre robo\u021bii moderni reu\u0219esc s\u0103 le ocoleasc\u0103 cu succes.<\/p>\n

Botnet-urile atacatoare sunt de asemenea unice \u0219i trebuie luate \u00een considerare caracteristicile fiec\u0103rui botnet mare.
\nAmplificarea, inunda\u021bia direct\u0103 din botnet, filtrarea traficului din diferite \u021b\u0103ri (filtrare diferit\u0103 pentru diferite \u021b\u0103ri), inunda\u021bia SYN\/ACK, fragmentarea pachetelor, ICMP, inunda\u021bia http, iar la nivelul aplica\u021biei\/http se pot inventa un num\u0103r nelimitat de atacuri diferite.
\n\u00cen total, la nivelul protec\u021biei canalelor, echipamentului specializat pentru filtrarea traficului, software-ului special, set\u0103rilor suplimentare de filtrare pentru fiecare client pot exista zeci \u0219i sute de niveluri de filtrare.
\nPentru a gestiona corect aceasta \u0219i a ajusta set\u0103rile de filtrare pentru diferi\u021bi utilizatori, este nevoie de mult\u0103 experien\u021b\u0103 \u0219i de personal calificat. Chiar \u0219i un mare operator care decide s\u0103 ofere servicii de protec\u021bie nu poate \"pur \u0219i simplu s\u0103 arunce bani\" asupra problemei: experien\u021ba trebuie acumulat\u0103 pe site-urile afectate \u0219i pe declan\u0219\u0103rile false pe traficul legitim.
\nPentru un operator de protec\u021bie, nu exist\u0103 un buton de \"stopping DDoS\", ci un num\u0103r mare de instrumente pe care trebuie s\u0103 \u0219tii s\u0103 le folose\u0219ti.<\/p>\n

\u0218i \u00eenc\u0103 un exemplu bonus.
\n\"Ce<\/a><\/noindex>
\nServerul f\u0103r\u0103 protec\u021bie a fost blocat de host la un atac cu o capacitate de 600 Mbps.<\/i>
\n(\"Dispari\u021bia\" traficului nu este vizibil\u0103, deoarece doar un singur site a fost atacat, acesta a fost \u00eendep\u0103rtat temporar de pe server \u0219i blocarea a fost ridicat\u0103 \u00een decurs de o or\u0103).<\/i>
\n\"Ce<\/a><\/noindex>
\nAcela\u0219i server sub protec\u021bie. Agresorii s-au \"predat\" dup\u0103 o zi de atacuri respinse. Atacul \u00een sine s-a dovedit a nu fi cel mai puternic.<\/i><\/p>\n

Atacurile \u0219i protec\u021bia L3\/L4 sunt mai triviale, \u00een principal, depind de l\u0103\u021bimea de band\u0103, algoritmii de detec\u021bie \u0219i filtrare a atacurilor.
\nAtacurile L7 sunt mai complexe \u0219i originale, acestea depind de aplica\u021bia atacat\u0103, capacit\u0103\u021bile \u0219i fantezia atacatorilor. Protec\u021bia \u00eempotriva lor necesit\u0103 cuno\u0219tin\u021be \u0219i experien\u021b\u0103 considerabile, iar rezultatele pot s\u0103 nu fie imediate \u0219i nu sunt \u00eentotdeauna sigure. \u00cenc\u0103 nu a inventat Google o nou\u0103 re\u021bea neuronal\u0103 pentru protec\u021bie.
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u00ab\u041c\u0430\u043b\u044c\u0447\u0438\u043a, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0434\u0435\u043b\u0430\u043b \u043d\u0430\u043c \u0441\u0430\u0439\u0442, \u0443\u0436\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u043b \u0437\u0430\u0449\u0438\u0442\u0443 \u043e\u0442 DDoS\u00bb. \u00ab\u0423 \u043d\u0430\u0441 \u0436\u0435 \u0441\u0442\u043e\u0438\u0442 \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 DDoS, \u043f\u043e\u0447\u0435\u043c\u0443 \u0441\u0430\u0439\u0442 \u043b\u0435\u0433?\u00bb \u00ab\u0421\u043a\u043e\u043b\u044c\u043a\u043e-\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0442\u044b\u0441\u044f\u0447 \u0445\u043e\u0447\u0435\u0442 Qrator?\u00bb \u0427\u0442\u043e\u0431\u044b \u043d\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u043e \u043e\u0442\u0432\u0435\u0447\u0430\u0442\u044c \u043d\u0430 \u0442\u0430\u043a\u0438\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u0430\/\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u0438\u043a\u0430, \u043d\u0435\u043f\u043b\u043e\u0445\u043e \u0431\u044b \u0437\u043d\u0430\u0442\u044c, \u0447\u0442\u043e \u0441\u043a\u0440\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u0437\u0430 \u043d\u0430\u0437\u0432\u0430\u043d\u0438\u0435\u043c \u00ab\u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 DDoS\u00bb. \u0412\u044b\u0431\u043e\u0440 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0437\u0430\u0449\u0438\u0442\u044b \u0431\u043e\u043b\u044c\u0448\u0435 \u043d\u0430\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442 \u0432\u044b\u0431\u043e\u0440 \u043b\u0435\u043a\u0430\u0440\u0441\u0442\u0432\u0430 \u0432\u0440\u0430\u0447\u043e\u043c, \u0447\u0435\u043c \u0432\u044b\u0431\u043e\u0440 \u0441\u0442\u043e\u043b\u0430 \u0432 IKEA. \u042f […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24508,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32724","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Ce este ce \u0219i cine este cine pe pia\u021ba protec\u021biei \u00eempotriva DDoS | ProHoster","description":"\"B\u0103iatul care ne-a f\u0103cut site-ul a configurat deja protec\u021bia \u00eempotriva DDoS\". \"Avem protec\u021bie \u00eempotriva DDoS, de ce a c\u0103zut site-ul?\" \"C\u00e2te mii vrea Qrator?\" Ca s\u0103 putem r\u0103spunde normal la astfel de \u00eentreb\u0103ri.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/chto-est-chto-i-kto-est-kto-na-rynke-zashhity-ot-ddos","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0427\u0442\u043e \u0435\u0441\u0442\u044c \u0447\u0442\u043e \u0438 \u043a\u0442\u043e \u0435\u0441\u0442\u044c \u043a\u0442\u043e \u043d\u0430 \u0440\u044b\u043d\u043a\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 DDoS | ProHoster","og:description":"\u00ab\u041c\u0430\u043b\u044c\u0447\u0438\u043a, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0434\u0435\u043b\u0430\u043b \u043d\u0430\u043c \u0441\u0430\u0439\u0442, \u0443\u0436\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u043b \u0437\u0430\u0449\u0438\u0442\u0443 \u043e\u0442 DDoS\u00bb. \u00ab\u0423 \u043d\u0430\u0441 \u0436\u0435 \u0441\u0442\u043e\u0438\u0442 \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 DDoS, \u043f\u043e\u0447\u0435\u043c\u0443 \u0441\u0430\u0439\u0442 \u043b\u0435\u0433?\u00bb \u00ab\u0421\u043a\u043e\u043b\u044c\u043a\u043e-\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0442\u044b\u0441\u044f\u0447 \u0445\u043e\u0447\u0435\u0442 Qrator?\u00bb \u0427\u0442\u043e\u0431\u044b \u043d\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u043e \u043e\u0442\u0432\u0435\u0447\u0430\u0442\u044c \u043d\u0430 \u0442\u0430\u043a\u0438\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/chto-est-chto-i-kto-est-kto-na-rynke-zashhity-ot-ddos","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:48:35+00:00","article:modified_time":"2019-10-31T18:48:35+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32724","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 12:16:55","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:53:25","updated":"2026-01-21 12:16:55","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/32724","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=32724"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/32724\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/24508"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=32724"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=32724"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=32724"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}