{"id":39334,"date":"2019-10-31T22:30:19","date_gmt":"2019-10-31T19:30:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat\/"},"modified":"2019-10-31T22:30:19","modified_gmt":"2019-10-31T19:30:19","slug":"pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat","title":{"rendered":"Pro\u010d tradi\u010dn\u00ed antiviry nejsou vhodn\u00e9 pro ve\u0159ejn\u00e1 cloudov\u00e1 \u0159e\u0161en\u00ed. A co s t\u00edm?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

St\u00e1le v\u00edce u\u017eivatel\u016f p\u0159en\u00e1\u0161\u00ed celou svou IT infrastrukturu do ve\u0159ejn\u00e9ho cloudu. Nicm\u00e9n\u011b v p\u0159\u00edpad\u011b nedostate\u010dn\u00e9 antivirov\u00e9 kontroly v infrastruktu\u0159e z\u00e1kazn\u00edka vznikaj\u00ed v\u00e1\u017en\u00e1 kybernetick\u00e1 rizika. Praxe ukazuje, \u017ee a\u017e 80 % st\u00e1vaj\u00edc\u00edch vir\u016f se skv\u011ble usazuje ve virtu\u00e1ln\u00edm prost\u0159ed\u00ed. V tomto p\u0159\u00edsp\u011bvku si pov\u00edme, jak ochr\u00e1nit IT zdroje ve ve\u0159ejn\u00e9m cloudu a pro\u010d tradi\u010dn\u00ed antiviry pro tyto \u00fa\u010dely nejsou zcela vhodn\u00e9. <\/b><\/p>\n

\"Pro\u010d
\n
\nNejd\u0159\u00edve si pov\u00edme, jak jsme do\u0161li k my\u0161lence, \u017ee pro ve\u0159ejn\u00fd cloud nevyhovuj\u00ed obvykl\u00e9 n\u00e1stroje antivirov\u00e9 ochrany a \u017ee jsou pot\u0159eba odli\u0161n\u00e9 p\u0159\u00edstupy k ochran\u011b zdroj\u016f. <\/a><\/noindex><\/p>\n

Za prv\u00e9, poskytovatel\u00e9 obvykle zaji\u0161\u0165uj\u00ed pot\u0159ebn\u00e1 opat\u0159en\u00ed k tomu, aby garantovali vysokou \u00farove\u0148 ochrany sv\u00fdch cloudov\u00fdch platforem. Nap\u0159\u00edklad my v #CloudMTS analyzujeme ve\u0161ker\u00fd s\u00ed\u0165ov\u00fd provoz, monitorujeme z\u00e1znamy bezpe\u010dnostn\u00edch syst\u00e9m\u016f na\u0161eho cloudu a pravideln\u011b prov\u00e1d\u00edme penetra\u010dn\u00ed testy. Segmenty cloudu, kter\u00e9 jsou sv\u011b\u0159eny jednotliv\u00fdm klient\u016fm, tak\u00e9 mus\u00ed b\u00fdt spolehliv\u011b chr\u00e1n\u011bny. <\/p>\n

Za druh\u00e9, klasick\u00e1 varianta boje s kybernetick\u00fdmi riziky p\u0159edpokl\u00e1d\u00e1 instalaci antiviru a prost\u0159edk\u016f jeho spr\u00e1vy na ka\u017ed\u00e9m virtu\u00e1ln\u00edm stroji. Nicm\u00e9n\u011b p\u0159i velk\u00e9m po\u010dtu virtu\u00e1ln\u00edch stroj\u016f m\u016f\u017ee b\u00fdt tato praxe neefektivn\u00ed a vy\u017eadovat zna\u010dn\u00e9 mno\u017estv\u00ed v\u00fdpo\u010detn\u00edch zdroj\u016f, \u010d\u00edm\u017e d\u00e1le zat\u011b\u017euje infrastrukturu z\u00e1kazn\u00edka a sni\u017euje celkov\u00fd v\u00fdkon cloudu. To se stalo kl\u00ed\u010dov\u00fdm d\u016fvodem pro hled\u00e1n\u00ed nov\u00fdch p\u0159\u00edstup\u016f k vytv\u00e1\u0159en\u00ed efektivn\u00ed antivirov\u00e9 ochrany virtu\u00e1ln\u00edch stroj\u016f z\u00e1kazn\u00edk\u016f. <\/p>\n

Krom\u011b toho v\u011bt\u0161ina dostupn\u00fdch antivirov\u00fdch \u0159e\u0161en\u00ed na trhu nen\u00ed p\u0159izp\u016fsobena pro \u0159e\u0161en\u00ed \u00fakol\u016f ochrany IT zdroj\u016f ve ve\u0159ejn\u00e9m cloudov\u00e9m prost\u0159ed\u00ed. Obvykle se jedn\u00e1 o t\u011b\u017ek\u00e1 EPP \u0159e\u0161en\u00ed (Endpoint Protection Platforms), kter\u00e1 nav\u00edc nenab\u00edzej\u00ed pot\u0159ebnou p\u0159izp\u016fsobivost na stran\u011b klient\u016f cloudov\u00e9ho poskytovatele. <\/p>\n

St\u00e1v\u00e1 se z\u0159ejm\u00fdm, \u017ee tradi\u010dn\u00ed antivirov\u00e1 \u0159e\u0161en\u00ed se \u0161patn\u011b hod\u00ed pro pr\u00e1ci v cloudu, proto\u017ee v\u00e1\u017en\u011b zat\u011b\u017euj\u00ed virtu\u00e1ln\u00ed infrastrukturu b\u011bhem aktualizac\u00ed a skenov\u00e1n\u00ed, tak\u00e9 nemaj\u00ed pot\u0159ebn\u00e9 \u00farovn\u011b role managementu a nastaven\u00ed. D\u00e1le podrobn\u011b probereme, pro\u010d cloud pot\u0159ebuje nov\u00e9 p\u0159\u00edstupy k antivirov\u00e9 ochran\u011b. <\/p>\n

Co by m\u011bl antivirus um\u011bt v ve\u0159ejn\u00e9m cloudu <\/h2>\n

\nPoj\u010fme se tedy zam\u011b\u0159it na specifika pr\u00e1ce ve virtu\u00e1ln\u00edm prost\u0159ed\u00ed: <\/p>\n

\u00da\u010dinnost prov\u00e1d\u011bn\u00ed aktualizac\u00ed a hromadn\u00fdch kontrol podle pl\u00e1nu.<\/b> Pokud v\u00fdznamn\u00e9 mno\u017estv\u00ed virtu\u00e1ln\u00edch stroj\u016f, kter\u00e9 pou\u017e\u00edvaj\u00ed tradi\u010dn\u00ed antivirus, sou\u010dasn\u011b iniciuje aktualizaci, v cloudu dojde k takzvan\u00e9 \u201eaktualiza\u010dn\u00ed bou\u0159i\u201c. Kapacity ESXi hostitele, na kter\u00e9m je um\u00edst\u011bno n\u011bkolik virtu\u00e1ln\u00edch stroj\u016f, nemus\u00ed sta\u010dit na zpracov\u00e1n\u00ed p\u0159\u00edvalov\u00fdch \u00faloh spu\u0161t\u011bn\u00fdch ve v\u00fdchoz\u00edm nastaven\u00ed. Z pohledu cloudov\u00e9ho poskytovatele m\u016f\u017ee tento probl\u00e9m v\u00e9st k dodate\u010dn\u00fdm z\u00e1t\u011b\u017e\u00edm na \u0159adu ESXi hostitel\u016f, co\u017e nakonec povede k poklesu v\u00fdkonu virtu\u00e1ln\u00ed infrastruktury cloudu. To se m\u016f\u017ee odrazit i na v\u00fdkonu virtu\u00e1ln\u00edch stroj\u016f dal\u0161\u00edch klient\u016f cloudu. Podobn\u00e1 situace m\u016f\u017ee nastat p\u0159i spu\u0161t\u011bn\u00ed hromadn\u00e9ho skenov\u00e1n\u00ed: sou\u010dasn\u00e9 zpracov\u00e1n\u00ed velk\u00e9ho mno\u017estv\u00ed podobn\u00fdch po\u017eadavk\u016f od r\u016fzn\u00fdch u\u017eivatel\u016f diskov\u00fdm syst\u00e9mem bude negativn\u011b ovliv\u0148ovat v\u00fdkon cel\u00e9ho cloudu. S vysokou pravd\u011bpodobnost\u00ed se sn\u00ed\u017een\u00ed v\u00fdkonu \u00falo\u017ei\u0161t\u011b odraz\u00ed na v\u0161ech klientech. Tyto skokov\u00e9 z\u00e1t\u011b\u017ee nepot\u011b\u0161\u00ed ani poskytovatele, ani jeho z\u00e1kazn\u00edky, proto\u017ee ovliv\u0148uj\u00ed \u201esoused\u00e9\u201c v cloudu. Z tohoto pohledu m\u016f\u017ee tradi\u010dn\u00ed antivirus p\u0159edstavovat zna\u010dn\u00fd probl\u00e9m.<\/p>\n

Bezpe\u010dn\u00e1 karant\u00e9na.<\/b> Pokud je v syst\u00e9mu nalezen soubor nebo dokument potenci\u00e1ln\u011b infikovan\u00fd virem, je zasl\u00e1n do karant\u00e9ny. Samoz\u0159ejm\u011b, infikovan\u00fd soubor lze okam\u017eit\u011b smazat, ale to je \u010dasto pro v\u011bt\u0161inu firem nep\u0159ijateln\u00e9. Firemn\u00ed enterprise antiviry, kter\u00e9 nejsou p\u0159izp\u016fsobeny k pou\u017eit\u00ed v cloudu poskytovatele, obvykle maj\u00ed spole\u010dnou karant\u00e9nn\u00ed z\u00f3nu \u2014 do n\u00ed spadaj\u00ed v\u0161echny infikovan\u00e9 objekty. Nap\u0159\u00edklad ty, kter\u00e9 byly objeveny na po\u010d\u00edta\u010d\u00edch u\u017eivatel\u016f firmy. Klienti cloudov\u00e9ho poskytovatele \u201e\u017eij\u00ed\u201c ve sv\u00fdch vlastn\u00edch segmentech (nebo tenantech). Tyto segmenty jsou nepr\u016fhledn\u00e9 a izolovan\u00e9: klienti o sob\u011b nev\u011bd\u00ed a samoz\u0159ejm\u011b nevid\u00ed, co do cloudu umis\u0165uj\u00ed ostatn\u00ed. Je z\u0159ejm\u00e9, \u017ee do spole\u010dn\u00e9 karant\u00e9ny, kterou budou vyu\u017e\u00edvat v\u0161ichni u\u017eivatel\u00e9 antiviru v cloudu, se potenci\u00e1ln\u011b m\u016f\u017ee dostat dokument obsahuj\u00edc\u00ed d\u016fv\u011brn\u00e9 informace nebo obchodn\u00ed tajemstv\u00ed. To je pro poskytovatele a jeho klienty nep\u0159ijateln\u00e9. Proto m\u016f\u017ee b\u00fdt \u0159e\u0161en\u00ed pouze jedno \u2013 osobn\u00ed karant\u00e9na pro ka\u017ed\u00e9ho klienta ve sv\u00e9m segmentu, do n\u00ed\u017e nemaj\u00ed p\u0159\u00edstup ani poskytovatel, ani ostatn\u00ed klienti. <\/p>\n

Individu\u00e1ln\u00ed bezpe\u010dnostn\u00ed politiky. <\/b>Ka\u017ed\u00fd klient v cloudu je samostatn\u00e1 firma, jej\u00ed\u017e IT odd\u011blen\u00ed nastavuje sv\u00e9 bezpe\u010dnostn\u00ed politiky. Nap\u0159\u00edklad administr\u00e1to\u0159i ur\u010duj\u00ed pravidla skenov\u00e1n\u00ed a rozvrh antivirov\u00fdch kontrol. Odpov\u00eddaj\u00edc\u00edm zp\u016fsobem mus\u00ed m\u00edt ka\u017ed\u00e1 organizace sv\u00e9 \u0159\u00eddic\u00ed centrum pro nastavov\u00e1n\u00ed antivirov\u00fdch politik. P\u0159itom zadan\u00e9 nastaven\u00ed nesm\u00ed ovlivnit ostatn\u00ed klienty cloudu a poskytovatel by m\u011bl m\u00edt mo\u017enost ujistit se, \u017ee nap\u0159\u00edklad aktualizace antiviru prob\u00edhaj\u00ed v norm\u00e1ln\u00edm re\u017eimu pro v\u0161echny virtu\u00e1ln\u00ed stroje klienta. <\/p>\n

Organizace fakturace a licencov\u00e1n\u00ed.<\/b> Cloudov\u00fd model se vyzna\u010duje flexibilitou a p\u0159edpokl\u00e1d\u00e1 pln\u011bn\u00ed pouze za objem IT zdroj\u016f, kter\u00e9 klient skute\u010dn\u011b pou\u017eil. Pokud je pot\u0159eba, nap\u0159\u00edklad s ohledem na sez\u00f3nn\u00ed faktory, je mo\u017en\u00e9 objem zdroj\u016f operativn\u011b zvy\u0161ovat nebo sni\u017eovat \u2014 v\u0161e na z\u00e1klad\u011b aktu\u00e1ln\u00edch po\u017eadavk\u016f na v\u00fdpo\u010detn\u00ed v\u00fdkon. Tradi\u010dn\u00ed antivir nen\u00ed tak flexibiln\u00ed \u2014 obvykle si klient kupuje licenci na rok na p\u0159edem ur\u010den\u00fd po\u010det. servery<\/a> nebo pracovn\u00edch stanic. U\u017eivatel\u00e9 cloudu pravideln\u011b odpojuj\u00ed a p\u0159ipojuj\u00ed dal\u0161\u00ed virtu\u00e1ln\u00ed stroje v z\u00e1vislosti na sv\u00fdch aktu\u00e1ln\u00edch pot\u0159eb\u00e1ch \u2014 t\u00edm p\u00e1dem by licencov\u00e1n\u00ed antiviru m\u011blo podporovat stejn\u00fd model. <\/p>\n

Druhou ot\u00e1zkou je, na co p\u0159esn\u011b se licence vztahuje. Tradi\u010dn\u00ed antivirus je licencov\u00e1n podle po\u010dtu server\u016f nebo pracovn\u00edch stanic. Licence podle po\u010dtu chr\u00e1n\u011bn\u00fdch virtu\u00e1ln\u00edch stroj\u016f nejsou zcela vhodn\u00e9 v r\u00e1mci cloudov\u00e9ho modelu. Klient m\u016f\u017ee z dostupn\u00fdch zdroj\u016f vytvo\u0159it libovoln\u00fd po\u010det virtu\u00e1ln\u00edch stroj\u016f, nap\u0159\u00edklad p\u011bt nebo deset stroj\u016f. Toto \u010d\u00edslo v\u011bt\u0161iny klient\u016f nen\u00ed st\u00e1l\u00e9, sledovat jeho zm\u011bnu pro n\u00e1s jako poskytovatele nen\u00ed mo\u017en\u00e9. Licencov\u00e1n\u00ed podle CPU nen\u00ed technicky mo\u017en\u00e9: klienti dost\u00e1vaj\u00ed virtu\u00e1ln\u00ed procesory (vCPU), na kter\u00e9 by m\u011blo prob\u00edhat licencov\u00e1n\u00ed. Nov\u00fd model antivirov\u00e9 ochrany by proto m\u011bl p\u0159edpokl\u00e1dat mo\u017enost ur\u010den\u00ed pot\u0159ebn\u00e9ho po\u010dtu vCPU, za kter\u00e9 klient z\u00edsk\u00e1 antivirov\u00e9 licence. <\/p>\n

Soulad s legislativou.<\/b> D\u016fle\u017eit\u00fd bod, proto\u017ee pou\u017eit\u00e1 \u0159e\u0161en\u00ed mus\u00ed zaji\u0161\u0165ovat spln\u011bn\u00ed po\u017eadavk\u016f regul\u00e1tora. Nap\u0159\u00edklad \u010dasto \u201eobyvatel\u00e9\u201c cloudu pracuj\u00ed s osobn\u00edmi \u00fadaji. V takov\u00e9m p\u0159\u00edpad\u011b by m\u011bl poskytovatel disponovat odd\u011blen\u00fdm certifikovan\u00fdm segmentem cloudu, kter\u00fd pln\u011b vyhovuje po\u017eadavk\u016fm z\u00e1kona \u201eO osobn\u00edch \u00fadaj\u00edch\u201c. Pot\u00e9 spole\u010dnosti nemus\u00ed samostatn\u011b \u201estav\u00ed\u201c cel\u00fd syst\u00e9m pro pr\u00e1ci s osobn\u00edmi \u00fadaji: nakupovat certifikovan\u00e9 vybaven\u00ed, p\u0159ipojovat ho a nastavovat, podstupovat certifikaci. Pro kybernetickou ochranu ISPDn t\u011bchto klient\u016f by tak\u00e9 m\u011bl antivirus spl\u0148ovat po\u017eadavky rusk\u00e9 legislativy a m\u00edt certifik\u00e1t FSTEK.<\/p>\n

Prozkoumali jsme povinn\u00e1 krit\u00e9ria, kter\u00e1 by m\u011bla spl\u0148ovat antivirov\u00e1 ochrana ve ve\u0159ejn\u00e9m cloudu. D\u00e1le se pod\u011bl\u00edme o vlastn\u00ed zku\u0161enosti s p\u0159izp\u016fsoben\u00edm antivirov\u00e9ho \u0159e\u0161en\u00ed pro pr\u00e1ci v cloudu poskytovatele. <\/p>\n

Jak lze spojit antivirus a cloud?<\/h2>\n

\nNa z\u00e1klad\u011b na\u0161\u00ed zku\u0161enosti plat\u00ed, \u017ee vybrat \u0159e\u0161en\u00ed podle popisu a dokumentace je jedna v\u011bc, ale implementovat ho v ji\u017e funguj\u00edc\u00edm cloudov\u00e9m prost\u0159ed\u00ed je \u00fakol mnohem slo\u017eit\u011bj\u0161\u00ed. Poj\u010fme si \u0159\u00edct, co jsme d\u011blali v praxi a jak jsme p\u0159izp\u016fsobili antivirus pro pr\u00e1ci v ve\u0159ejn\u00e9m cloudu poskytovatele. Dodavatelem antivirov\u00e9ho \u0159e\u0161en\u00ed se stal Kaspersky, jeho\u017e portfolio zahrnuje \u0159e\u0161en\u00ed pro antivirovou ochranu v cloudov\u00fdch prost\u0159ed\u00edch. Zvolili jsme 'Kaspersky Security pro virtu\u00e1ln\u00ed prost\u0159ed\u00ed' (Lehk\u00fd agent). <\/p>\n

To zahrnuje jednotnou konzoli Kaspersky Security Center. Lehk\u00fd agent a bezpe\u010dnostn\u00ed virtu\u00e1ln\u00ed stroje (SVM, Security Virtual Machine) a server integrace KSC. <\/p>\n

Pot\u00e9, co jsme prozkoumali architekturu \u0159e\u0161en\u00ed Kaspersky a provedli prvn\u00ed testy spole\u010dn\u011b s in\u017een\u00fdry dodavatele, nastala ot\u00e1zka integrace slu\u017eby do cloudu. Prvn\u00ed nasazen\u00ed bylo provedeno spole\u010dn\u00fdmi silami na moskevsk\u00e9 platform\u011b cloudu. A zde je to, co jsme pochopili. <\/p>\n

Abychom minimalizovali s\u00ed\u0165ov\u00fd provoz, bylo rozhodnuto um\u00edstit SVM na ka\u017ed\u00fd ESXi host a 'p\u0159ipojit' SVM k ESXi host\u016fm. V takov\u00e9m p\u0159\u00edpad\u011b se lehk\u00e9 agenti chr\u00e1n\u011bn\u00fdch virtu\u00e1ln\u00edch stroj\u016f obracej\u00ed na SVM pr\u00e1v\u011b toho ESXi hosta, na kter\u00e9m jsou spu\u0161t\u011bny. Pro hlavn\u00ed KSC byl zvolen samostatn\u00fd administrativn\u00ed tenant. V\u00fdsledkem je, \u017ee pod\u0159\u00edzen\u00e9 KSC se nach\u00e1z\u00ed v tenantech ka\u017ed\u00e9ho jednotliv\u00e9ho klienta a obrac\u00ed se na nad\u0159azen\u00fd KSC, um\u00edst\u011bn\u00fd v segmentu spr\u00e1vy. Tento model umo\u017e\u0148uje rychle \u0159e\u0161it probl\u00e9my, kter\u00e9 vznikaj\u00ed v tenantech klient\u016f. <\/p>\n

Krom\u011b ot\u00e1zek t\u00fdkaj\u00edc\u00edch se nasazen\u00ed samotn\u00fdch komponent antivirov\u00e9ho \u0159e\u0161en\u00ed jsme \u010delili \u00fakolu organizace s\u00ed\u0165ov\u00e9 komunikace prost\u0159ednictv\u00edm vytv\u00e1\u0159en\u00ed dal\u0161\u00edch VxLAN. A\u010dkoli bylo \u0159e\u0161en\u00ed p\u016fvodn\u011b ur\u010deno pro enterprise klienty s priv\u00e1tn\u00edmi cloudu \u2014 d\u00edky in\u017een\u00fdrsk\u00e9 vynal\u00e9zavosti a technologick\u00e9 flexibilit\u011b NSX Edge se n\u00e1m poda\u0159ilo vy\u0159e\u0161it v\u0161echny \u00fakoly spojen\u00e9 se segmentac\u00ed tenant\u016f a licencov\u00e1n\u00edm. <\/p>\n

\u00dazce jsme spolupracovali s in\u017een\u00fdry spole\u010dnosti Kaspersky. B\u011bhem anal\u00fdzy architektury \u0159e\u0161en\u00ed v oblasti s\u00ed\u0165ov\u00e9 interakce mezi komponenty syst\u00e9mu jsme zjistili, \u017ee krom\u011b p\u0159\u00edstupu lehk\u00fdch agent\u016f k SVM je tak\u00e9 nezbytn\u00e1 zp\u011btn\u00e1 vazba \u2013 z SVM k lehk\u00fdm agent\u016fm. Tato s\u00ed\u0165ov\u00e1 prov\u00e1zanost je v multitenantn\u00edm prost\u0159ed\u00ed nemo\u017en\u00e1 kv\u016fli mo\u017enosti existence identick\u00fdch s\u00ed\u0165ov\u00fdch nastaven\u00ed virtu\u00e1ln\u00edch stroj\u016f v r\u016fzn\u00fdch tenantech cloudu. Proto byl na na\u0161i \u017e\u00e1dost mechanismus s\u00ed\u0165ov\u00e9 interakce mezi lehk\u00fdm agentem a SVM p\u0159epracov\u00e1n tak, aby se vylou\u010dila pot\u0159eba s\u00ed\u0165ov\u00e9 prov\u00e1zanosti z SVM k lehk\u00fdm agent\u016fm.<\/p>\n

Po rozlo\u017een\u00ed a testov\u00e1n\u00ed \u0159e\u0161en\u00ed na moskevsk\u00e9 cloudov\u00e9 platform\u011b jsme jej zkop\u00edrovali na dal\u0161\u00ed platformy, v\u010detn\u011b certifikovan\u00e9ho segmentu cloudu. Nyn\u00ed je slu\u017eba dostupn\u00e1 ve v\u0161ech regionech zem\u011b. <\/p>\n

Architektura \u0159e\u0161en\u00ed kybernetick\u00e9 bezpe\u010dnosti v r\u00e1mci nov\u00e9ho p\u0159\u00edstupu<\/h2>\n

\nObecn\u00fd sch\u00e9ma fungov\u00e1n\u00ed antivirov\u00e9ho \u0159e\u0161en\u00ed v ve\u0159ejn\u00e9m cloudov\u00e9m prost\u0159ed\u00ed vypad\u00e1 takto:<\/p>\n

\"Pro\u010d
\nSch\u00e9ma fungov\u00e1n\u00ed antivirov\u00e9ho \u0159e\u0161en\u00ed v ve\u0159ejn\u00e9m cloudov\u00e9m prost\u0159ed\u00ed #CloudMTS<\/i><\/p>\n

Pop\u00ed\u0161eme zvl\u00e1\u0161tnosti fungov\u00e1n\u00ed jednotliv\u00fdch komponent \u0159e\u0161en\u00ed v cloudu: <\/p>\n

\u2022 Jedin\u00e1 konzole, kter\u00e1 umo\u017e\u0148uje klient\u016fm centr\u00e1ln\u011b spravovat ochrann\u00fd syst\u00e9m: spou\u0161t\u011bt kontroly, sledovat aktualizace a pozorovat karant\u00e9nn\u00ed z\u00f3ny. Existuje mo\u017enost nastavovat individu\u00e1ln\u00ed bezpe\u010dnostn\u00ed politiky v r\u00e1mci sv\u00e9ho segmentu. <\/p>\n

Je t\u0159eba poznamenat, \u017ee i kdy\u017e jsme poskytovatelem slu\u017eby, nezasahujeme do nastaven\u00ed proveden\u00fdch klienty. To jedin\u00e9, co m\u016f\u017eeme ud\u011blat, je resetovat bezpe\u010dnostn\u00ed politiky na v\u00fdchoz\u00ed, pokud je pot\u0159eba p\u0159eprogramovat. Nap\u0159\u00edklad to m\u016f\u017ee b\u00fdt nutn\u00e9, pokud klient n\u00e1hodou tyto politiky zp\u0159\u00edsnil nebo v\u00fdrazn\u011b uvolnil. Spole\u010dnost v\u017edy m\u016f\u017ee z\u00edskat \u0159\u00eddic\u00ed centrum s v\u00fdchoz\u00edmi politikami, kter\u00e9 m\u016f\u017ee pot\u00e9 samostatn\u011b p\u0159izp\u016fsobit. Nev\u00fdhodou Kaspersky Security Center je, \u017ee zat\u00edm je platforma dostupn\u00e1 pouze pro opera\u010dn\u00ed syst\u00e9m Microsoft. A\u010dkoli lehk\u00e9 agenty mohou fungovat jak na Windows, tak na Linuxov\u00fdch stroj\u00edch. Nicm\u00e9n\u011b v \u201eLaborato\u0159\u00edch Kaspersky\u201c slibuj\u00ed, \u017ee u\u017e v bl\u00edzk\u00e9 dob\u011b bude KSC fungovat i pod opera\u010dn\u00edm syst\u00e9mem Linux. Jedna z d\u016fle\u017eit\u00fdch funkc\u00ed KSC je mo\u017enost spr\u00e1vy karant\u00e9ny. Ka\u017ed\u00e1 spole\u010dnost-klient v na\u0161em cloudu m\u00e1 vlastn\u00ed karant\u00e9nu. Tento p\u0159\u00edstup vylu\u010duje situace, kdy by infikovan\u00fd dokument n\u00e1hodn\u011b unikl na ve\u0159ejnost, jak by to mohlo nastat v p\u0159\u00edpad\u011b klasick\u00e9ho firemn\u00edho antiviru s centr\u00e1ln\u00ed karant\u00e9nou.<\/p>\n

\u2022 Lehk\u00e9 agenty. V r\u00e1mci nov\u00e9ho modelu je na ka\u017edou virtu\u00e1ln\u00ed stroj instalov\u00e1n lehk\u00fd agent Kaspersky Security. To umo\u017e\u0148uje neukl\u00e1dat antivirovou datab\u00e1zi na ka\u017ed\u00e9m VM, co\u017e sni\u017euje objem zabran\u00e9ho diskov\u00e9ho prostoru. Slu\u017eba je integrov\u00e1na se cloudovou infrastrukturou a pracuje prost\u0159ednictv\u00edm SVM, co\u017e zvy\u0161uje hustotu virtu\u00e1ln\u00edch stroj\u016f na ESXi hostiteli a v\u00fdkon cel\u00e9ho cloudov\u00e9ho syst\u00e9mu. Lehk\u00e9 agenti vytv\u00e1\u0159ej\u00ed frontu \u00fakol\u016f pro ka\u017ed\u00fd virtu\u00e1ln\u00ed stroj: prov\u011b\u0159it souborov\u00fd syst\u00e9m, pam\u011b\u0165 atd. Ale za prov\u00e1d\u011bn\u00ed t\u011bchto operac\u00ed u\u017e odpov\u00edd\u00e1 SVM, o kter\u00e9 si pov\u00edme d\u00e1le. Tak\u00e9 agent vykon\u00e1v\u00e1 funkce firewallu, kontroluje bezpe\u010dnostn\u00ed politiky, pos\u00edl\u00e1 infikovan\u00e9 soubory do karant\u00e9ny a monitoruje celkov\u00e9 \u201ezdrav\u00ed\u201c opera\u010dn\u00edho syst\u00e9mu, na kter\u00e9m je nainstalov\u00e1n. V\u0161e t\u00edmto lze spravovat pomoc\u00ed ji\u017e zm\u00edn\u011bn\u00e9 jednotn\u00e9 konzole. <\/p>\n

\u2022 Bezpe\u010dnostn\u00ed virtu\u00e1ln\u00ed stroj. V\u0161echny zdroje n\u00e1ro\u010dn\u00e9 \u00fakoly (aktualizace antivirov\u00fdch datab\u00e1z\u00ed, prov\u00e1d\u011bn\u00ed pl\u00e1novan\u00fdch kontrol) zaji\u0161\u0165uje samostatn\u00fd Bezpe\u010dnostn\u00ed virtu\u00e1ln\u00ed stroj (SVM). Ten je zodpov\u011bdn\u00fd za provoz plnohodnotn\u00e9ho antivirov\u00e9ho motoru a jeho datab\u00e1z\u00ed. IT infrastruktura spole\u010dnosti m\u016f\u017ee zahrnovat n\u011bkolik SVM. Tento p\u0159\u00edstup zvy\u0161uje spolehlivost syst\u00e9mu \u2014 pokud n\u011bjak\u00fd stroj sel\u017ee a neodpov\u00edd\u00e1 po dobu t\u0159iceti sekund, agenti automaticky za\u010dnou vyhled\u00e1vat jin\u00fd. <\/p>\n

\u2022 Server integrace KSC. Jedna z komponent hlavn\u00edho KSC, kter\u00e1 p\u0159id\u011bluje podle v jeho nastaven\u00ed zadan\u00e9ho algoritmu lehk\u00fdm agent\u016fm sv\u00e9 SVM, a tak\u00e9 kontroluje dostupnost SVM. T\u00edmto zp\u016fsobem tento softwarov\u00fd modul zaji\u0161\u0165uje vyv\u00e1\u017een\u00ed z\u00e1t\u011b\u017ee na v\u0161ech SVM cloudov\u00e9 infrastruktury. <\/p>\n

Algoritmus pr\u00e1ce v cloudu: sn\u00ed\u017een\u00ed z\u00e1t\u011b\u017ee na infrastrukturu <\/h2>\n

\nCelkov\u011b lze algoritmus fungov\u00e1n\u00ed antiviru p\u0159edstavit n\u00e1sledovn\u011b. Agent se obrac\u00ed na soubor na virtu\u00e1ln\u00edm stroji a kontroluje ho. V\u00fdsledek kontroly se ukl\u00e1d\u00e1 do spole\u010dn\u00e9 centralizovan\u00e9 datab\u00e1ze verdikt\u016f SVM (ta se naz\u00fdv\u00e1 Shared Cache), p\u0159i\u010dem\u017e ka\u017ed\u00e1 polo\u017eka v t\u00e9to datab\u00e1zi identifikuje jedine\u010dn\u00fd vzorek souboru. Tento p\u0159\u00edstup umo\u017e\u0148uje sledovat, aby stejn\u00fd soubor nebyl kontrolov\u00e1n n\u011bkolikr\u00e1t po sob\u011b (nap\u0159\u00edklad, pokud ho otev\u0159eli na r\u016fzn\u00fdch virtu\u00e1ln\u00edch stroj\u00edch). Soubor se znovu skenuje pouze v p\u0159\u00edpad\u011b, \u017ee do n\u011bj byly provedeny zm\u011bny nebo byla kontrola spu\u0161t\u011bna ru\u010dn\u011b.<\/p>\n

\"Pro\u010d
\nRealizace antivirov\u00e9ho \u0159e\u0161en\u00ed v cloudu poskytovatele<\/i><\/p>\n

Na obr\u00e1zku je zn\u00e1zorn\u011bn celkov\u00fd sch\u00e9ma implementace \u0159e\u0161en\u00ed v cloudu. V \u0159\u00eddic\u00ed z\u00f3n\u011b cloudu je nasazen hlavn\u00ed Kaspersky Security Center a na ka\u017ed\u00e9m ESXi hostiteli je pomoc\u00ed integra\u010dn\u00edho serveru KSC nasazena individu\u00e1ln\u00ed SVM (ka\u017ed\u00e9 ESXi hostiteli je zvl\u00e1\u0161tn\u00edmi nastaven\u00edmi na VMware vCenter Server p\u0159i\u0159azena vlastn\u00ed SVM). Klienti pracuj\u00ed ve sv\u00fdch segmentech cloudu, kde jsou um\u00edst\u011bny virtu\u00e1ln\u00ed stroje s agenty. Tyto po\u0159izuj\u00ed prost\u0159ednictv\u00edm individu\u00e1ln\u00edch KSC server\u016f, kter\u00e9 podl\u00e9haj\u00ed hlavn\u00edmu KSC. V p\u0159\u00edpad\u011b pot\u0159eby ochrany mal\u00e9ho po\u010dtu virtu\u00e1ln\u00edch stroj\u016f (do 5) m\u016f\u017ee b\u00fdt klientovi poskytnut p\u0159\u00edstup k virtu\u00e1ln\u00ed konzoli specializovan\u00e9ho dedikovan\u00e9ho serveru KSC. S\u00ed\u0165ov\u00e1 interakce mezi klientsk\u00fdmi KSC a hlavn\u00edm KSC, stejn\u011b jako mezi lehk\u00fdmi agenty a SVM, prob\u00edh\u00e1 pomoc\u00ed NAT p\u0159es klientsk\u00e9 virtu\u00e1ln\u00ed sm\u011brova\u010de EdgeGW.<\/p>\n

Podle na\u0161ich odhad\u016f a v\u00fdsledk\u016f test\u016f koleg\u016f u dodavatele, Lehk\u00e9 agenty sni\u017euj\u00ed z\u00e1t\u011b\u017e na virtu\u00e1ln\u00ed infrastruktu\u0159e klient\u016f p\u0159ibli\u017en\u011b o 25 % (ve srovn\u00e1n\u00ed se syst\u00e9mem, kter\u00fd pou\u017e\u00edv\u00e1 tradi\u010dn\u00ed antivirus). Konkr\u00e9tn\u011b standardn\u00ed antivirus Kaspersky Endpoint Security (KES) pro fyzick\u00e1 prost\u0159ed\u00ed spot\u0159ebov\u00e1v\u00e1 t\u00e9m\u011b\u0159 dvakr\u00e1t v\u00edce procesorov\u00e9ho \u010dasu serveru (2,95 %) ne\u017e \u0159e\u0161en\u00ed pro virtualizaci zalo\u017een\u00e9 na lehk\u00fdch agentech (1,67 %).<\/p>\n

\"Pro\u010d
\nGraf porovn\u00e1n\u00ed z\u00e1t\u011b\u017ee na procesor
\n<\/i>
\nPodobn\u00e1 situace se projevuje u frekvence zapisov\u00e1n\u00ed na disk: pro klasick\u00fd antivirus je 1011 IOPS, pro cloudov\u00fd antivirus \u2014 671 IOPS.<\/p>\n

\"Pro\u010d
\nGraf porovn\u00e1n\u00ed frekvence p\u0159\u00edstupu na disk
\n<\/i>
\nZisk v v\u00fdkonu umo\u017e\u0148uje udr\u017eovat stabilitu infrastruktury a efektivn\u011bji vyu\u017e\u00edvat v\u00fdpo\u010detn\u00ed zdroje. D\u00edky adaptaci pro pr\u00e1ci v ve\u0159ejn\u00e9m cloudov\u00e9m prost\u0159ed\u00ed \u0159e\u0161en\u00ed nesni\u017euje v\u00fdkon cloudu: prov\u00e1d\u00ed centralizovan\u00e9 kontroly soubor\u016f a stahov\u00e1n\u00ed aktualizac\u00ed, \u010d\u00edm\u017e rozd\u011bluje z\u00e1t\u011b\u017e. To znamen\u00e1, \u017ee na jedn\u00e9 stran\u011b nebudou p\u0159ehl\u00e9dnuty aktu\u00e1ln\u00ed hrozby pro cloudovou infrastrukturu, na druh\u00e9 stran\u011b se pr\u016fm\u011brn\u011b o 25 % sn\u00ed\u017e\u00ed po\u017eadavky na zdroje virtu\u00e1ln\u00edch stroj\u016f ve srovn\u00e1n\u00ed s tradi\u010dn\u00edm antivirem.<\/p>\n

Funk\u010dn\u011b si ob\u011b \u0159e\u0161en\u00ed velmi p\u0159ipom\u00ednaj\u00ed: n\u00ed\u017ee je uvedena srovn\u00e1vac\u00ed tabulka. Ve cloudu je v\u0161ak, jak ukazuj\u00ed v\u00fd\u0161e uveden\u00e9 testovac\u00ed v\u00fdsledky, optim\u00e1ln\u011bj\u0161\u00ed pou\u017e\u00edt \u0159e\u0161en\u00ed pro virtu\u00e1ln\u00ed prost\u0159ed\u00ed. <\/p>\n

\"Pro\u010d
\n
\nO tarifaci v r\u00e1mci nov\u00e9ho p\u0159\u00edstupu.<\/b> Rozhodli jsme se vyu\u017e\u00edt model, kter\u00fd umo\u017e\u0148uje z\u00edsk\u00e1vat licence podle po\u010dtu vCPU. To znamen\u00e1, \u017ee po\u010det licenc\u00ed bude odpov\u00eddat po\u010dtu vCPU. Antivir m\u016f\u017eete otestovat t\u00edm, \u017ee pod\u00e1te \u017e\u00e1dost. na webu<\/a><\/noindex>. <\/p>\n

V dal\u0161\u00edm materi\u00e1lu o cloudov\u00e9m t\u00e9matu se pod\u00edv\u00e1me na evoluci cloudov\u00fdch WAF a na to, co je lep\u0161\u00ed zvolit: hardware, software nebo cloud. <\/p>\n

Text p\u0159ipravili zam\u011bstnanci cloudov\u00e9ho poskytovatele #CloudMTS: Denis Mjagkov, hlavn\u00ed architekt a Alexej Afanasjev, mana\u017eer pro rozvoj produkt\u016f v oblasti kybernetick\u00e9 bezpe\u010dnosti. <\/i><\/p>\n

Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0412\u0441\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u044b\u0432\u043e\u0434\u044f\u0442 \u0432 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u0432\u0441\u044e \u0441\u0432\u043e\u044e \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443. \u041e\u0434\u043d\u0430\u043a\u043e \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0430\u043d\u0442\u0438\u0432\u0438\u0440\u0443\u0441\u043d\u043e\u0433\u043e \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0432 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0435 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u0430 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u044e\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u043a\u0438\u0431\u0435\u0440-\u0440\u0438\u0441\u043a\u0438. \u041f\u0440\u0430\u043a\u0442\u0438\u043a\u0430 \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442, \u0447\u0442\u043e \u0434\u043e 80% \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445 \u0432\u0438\u0440\u0443\u0441\u043e\u0432 \u043e\u0442\u043b\u0438\u0447\u043d\u043e \u0436\u0438\u0432\u0443\u0442 \u0432 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u0441\u0440\u0435\u0434\u0435. \u0412 \u044d\u0442\u043e\u043c \u043f\u043e\u0441\u0442\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u043c \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u0437\u0430\u0449\u0438\u0442\u0438\u0442\u044c \u0418\u0422-\u0440\u0435\u0441\u0443\u0440\u0441\u044b \u0432 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u043c \u043e\u0431\u043b\u0430\u043a\u0435 \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u0442\u0440\u0430\u0434\u0438\u0446\u0438\u043e\u043d\u043d\u044b\u0435 \u0430\u043d\u0442\u0438\u0432\u0438\u0440\u0443\u0441\u044b \u043d\u0435 \u0441\u043e\u0432\u0441\u0435\u043c \u043f\u043e\u0434\u0445\u043e\u0434\u044f\u0442 \u0434\u043b\u044f \u044d\u0442\u0438\u0445 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":39335,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39334","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\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\udd47Pro\u010d tradi\u010dn\u00ed antiviry nejsou vhodn\u00e9 pro ve\u0159ejn\u00e9 cloudy. A co s t\u00edm d\u011blat? | ProHoster","description":"\u010c\u00edm d\u00e1l v\u00edce u\u017eivatel\u016f p\u0159esouv\u00e1 celou svou IT infrastrukturu do ve\u0159ejn\u00e9ho cloudu. Pokud v\u0161ak v infrastruktu\u0159e z\u00e1kazn\u00edka chyb\u00ed antivirov\u00e1 kontrola, mohou vzniknout v\u00e1\u017en\u00e9 kybernetick\u00e9 rizika.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\u041f\u043e\u0447\u0435\u043c\u0443 \u0442\u0440\u0430\u0434\u0438\u0446\u0438\u043e\u043d\u043d\u044b\u0435 \u0430\u043d\u0442\u0438\u0432\u0438\u0440\u0443\u0441\u044b \u043d\u0435 \u043f\u043e\u0434\u0445\u043e\u0434\u044f\u0442 \u0434\u043b\u044f \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0445 \u043e\u0431\u043b\u0430\u043a\u043e\u0432. \u0418 \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0442\u044c? | ProHoster","og:description":"\u0412\u0441\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0432\u044b\u0432\u043e\u0434\u044f\u0442 \u0432 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u0432\u0441\u044e \u0441\u0432\u043e\u044e \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443. \u041e\u0434\u043d\u0430\u043a\u043e \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0430\u043d\u0442\u0438\u0432\u0438\u0440\u0443\u0441\u043d\u043e\u0433\u043e \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0432 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0435 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u0430 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u044e\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u043a\u0438\u0431\u0435\u0440-\u0440\u0438\u0441\u043a\u0438.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat","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-31T19:30:19+00:00","article:modified_time":"2019-10-31T19:30:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39334","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-02-09 18:02:23","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:51:28","updated":"2026-02-09 18:02:23","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/39334","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=39334"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/39334\/revisions"}],"predecessor-version":[{"id":158518,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/39334\/revisions\/158518"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/39335"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=39334"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=39334"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=39334"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}