{"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\/sq\/blog\/administrirovanie\/pochemu-traditsionnye-antivirusy-ne-podhodyat-dlya-publichnyh-oblakov-i-chto-delat","title":{"rendered":"Pse antivirus\u00ebt tradicional\u00eb nuk jan\u00eb t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr cloud-in publik. \u00c7far\u00eb duhet b\u00ebr\u00eb?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Po duket se gjithnj\u00eb e m\u00eb shum\u00eb p\u00ebrdorues po transferojn\u00eb t\u00eb gjith\u00eb infrastruktura e tyre IT n\u00eb nj\u00eb sistem cloud publik. Megjithat\u00eb, n\u00eb rast se kontrolli antivirus n\u00eb infrastruktur\u00ebn e klientit \u00ebsht\u00eb i pamjaftuesh\u00ebm, lindin rreziqe serioze kibernetike. Praktika tregon se deri n\u00eb 80% e viruseve ekzistuese ndihen rehat n\u00eb ambientin virtual. N\u00eb k\u00ebt\u00eb postim do t\u00eb flasim p\u00ebr m\u00ebnyrat si t\u00eb mbrojm\u00eb burimet IT n\u00eb cloud publik dhe pse antivirus\u00ebt tradicional\u00eb nuk jan\u00eb t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr k\u00ebto q\u00ebllime. <\/b><\/p>\n

\"Pse
\n
\nP\u00ebr t\u00eb filluar, le t\u00eb flasim p\u00ebr m\u00ebnyr\u00ebn se si arrit\u00ebm n\u00eb p\u00ebrfundimin se mjetet e zakonshme t\u00eb mbrojtjes antivirus p\u00ebr cloud publik nuk jan\u00eb t\u00eb p\u00ebrshtatshme dhe se k\u00ebrkohen qasje t\u00eb tjera p\u00ebr mbrojtjen e burimeve. <\/a><\/noindex><\/p>\n

S\u00eb pari, zakonisht ofruesit sigurojn\u00eb masat e nevojshme p\u00ebr t\u00eb garantuar mbrojtjen e lart\u00eb t\u00eb platformave t\u00eb tyre cloud. P\u00ebr shembull, ne n\u00eb #CloudMTS analizojm\u00eb t\u00eb gjith\u00eb trafikun rrjet, monitorojm\u00eb log-et e sistemeve t\u00eb siguris\u00eb s\u00eb cloud-it ton\u00eb, dhe kryejm\u00eb rregullisht teste penetrimi. Segmentet e cloud-it q\u00eb i jan\u00eb dh\u00ebn\u00eb klient\u00ebve individualisht gjithashtu duhet t\u00eb jen\u00eb t\u00eb mbrojtura n\u00eb m\u00ebnyr\u00eb t\u00eb besueshme. <\/p>\n

S\u00eb dyti, varianti klasik i luft\u00ebs ndaj rreziqeve kibernetike parashikon instalimin e antivirus\u00ebve dhe mjeteve t\u00eb menaxhimit t\u00eb tyre n\u00eb \u00e7do makin\u00eb virtuale. Megjithat\u00eb, n\u00ebse ka num\u00ebr t\u00eb madh makinash virtuale, nj\u00eb praktik\u00eb e till\u00eb mund t\u00eb jet\u00eb e pafavorshme dhe t\u00eb k\u00ebrkoj\u00eb burime t\u00eb konsiderueshme llogarit\u00ebse, duke ngarkuar k\u00ebshtu m\u00eb tej infrastruktur\u00ebn e klientit dhe duke ulur performanc\u00ebn e p\u00ebrgjithshme t\u00eb cloud-it. Kjo u b\u00eb premisa kryesore p\u00ebr k\u00ebrkimin e qasjeve t\u00eb reja p\u00ebr nd\u00ebrtimin e mbrojtjes efektive antivirus p\u00ebr makinat virtuale t\u00eb klient\u00ebve. <\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, shumica e zgjidhjeve antivirus q\u00eb gjenden n\u00eb treg nuk jan\u00eb t\u00eb adaptuara p\u00ebr t\u00eb zgjidhur problemet e mbrojtjes s\u00eb burimeve IT n\u00eb nj\u00eb ambient cloud publik. N\u00eb p\u00ebrgjith\u00ebsi, ato jan\u00eb zgjidhje EPP (Platforma e Mbrojtjes n\u00eb Pik\u00eb) t\u00eb r\u00ebnda, t\u00eb cilat, p\u00ebr m\u00eb tep\u00ebr, nuk ofrojn\u00eb mund\u00ebsin\u00eb e personalizimit t\u00eb nevojsh\u00ebm n\u00eb an\u00ebn e klient\u00ebve t\u00eb ofruesve t\u00eb cloud-it. <\/p>\n

B\u00ebhet e qart\u00eb se zgjidhjet tradicionale antivirus jan\u00eb t\u00eb pap\u00ebrshtatshme p\u00ebr pun\u00eb n\u00eb cloud, pasi ato ngarkojn\u00eb seriozisht infrastruktur\u00ebn virtuale gjat\u00eb p\u00ebrdit\u00ebsimeve dhe skanimeve, gjithashtu nuk kan\u00eb nivelet e nevojshme t\u00eb menaxhimit t\u00eb rolit dhe konfigurimeve. M\u00eb pas do t\u00eb shqyrtojm\u00eb n\u00eb detaje arsyet se pse cloud-i ka nevoj\u00eb p\u00ebr qasje t\u00eb reja p\u00ebr mbrojtjen antivirus. <\/p>\n

\u00c7far\u00eb duhet t\u00eb dij\u00eb nj\u00eb antivirus n\u00eb cloud publik <\/h2>\n

\nPra, le t\u00eb shikojm\u00eb specifikat e funksionimit n\u00eb nj\u00eb mjedis virtual: <\/p>\n

Efektiviteti i p\u00ebrdit\u00ebsimeve dhe kontrollit masiv sipas nj\u00eb programi.<\/b> N\u00ebse nj\u00eb num\u00ebr i konsideruesh\u00ebm makinash virtuale q\u00eb p\u00ebrdorin antivirus tradicional aktivizojn\u00eb p\u00ebrdit\u00ebsimin nj\u00ebkoh\u00ebsisht, n\u00eb cloud do t\u00eb ndodhi nj\u00eb \"stuhi\" p\u00ebrdit\u00ebsimesh. Kapacitetet e hostit ESXi, n\u00eb t\u00eb cilin jan\u00eb vendosur disa makina virtuale, mund t\u00eb mos mjaftojn\u00eb p\u00ebr t\u00eb p\u00ebrpunuar nj\u00eb fluks t\u00eb till\u00eb detyrash identike, t\u00eb nisura si parazgjedhje. Nga k\u00ebndv\u00ebshtrimi i ofruesit t\u00eb cloud-it, nj\u00eb problem i till\u00eb mund t\u00eb shkaktoj\u00eb ngarkesa shtes\u00eb n\u00eb nj\u00eb s\u00ebr\u00eb hostesh ESXi, q\u00eb n\u00eb p\u00ebrfundim do t\u00eb \u00e7oj\u00eb n\u00eb r\u00ebnie t\u00eb performanc\u00ebs s\u00eb infrastruktur\u00ebs virtuale t\u00eb cloud-it. Kjo mund t\u00eb ndikoj\u00eb, p\u00ebrfshir\u00eb, n\u00eb performanc\u00ebn e makinave virtuale t\u00eb klient\u00ebve t\u00eb tjer\u00eb t\u00eb cloud-it. Nj\u00eb situat\u00eb e ngjashme mund t\u00eb ndodh\u00eb kur fillohet nj\u00eb skanim masiv: p\u00ebrpunimi i nj\u00eb s\u00ebr\u00eb k\u00ebrkesave identike nga p\u00ebrdorues t\u00eb ndrysh\u00ebm do t\u00eb ndikoj\u00eb negativisht n\u00eb performanc\u00ebn e t\u00ebr\u00eb cloud-it. Me nj\u00eb shkall\u00eb t\u00eb madhe t\u00eb siguris\u00eb, ulja e funksionimit t\u00eb SYSK do t\u00eb pasqyrohet te t\u00eb gjith\u00eb klient\u00ebt. Ngarkesat e tilla ekskluzive nuk e g\u00ebzojn\u00eb as ofruesin, as klient\u00ebt e tij, pasi ato ndikojn\u00eb te \"fqinj\u00ebt\" n\u00eb cloud. Nga kjo perspektiv\u00eb, antivirus tradicional mund t\u00eb paraqes\u00eb nj\u00eb problem t\u00eb madh.<\/p>\n

Karanta e sigurt.<\/b> N\u00ebse n\u00eb sistem zbulohen skedar\u00eb ose dokumente, potencialisht t\u00eb infektuar nga virusi, ato d\u00ebrgohen n\u00eb karantin\u00eb. Natyrisht, skedari i infektuar mund t\u00eb fshihet menj\u00ebher\u00eb, por kjo shpesh nuk \u00ebsht\u00eb e pranueshme p\u00ebr shumic\u00ebn e kompanive. Antivirus\u00ebt enterprise p\u00ebr korporata, t\u00eb cil\u00ebt nuk jan\u00eb t\u00eb p\u00ebrshtatur p\u00ebr t\u00eb punuar n\u00eb re t\u00eb ofruesit, zakonisht kan\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt karantine \u2014 n\u00eb t\u00eb hyjn\u00eb t\u00eb gjith\u00eb objektet e infektuara, p\u00ebr shembull, ato t\u00eb zbuluara n\u00eb kompjuter\u00ebt e p\u00ebrdoruesve t\u00eb kompanis\u00eb. Klient\u00ebt e ofruesit t\u00eb re vazhdojn\u00eb t\u00eb 'jetojn\u00eb' n\u00eb segmente t\u00eb tyre (ose tenanta). K\u00ebto segmente jan\u00eb t\u00eb pap\u00ebrshkueshme dhe t\u00eb izoluara: klient\u00ebt nuk e din\u00eb nj\u00ebri-tjetrin dhe, natyrisht, nuk e shohin se \u00e7far\u00eb vendosin n\u00eb re t\u00eb tjer\u00ebt. \u00cbsht\u00eb e qart\u00eb se n\u00eb karantin\u00ebn e p\u00ebrbashk\u00ebt, t\u00eb cil\u00ebn do ta p\u00ebrdorin t\u00eb gjith\u00eb p\u00ebrdoruesit e antivirusit n\u00eb re, potencialisht mund t\u00eb hyj\u00eb nj\u00eb dokument q\u00eb p\u00ebrmban informacion t\u00eb ndjesh\u00ebm ose sekret tregtar. Kjo \u00ebsht\u00eb e papranueshme p\u00ebr ofruesin dhe klient\u00ebt e tij. Prandaj, zgjidhja mund t\u00eb jet\u00eb vet\u00ebm nj\u00eb - karantina personale p\u00ebr \u00e7do klient n\u00eb segmentin e tij, n\u00eb t\u00eb cilin nuk ka akses as ofruesi, as klient\u00ebt e tjer\u00eb. <\/p>\n

Politikat e sigurimit individuale. <\/b>\u00c7do klient n\u00eb re \u00ebsht\u00eb nj\u00eb kompani e ve\u00e7ant\u00eb, departamenti i IT-s\u00eb s\u00eb s\u00eb cil\u00ebs vendos politik\u00ebn e saj t\u00eb sigurimit. P\u00ebr shembull, administrator\u00ebt p\u00ebrcaktojn\u00eb rregullat e skanimit dhe orarin e kontrolleve antivirus. P\u00ebr k\u00ebt\u00eb arsye, \u00e7do organizat\u00eb duhet t\u00eb ket\u00eb qendr\u00ebn e saj t\u00eb menaxhimit p\u00ebr t\u00eb konfiguruar politikat e antivirusit. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, parametrat e vendosur nuk duhet t\u00eb ndikojn\u00eb n\u00eb klient\u00ebt e tjer\u00eb t\u00eb re, nd\u00ebrsa ofruesi duhet t\u00eb ket\u00eb mund\u00ebsin\u00eb t\u00eb sigurohet se, p\u00ebr shembull, p\u00ebrdit\u00ebsimet e antivirusit kalojn\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb rregullt p\u00ebr t\u00eb gjitha makinat virtuale t\u00eb klientit. <\/p>\n

Organizimi i faturimit dhe licencimi.<\/b> Modeli i re karakterizohet nga fleksibiliteti dhe parashikon pages\u00ebn vet\u00ebm p\u00ebr volumet e burimeve IT t\u00eb p\u00ebrdorura nga klienti. N\u00ebse ka nj\u00eb nevoj\u00eb, p\u00ebr shembull, p\u00ebr shkak t\u00eb faktor\u00ebve sezonal\u00eb, volumi i burimeve mund t\u00eb rritet ose ulet menj\u00ebher\u00eb \u2014 t\u00eb gjitha n\u00eb p\u00ebrputhje me nevojat aktuale p\u00ebr fuqin\u00eb llogarit\u00ebse. Antivirus\u00ebt tradicional\u00eb nuk jan\u00eb aq fleksib\u00ebl \u2014 zakonisht, klienti blen nj\u00eb licenc\u00eb p\u00ebr nj\u00eb vit p\u00ebr nj\u00eb num\u00ebr t\u00eb parap\u00ebrcaktuar. server\u00ebsh<\/a> ose q\u00eb p\u00ebrdorin stacione pune. P\u00ebrdoruesit e cloud-it shpesh \u00e7aktivizojn\u00eb dhe aktivizojn\u00eb makina virtuale shtes\u00eb n\u00eb var\u00ebsi t\u00eb nevojave t\u00eb tyre aktuale - p\u00ebr pasoj\u00eb, licencat e antivirusit duhet t\u00eb mb\u00ebshtesin nj\u00eb model t\u00eb till\u00eb. <\/p>\n

Pyetja e dyt\u00eb \u00ebsht\u00eb se \u00e7far\u00eb do t\u00eb mbuloj\u00eb pik\u00ebrisht licenca. Antivirus tradicional licencohet sipas numrit t\u00eb server\u00ebve ose stacioneve t\u00eb pun\u00ebs. Licencat sipas numrit t\u00eb makinave virtuale t\u00eb mbrojtura nuk jan\u00eb t\u00ebr\u00ebsisht t\u00eb p\u00ebrshtatshme brenda modelit cloud. Klienti mund t\u00eb krijoj\u00eb \u00e7do num\u00ebr t\u00eb p\u00ebrshtatsh\u00ebm makinash virtuale nga burimet ekzistuese, p\u00ebr shembull, pes\u00eb ose dhjet\u00eb makina. Ky num\u00ebr p\u00ebr shumic\u00ebn e klient\u00ebve nuk \u00ebsht\u00eb i q\u00ebndruesh\u00ebm, dhe ndjekja e ndryshimeve t\u00eb tij p\u00ebr ne si ofrues nuk \u00ebsht\u00eb e mundur. Licenca sipas CPU nuk ka mund\u00ebsi teknike: klient\u00ebt marrin procesor\u00eb virtual\u00eb (vCPU), bazuar n\u00eb t\u00eb cil\u00ebt duhet t\u00eb b\u00ebhet licencimi. Prandaj, modeli i ri i mbrojtjes antivirus duhet t\u00eb parashikoj\u00eb mund\u00ebsin\u00eb p\u00ebr klientin t\u00eb p\u00ebrcaktoj\u00eb numrin e nevojsh\u00ebm t\u00eb vCPU-ve p\u00ebr t\u00eb cilat do t\u00eb marr\u00eb licencat antivirus. <\/p>\n

P\u00ebrputhshm\u00ebria me ligjin.<\/b> Nj\u00eb pik\u00eb e r\u00ebnd\u00ebsishme, pasi zgjidhjet e aplikuara duhet t\u00eb sigurojn\u00eb p\u00ebrmbushjen e k\u00ebrkesave t\u00eb rregullatorit. P\u00ebr shembull, shpesh \"banor\u00ebt\" e cloud-it punojn\u00eb me t\u00eb dh\u00ebna personale. N\u00eb k\u00ebt\u00eb rast, ofruesi duhet t\u00eb ken\u00eb nj\u00eb segment t\u00eb ve\u00e7ant\u00eb t\u00eb cloud-it t\u00eb \u00e7ertifikuar, i cili plot\u00ebson plot\u00ebsisht k\u00ebrkesat e ligjit \"P\u00ebr t\u00eb dh\u00ebnat personale\". K\u00ebshtu, kompanit\u00eb nuk kan\u00eb nevoj\u00eb t\u00eb \"nd\u00ebrtojn\u00eb\" vet\u00eb t\u00eb gjith\u00eb sistemin p\u00ebr t\u00eb punuar me t\u00eb dh\u00ebna personale: t\u00eb blejn\u00eb pajisje t\u00eb \u00e7ertifikuara, t'i lidhin dhe t'i konfigurojn\u00eb, t\u00eb kalojn\u00eb testimin. P\u00ebr mbrojtjen kibernetike t\u00eb ISpD-nj t\u00eb till\u00eb, antivirus gjithashtu duhet t\u00eb p\u00ebrmbush\u00eb k\u00ebrkesat e legjislacionit rus dhe t\u00eb ket\u00eb nj\u00eb certifikat\u00eb FSTEK.<\/p>\n

Ne kemi shqyrtuar kriteret e detyrueshme, t\u00eb cilat duhet t\u00eb p\u00ebrmbush\u00eb mbrojtja antivirus n\u00eb cloud-in publik. M\u00eb pas, do t\u00eb ndajm\u00eb p\u00ebrvoj\u00ebn ton\u00eb n\u00eb adaptimin e zgjidhjes antivirus p\u00ebr pun\u00eb n\u00eb cloud-in e ofruesit. <\/p>\n

Si mund t\u00eb miqt\u00eb antivirusin dhe cloud-in<\/h2>\n

\nSipas p\u00ebrvoj\u00ebs son\u00eb, t\u00eb zgjedh\u00ebsh nj\u00eb zgjidhje t\u00eb bazuar n\u00eb p\u00ebrshkrim dhe dokumentacion \u00ebsht\u00eb nj\u00eb gj\u00eb, por ta realizosh at\u00eb n\u00eb praktik\u00eb n\u00eb nj\u00eb mjedis cloud q\u00eb funksionon, \u00ebsht\u00eb nj\u00eb detyr\u00eb krejt\u00ebsisht ndryshe me nivelin e kompleksitetit. Do t\u00eb tregojm\u00eb se \u00e7far\u00eb kemi b\u00ebr\u00eb n\u00eb praktik\u00eb dhe si e adapotuam antivirusin p\u00ebr t\u00eb punuar n\u00eb nj\u00eb cloud publik t\u00eb ofruesit. Furnizuesi i zgjidhjes antivirus ishte Kaspersky, i cili ka n\u00eb portofol zgjidhje p\u00ebr mbrojtjen antivirus p\u00ebr mjediset cloud. Ne u ndal\u00ebm te 'Kaspersky Security p\u00ebr mjediset virtuale' (Agjenti i Leht\u00eb). <\/p>\n

Ai p\u00ebrfshin nj\u00eb konsol\u00eb t\u00eb vetme Kaspersky Security Center. Agjenti i Leht\u00eb dhe makinat virtuale t\u00eb siguris\u00eb (SVM, Security Virtual Machine) dhe serveri i integrimit KSC. <\/p>\n

Pasi studiojm\u00eb arkitektur\u00ebn e zgjidhjes Kaspersky dhe kryem testet e para s\u00eb bashku me inxhinier\u00ebt e furnizuesit, u p\u00ebrball\u00ebm me pyetjen e integrimit t\u00eb sh\u00ebrbimit n\u00eb cloud. Implementimi i par\u00eb u krye me forcat e p\u00ebrbashk\u00ebta n\u00eb platform\u00ebn cloud t\u00eb Mosk\u00ebs. Dhe ja \u00e7far\u00eb kuptuam. <\/p>\n

P\u00ebr t\u00eb minimizuar trafikun rrjet\u00ebsor, u mor nj\u00eb vendim p\u00ebr t\u00eb vendosur SVM n\u00eb \u00e7do host ESXi dhe p\u00ebr ta 'lidhuar' SVM me hostet ESXi. N\u00eb k\u00ebt\u00eb rast, agjent\u00ebt e leht\u00eb t\u00eb makinave virtuale t\u00eb mbrojtura i drejtohen SVM-s\u00eb pik\u00ebrisht t\u00eb atij hosti ESXi ku jan\u00eb aktivizuar. P\u00ebr KSC-n\u00eb kryesore u zgjodh nj\u00eb tenant administrativ i ve\u00e7ant\u00eb. Si rezultat, KSC-t\u00eb n\u00ebnor jan\u00eb vendosur n\u00eb tenant\u00ebt e \u00e7do klienti t\u00eb ve\u00e7ant\u00eb dhe iu drejtohen KSC-s\u00eb kryesore, e vendosur n\u00eb segmentin menaxherial. Ky skem\u00eb lejon t\u00eb zgjidhen shpejt problemet q\u00eb shfaqen n\u00eb tenant\u00ebt e klient\u00ebve. <\/p>\n

P\u00ebrve\u00e7 \u00e7\u00ebshtjeve t\u00eb ngritjes s\u00eb komponenteve t\u00eb zgjidhjes antivirus, u p\u00ebrball\u00ebm me detyr\u00ebn p\u00ebr organizimin e nd\u00ebrveprimit rrjet\u00ebsor p\u00ebrmes krijimit t\u00eb VxLAN-ve t\u00eb tjera. Dhe megjithat\u00eb, zgjidhja n\u00eb fillim ishte parashikuar p\u00ebr klient\u00eb enterprise me cloud privat \u2014 me ndihm\u00ebn e zgjuarsis\u00eb inxhinierike dhe fleksibilitetit teknologjik t\u00eb NSX Edge, arrit\u00ebm t\u00eb zgjidhim t\u00eb gjitha detyrat q\u00eb lidhen me ndarjen e tenant\u00ebve dhe licencimin. <\/p>\n

Ne kemi punuar ngusht\u00eb me inxhinier\u00ebt e Kaspersky. Gjat\u00eb analiz\u00ebs s\u00eb arkitektur\u00ebs s\u00eb zgjidhjes sa i p\u00ebrket nd\u00ebrveprimit rrjetor midis komponent\u00ebve t\u00eb sistemit, u p\u00ebrcaktua se, p\u00ebrve\u00e7 qasjes nga agent\u00ebt e leht\u00eb n\u00eb SVM, nevojitej gjithashtu nj\u00eb feedback - nga SVM n\u00eb agent\u00ebt e leht\u00eb. Kjo lidhje rrjetore \u00ebsht\u00eb e pamundur n\u00eb nj\u00eb mjedis multitenant p\u00ebr shkak t\u00eb mund\u00ebsis\u00eb s\u00eb ekzistenc\u00ebs s\u00eb konfigurimeve rrjetore identike t\u00eb makina virtuale n\u00eb tenanta t\u00eb ndrysh\u00ebm t\u00eb rejes. Prandaj, me k\u00ebrkes\u00eb ton\u00eb, koleg\u00ebt nga ofruesi rishikuan mekanizmin e nd\u00ebrveprimit rrjetor midis agentit t\u00eb leht\u00eb dhe SVM n\u00eb pjes\u00ebn e p\u00ebrjashtimit t\u00eb nevoj\u00ebs p\u00ebr lidhjen rrjetore nga SVM n\u00eb agent\u00ebt e leht\u00eb.<\/p>\n

Pas vendosjes dhe testimit t\u00eb zgjidhjes n\u00eb platform\u00ebn e Mosk\u00ebs t\u00eb rejes, ne e shp\u00ebrndan\u00eb at\u00eb n\u00eb platformat e tjera, duke p\u00ebrfshir\u00eb segmentin e akredituar t\u00eb rejes. Tani sh\u00ebrbimi \u00ebsht\u00eb i disponuesh\u00ebm n\u00eb t\u00eb gjitha rajonet e vendit. <\/p>\n

Arkitektura e zgjidhjes s\u00eb siguris\u00eb n\u00eb kuad\u00ebr t\u00eb qasjes s\u00eb re<\/h2>\n

\nDrejtimi i p\u00ebrgjithsh\u00ebm i funksionimit t\u00eb zgjidhjes antivirus n\u00eb nj\u00eb mjedis publik t\u00eb rejes duket si n\u00eb vijim:<\/p>\n

\"Pse
\nSkema e funksionimit t\u00eb zgjidhjes antivirus n\u00eb nj\u00eb mjedis publik t\u00eb rejes #CloudMTS<\/i><\/p>\n

Le t\u00eb p\u00ebrshkruajm\u00eb ve\u00e7orit\u00eb e funksionimit t\u00eb elementeve t\u00eb ndryshme t\u00eb zgjidhjes n\u00eb re: <\/p>\n

\u2022 Nj\u00eb konsol\u00eb e vetme, e cila u lejon klient\u00ebve t\u00eb menaxhojn\u00eb n\u00eb m\u00ebnyr\u00eb qendrore sistemin e mbrojtjes: t\u00eb fillojn\u00eb kontrollet, t\u00eb kontrollojn\u00eb p\u00ebrdit\u00ebsimet dhe t\u00eb v\u00ebzhgojn\u00eb zonat e karantinit. Ka mund\u00ebsi p\u00ebr t\u00eb konfiguruar politika t\u00eb ve\u00e7anta t\u00eb siguris\u00eb brenda segmentit t\u00eb tyre. <\/p>\n

Duhet t\u00eb theksohet se, ndon\u00ebse jemi nj\u00eb ofrues sh\u00ebrbimi, ne nuk nd\u00ebrhyjm\u00eb n\u00eb ngarkesat t\u00eb cilat vendosen nga klient\u00ebt. E vetmja gj\u00eb q\u00eb mund t\u00eb b\u00ebjm\u00eb \u00ebsht\u00eb t\u00eb rikthejm\u00eb politikat e siguris\u00eb n\u00eb ato standarde n\u00eb rast se \u00ebsht\u00eb e nevojshme p\u00ebr t\u00eb rikonfiguruar. P\u00ebr shembull, kjo mund t\u00eb jet\u00eb e nevojshme n\u00ebse klienti rast\u00ebsisht i ka ashp\u00ebrsuar ose leht\u00ebsuar ndjesh\u00ebm. Kompania gjithmon\u00eb mund t\u00eb marr\u00eb nj\u00eb qend\u00ebr menaxhimi me politikat defaut, t\u00eb cilat pastaj mund t'i p\u00ebrshtat\u00eb vet\u00eb. Nj\u00eb nga disavantazhet e Kaspersky Security Center \u00ebsht\u00eb se platforma aktualisht \u00ebsht\u00eb e disponueshme vet\u00ebm p\u00ebr sistemin operativ Microsoft. Megjithat\u00eb, agjent\u00ebt e leht\u00eb mund t\u00eb funksionojn\u00eb si me makinat Windows ashtu edhe me ato Linux. Sidoqoft\u00eb, n\u00eb \"Laboratorin Kaspersky\" premtojn\u00eb se shum\u00eb shpejt KSC do t\u00eb funksionoj\u00eb gjithashtu n\u00ebn sistemin operativ Linux. Nj\u00eb nga funksionet e r\u00ebnd\u00ebsishme t\u00eb KSC \u00ebsht\u00eb mund\u00ebsia p\u00ebr t\u00eb menaxhuar karantin\u00ebn. \u00c7do kompani-klient n\u00eb cloud-in ton\u00eb ka nj\u00eb karantin\u00eb personale. Ky qasje p\u00ebrjashton situatat kur nj\u00eb dokument i infektuar me virus p\u00ebrs\u00ebri del n\u00eb shikim publik, si\u00e7 mund t\u00eb kishte ndodhur me nj\u00eb antivirus klasik korporativ me nj\u00eb karantin\u00eb t\u00eb p\u00ebrbashk\u00ebt.<\/p>\n

\u2022 Agjent\u00eb t\u00eb leht\u00eb. N\u00eb kuad\u00ebr t\u00eb modelit t\u00eb ri, n\u00eb \u00e7do makin\u00eb virtuale instalohet nj\u00eb agjent i leht\u00eb Kaspersky Security. Kjo lejon q\u00eb t\u00eb mos ruhet baza e t\u00eb dh\u00ebnave antivirus n\u00eb \u00e7do VM, duke i reduktuar k\u00ebshtu volumet e hap\u00ebsir\u00ebs disk. Sh\u00ebrbimi \u00ebsht\u00eb integrohet me infrastruktur\u00ebn e cloud-it dhe funksionon p\u00ebrmes SVM, duke rritur densitetin e makinave virtuale n\u00eb host-in ESXi dhe performanc\u00ebn e gjith\u00eb sistemit cloud. Agjenti i leht\u00eb krijon nj\u00eb radh\u00eb detyrash p\u00ebr \u00e7do makin\u00ebn virtuale: t\u00eb kontrolloj\u00eb sistemin e skedar\u00ebve, memorjen etj. Por realizimi i k\u00ebtyre operacioneve \u00ebsht\u00eb n\u00eb p\u00ebrgjegj\u00ebsin\u00eb e SVM-s\u00eb, p\u00ebr t\u00eb cil\u00ebn do t\u00eb flasim m\u00eb tutje. Gjithashtu agjenti mbulon funksionet e nj\u00eb firewalle, kontrollon politikat e siguris\u00eb, d\u00ebrgon skedar\u00eb t\u00eb infektuar n\u00eb karantin\u00eb dhe monitoron \"sh\u00ebndetin\" e p\u00ebrgjithsh\u00ebm t\u00eb sistemit operativ n\u00eb t\u00eb cilin \u00ebsht\u00eb instaluar. T\u00eb gjitha k\u00ebto mund t\u00eb menaxhohen p\u00ebrmes konsol\u00ebs s\u00eb p\u00ebrmendur m\u00eb par\u00eb. <\/p>\n

\u2022 Virtual Machine e Siguris\u00eb. T\u00eb gjitha detyrat q\u00eb k\u00ebrkojn\u00eb burime (p\u00ebrdit\u00ebsimet e bazave antivirus, kontrollet e programuar) menaxhohen nga nj\u00eb Virtual Machine e Siguris\u00eb (SVM) t\u00eb ve\u00e7ant\u00eb. Ajo \u00ebsht\u00eb p\u00ebrgjegj\u00ebse p\u00ebr funksionimin e motorit antivirus dhe bazave t\u00eb tij. Infrastruktura IT e kompanis\u00eb mund t\u00eb p\u00ebrfshij\u00eb disa SVM. Ky qasja rrit besueshm\u00ebrin\u00eb e sistemit \u2014 n\u00ebse ndonj\u00eb makin\u00eb d\u00ebshton dhe nuk p\u00ebrgjigjet p\u00ebr tridhjet\u00eb sekonda, agent\u00ebt automatikisht fillojn\u00eb t\u00eb k\u00ebrkojn\u00eb nj\u00eb tjet\u00ebr. <\/p>\n

\u2022 Serveri i Integrimit KSC. Nj\u00eb nga komponent\u00ebt e KSC kryesor, i cili cakton sipas algoritmit t\u00eb caktuar n\u00eb konfigurimet e tij, agjent\u00ebve t\u00eb leht\u00eb SVM-t\u00eb e tyre, si dhe monitoron disponueshm\u00ebrin\u00eb e SVM. K\u00ebshtu, ky moduli programor siguron balancimin e ngarkes\u00ebs n\u00eb t\u00eb gjitha SVM t\u00eb infrastruktur\u00ebs cloud. <\/p>\n

Algoritmi i funksionimit n\u00eb cloud: reduktimi i ngarkes\u00ebs n\u00eb infrastruktur\u00eb <\/h2>\n

\nN\u00eb p\u00ebrgjith\u00ebsi, algoritmi i funksionimit t\u00eb antivirusit mund t\u00eb p\u00ebrfaq\u00ebsohet si n\u00eb vijim. Agjenti i drejtohet nj\u00eb skedari n\u00eb makin\u00eb virtuale dhe e kontrollon at\u00eb. Rezultati i kontrollit ruhet n\u00eb nj\u00eb baz\u00eb t\u00eb p\u00ebrbashk\u00ebt t\u00eb qendruar t\u00eb verdiktit t\u00eb SVM (e cila quhet Shared Cache), \u00e7do regjistrim n\u00eb t\u00eb identifikon nj\u00eb most\u00ebr unike skedari. Ky qasje lejon ndjekjen q\u00eb nj\u00eb skedar i nj\u00ebjt\u00eb t\u00eb mos kontrollohet disa her\u00eb pas nj\u00ebri-tjetrit (p.sh., n\u00ebse \u00ebsht\u00eb hapur n\u00eb makina t\u00eb ndryshme virtuale). Skedari skanohet s\u00ebrish vet\u00ebm n\u00ebse jan\u00eb b\u00ebr\u00eb ndryshime n\u00eb t\u00eb ose n\u00ebse kontrolli \u00ebsht\u00eb nisur manualisht.<\/p>\n

\"Pse
\nImplementimi i zgjidhjes antivirus n\u00eb cloud t\u00eb ofruesit<\/i><\/p>\n

N\u00eb imazh paraqitet skema e p\u00ebrgjithshme e realizimit t\u00eb zgjidhjes n\u00eb re. N\u00eb zon\u00ebn menaxhuese t\u00eb deus shtrihet Kaspersky Security Center kryesor, nd\u00ebrsa n\u00eb \u00e7do host ESXi, p\u00ebrmes serverit t\u00eb integrimit KSC, \u00ebsht\u00eb shtrir\u00eb nj\u00eb SVM individuale (p\u00ebr \u00e7do host ESXi, jan\u00eb lidhur me parametrat e ve\u00e7ant\u00eb n\u00eb VMware vCenter Server SVM t\u00eb vetin). Klient\u00ebt punojn\u00eb n\u00eb segmentet e tyre t\u00eb cloud-it, ku jan\u00eb vendosur makina virtuale me agjent\u00ebt. Ato menaxhohen p\u00ebrmes serverave individual\u00eb KSC, n\u00ebn kontrollin e KSC kryesor. N\u00eb rast nevoje p\u00ebr t\u00eb mbrojtur nj\u00eb num\u00ebr t\u00eb vog\u00ebl makin\u00eb virtualesh (deri n\u00eb 5), klientit mund t'i jepet akses n\u00eb konsoll\u00ebn virtuale t\u00eb nj\u00eb serveri KSC t\u00eb dedikuar. Nd\u00ebrveprimi rrjetor midis KSC-ve t\u00eb klient\u00ebve dhe KSC kryesor, si dhe agjent\u00ebve t\u00eb leht\u00eb dhe SVM-s\u00eb, realizohet p\u00ebrmes NAT-it p\u00ebrmes ruter\u00ebve virtual\u00eb EdgeGW t\u00eb klient\u00ebve.<\/p>\n

Sipas vler\u00ebsimeve tona dhe rezultateve t\u00eb testeve t\u00eb koleg\u00ebve n\u00eb ofruesin e sh\u00ebrbimeve, Agjenti i Leht\u00eb redukton ngarkes\u00ebn n\u00eb infrastruktur\u00ebn virtuale t\u00eb klient\u00ebve p\u00ebr rreth 25% (n\u00eb krahasim me sistemin q\u00eb p\u00ebrdor program t\u00eb zakonsh\u00ebm antivirus). Konkretisht, antivirus standard i Kaspersky Endpoint Security (KES) p\u00ebr ambientet fizike konsumon pothuajse dy her\u00eb m\u00eb shum\u00eb koh\u00eb procesori t\u00eb serverit (2,95%) sesa zgjidhja p\u00ebr virtualizimin e bazuar n\u00eb agjent\u00eb t\u00eb leht\u00eb (1,67%).<\/p>\n

\"Pse
\nGrafiku i krahasimit t\u00eb ngarkes\u00ebs n\u00eb procesor
\n<\/i>
\nNj\u00eb situat\u00eb e ngjashme v\u00ebrehet me frekuenc\u00ebn e aksesit n\u00eb disk p\u00ebr shkrim: p\u00ebr antivirusin klasik ajo \u00ebsht\u00eb 1011 IOPS, p\u00ebr antivirusin n\u00eb re \u2014 671 IOPS.<\/p>\n

\"Pse
\nGrafiku i krahasimit t\u00eb frekuenc\u00ebs s\u00eb aksesit n\u00eb disk
\n<\/i>
\nFitimi n\u00eb performanc\u00eb lejon mbajtjen e stabilitetit t\u00eb infrastruktur\u00ebs dhe p\u00ebrdorimin m\u00eb efikas t\u00eb fuqive llogarit\u00ebse. P\u00ebrmes adaptimit p\u00ebr t\u00eb punuar n\u00eb nj\u00eb ambient cloud publik, zgjidhja nuk e ul performanc\u00ebn e cloud-it: ajo realizon kontrollin qendror t\u00eb skedar\u00ebve dhe ngarkimin e azhurnimeve, duke shp\u00ebrndar\u00eb ngarkes\u00ebn. Kjo do t\u00eb thot\u00eb se, nga nj\u00ebra an\u00eb, nuk do t\u00eb kalohen k\u00ebrc\u00ebnimet e r\u00ebnd\u00ebsishme p\u00ebr infrastruktur\u00ebn n\u00eb cloud, dhe nga ana tjet\u00ebr, n\u00eb mesatare do t\u00eb ulen k\u00ebrkesat p\u00ebr burime t\u00eb makinave virtuale p\u00ebr rreth 25% n\u00eb krahasim me antivirusin tradicional.<\/p>\n

Funksionaliteti i dy zgjidhjeve ngjan shum\u00eb me nj\u00ebri-tjetrin: m\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb tabel\u00eb krahasuese. Megjithat\u00eb, n\u00eb cloud, si\u00e7 tregojn\u00eb rezultatet e testimeve t\u00eb m\u00ebsip\u00ebrme, \u00ebsht\u00eb m\u00eb optimiste t\u00eb p\u00ebrdorim zgjidhje p\u00ebr mjedise virtuale. <\/p>\n

\"Pse
\n
\nRreth tarifimit n\u00eb kuad\u00ebr t\u00eb qasjes s\u00eb re.<\/b> Ne vendos\u00ebm t\u00eb p\u00ebrdorim nj\u00eb model q\u00eb lejon marrjen e licencave bazuar n\u00eb numrin e vCPU-ve. Kjo do t\u00eb thot\u00eb se numri i licencave do t\u00eb jet\u00eb i barabart\u00eb me numrin e vCPU-ve. Antivirusi mund t\u00eb testohet duke l\u00ebn\u00eb nj\u00eb k\u00ebrkes\u00eb. n\u00eb faqen e internetit<\/a><\/noindex>. <\/p>\n

N\u00eb materialin e ardhsh\u00ebm mbi tem\u00ebn e cloud-it do t\u00eb flasim p\u00ebr evoluimin e WAF-eve t\u00eb buliz\u00ebs dhe se \u00e7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb zgjidhni: harduer, softuer apo cloud. <\/p>\n

Tekstin e p\u00ebrgatit\u00ebn punonj\u00ebsit e ofruesit t\u00eb cloud-it #CloudMTS: Denis Myagkov, arkitekt kryesor dhe Alexey Afanasyev, menaxher i zhvillimit t\u00eb produkteve t\u00eb siguris\u00eb s\u00eb informacionit. <\/i><\/p>\n

Burimi: 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\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\udd47Pse antivirus\u00ebt tradicional\u00eb nuk jan\u00eb t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr cloud-et publike. Dhe \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb? | ProHoster","description":"Nj\u00eb num\u00ebr gjithnj\u00eb e n\u00eb rritje p\u00ebrdoruesish po e kalojn\u00eb t\u00ebr\u00eb infrastruktur\u00ebn e tyre IT n\u00eb cloud-in publik. Megjithat\u00eb, n\u00eb rast t\u00eb insuficenc\u00ebs s\u00eb kontrollit t\u00eb antivirusit n\u00eb infrastruktur\u00ebn e klientit, lindin rreziqe serioze kibernetike.","canonical_url":"https:\/\/prohoster.info\/sq\/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":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/39334","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=39334"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/39334\/revisions"}],"predecessor-version":[{"id":158518,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/39334\/revisions\/158518"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/39335"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=39334"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=39334"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=39334"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}