{"id":54536,"date":"2019-12-28T00:00:00","date_gmt":"2019-12-27T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/3-elastic-stack-analiz-security-logov-dashbordy"},"modified":"2020-02-18T14:02:33","modified_gmt":"2020-02-18T11:02:33","slug":"3-elastic-stack-analiz-security-logov-dashbordy","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/3-elastic-stack-analiz-security-logov-dashbordy","title":{"rendered":"3. Elastic stack: analiza e log\u00ebve t\u00eb siguris\u00eb. Dashboard-et","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"3.
\n
\nN\u00eb artikujt e kaluar, ne u njoh\u00ebm pak me arsenalit elk dhe konfigurimin e skedarit t\u00eb konfigurimit Logstash p\u00ebr parserin e log\u00ebve, n\u00eb k\u00ebt\u00eb artikull do t\u00eb kalojm\u00eb n\u00eb at\u00eb q\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishme nga pik\u00ebpamja analitike, at\u00eb q\u00eb d\u00ebshironi t\u00eb shihni nga sistemi dhe p\u00ebr t\u00eb cil\u00ebn \u00ebsht\u00eb krijuar gjith\u00e7ka \u2014 k\u00ebto jan\u00eb grafik\u00ebt dhe tabelat t\u00eb bashkuara n\u00eb dashboarde<\/b>. Sot do t\u00eb njihemi m\u00eb af\u00ebr me sistemin e vizualizimit Kibana<\/b>, do t\u00eb shqyrtojm\u00eb se si t\u00eb krijojm\u00eb grafik\u00eb, tabela, dhe si rezultat do t\u00eb nd\u00ebrtojm\u00eb nj\u00eb dashboard t\u00eb thjesht\u00eb bazuar n\u00eb log\u00ebt nga firewalli Check Point.
\n<\/a><\/noindex>
\nHapi i par\u00eb n\u00eb pun\u00ebn me kibana \u00ebsht\u00eb krijimi i index pattern<\/b>, logjikisht, kjo \u00ebsht\u00eb baza e indekseve q\u00eb ndjekin nj\u00eb parim t\u00eb caktuar. Natyrisht, kjo \u00ebsht\u00eb nj\u00eb konfigurim ekskluziv p\u00ebr t\u00eb leht\u00ebsuar Kibana n\u00eb k\u00ebrkimin e informacionit p\u00ebr t\u00eb gjitha indiket n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb. Ajo vendoset p\u00ebrmes p\u00ebrshtatjes s\u00eb nj\u00eb string-u, p\u00ebr shembull \u201ccheckpoint-*\u201d dhe emrit t\u00eb indeksit. P\u00ebr shembull, \u00abcheckpoint-2019.12.05\u00bb do t\u00eb p\u00ebrshtatet me modelin, nd\u00ebrsa thjesht \u00abcheckpoint\u00bb nuk do t\u00eb b\u00ebj\u00eb. Ve\u00e7an\u00ebrisht duhet t\u00eb p\u00ebrmendim se nuk \u00ebsht\u00eb e mundur t\u00eb k\u00ebrkoni informacion n\u00eb lidhje me modele t\u00eb ndryshme indeksesh nj\u00ebher\u00ebsh, pak m\u00eb von\u00eb n\u00eb artikujt e ardhsh\u00ebm do t\u00eb shohim se k\u00ebrkesat API b\u00ebhen ose sipas emrit t\u00eb indeksit, ose pas nj\u00eb rreshti model, figura \u00ebsht\u00eb klikueshme:<\/p>\n

\"3.<\/a><\/noindex><\/p>\n

Pas k\u00ebsaj, kontrollem n\u00eb menun\u00eb Discover se t\u00eb gjith\u00eb log\u00ebt jan\u00eb indekseuar dhe se parseri \u00ebsht\u00eb i sakt\u00eb. N\u00ebse zbulohen ndonj\u00eb \u00e7arje, p\u00ebr shembull, t\u00eb ndryshoni tipin e t\u00eb dh\u00ebnave nga string n\u00eb num\u00ebr t\u00eb plot\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb rregulloni skedarin e konfigurimit Logstash, si rezultat log\u00ebt e reja do t\u00eb regjistrohen si\u00e7 duhet. N\u00eb m\u00ebnyr\u00eb q\u00eb log\u00ebt e vjet\u00ebr t\u00eb marrin pamjen e duhur pas ndryshimeve, ndihmon vet\u00ebm procesi i riindeksimit, n\u00eb artikujt e ardhsh\u00ebm kjo operacion do t\u00eb shqyrtohet m\u00eb n\u00eb detaje. Le t\u00eb sigurohemi se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull, figura \u00ebsht\u00eb klikueshme:<\/p>\n

\"3.<\/a><\/noindex><\/p>\n

Log\u00ebt dol\u00ebn n\u00eb vend, q\u00eb do t\u00eb thot\u00eb se mund t\u00eb fillojm\u00eb nd\u00ebrtimin e dashboardeve. N\u00eb baz\u00eb t\u00eb analiz\u00ebs s\u00eb dashboardeve nga produktet e siguris\u00eb, mund t\u00eb kuptojm\u00eb gjendjen e siguris\u00eb n\u00eb organizat\u00eb, t\u00eb shohim qart\u00eb vendet e shp\u00ebrthimit n\u00eb politik\u00ebn aktuale, dhe m\u00eb von\u00eb t\u00eb zhvillojm\u00eb m\u00ebnyrat p\u00ebr t'i eliminuar. Le t\u00eb nd\u00ebrtojm\u00eb nj\u00eb dashboard t\u00eb vog\u00ebl, duke p\u00ebrdorur disa mjete vizualizimi. Dashboardi do t\u00eb p\u00ebrb\u00ebhet nga 5 komponent\u00eb: <\/p>\n

    \n
  1. nj\u00eb tabel\u00eb p\u00ebr num\u00ebrimin e sasis\u00eb totale t\u00eb log\u00ebve sipas blade-\u00ebve<\/li>\n
  2. nj\u00eb tabel\u00eb p\u00ebr n\u00ebnshkrimet kritike IPS<\/li>\n
  3. nj\u00eb diagram petal\u00ebsh p\u00ebr ngjarjet e Parandalimit t\u00eb K\u00ebrc\u00ebnimeve<\/li>\n
  4. grafiku mbi faqet m\u00eb t\u00eb njohura t\u00eb vizituara<\/li>\n
  5. grafiku mbi p\u00ebrdorimin e aplikacioneve m\u00eb t\u00eb rrezikshme<\/li>\n<\/ol>\n

    \nP\u00ebr t\u00eb krijuar figura vizualizimi, duhet t\u00eb kaloni n\u00eb menu Vizualizo<\/b>, dhe t\u00eb zgjidhni figur\u00ebn q\u00eb d\u00ebshirojm\u00eb t\u00eb nd\u00ebrtojm\u00eb! T\u00eb ecim me radh\u00eb.<\/p>\n

    Tabel\u00eb p\u00ebr num\u00ebrimin e sasis\u00eb totale t\u00eb log\u00ebve p\u00ebr blades<\/h3>\n

    \nP\u00ebr k\u00ebt\u00eb, zgjidhim figur\u00ebn Tabela e Dh\u00ebnave<\/b>, kalojm\u00eb n\u00eb mjetin p\u00ebr krijimin e grafik\u00ebve, majtas vendosen parametrat e figur\u00ebs, djathtas si do t\u00eb duket ajo me konfigurimin aktual. Fillimisht do t\u00eb demonstroje se si do t\u00eb duket tabela e gatshme, pastaj do t\u00eb kalojm\u00eb n\u00eb parametrat, figura \u00ebsht\u00eb klikuese:<\/p>\n

    \"3.<\/a><\/noindex><\/p>\n

    Parametrat m\u00eb t\u00eb detajuar t\u00eb figur\u00ebs, figura \u00ebsht\u00eb klikuese:<\/p>\n

    \"3.<\/a><\/noindex><\/p>\n

    T\u00eb shqyrtojm\u00eb parametrat.<\/p>\n

    Fillimisht konfigurohet metrika<\/b>, kjo \u00ebsht\u00eb vlera, mbi t\u00eb cil\u00ebn do t\u00eb agregohen t\u00eb gjitha fushat. Metrit executohen mbi baz\u00ebn e vlerave t\u00eb nxjerra n\u00eb nj\u00eb ose tjetr\u00ebn m\u00ebnyr\u00eb nga dokumentet. Vlerat zakonisht nxirren nga fushat<\/b> e dokumentit, por gjithashtu mund t\u00eb gjenerohen duke p\u00ebrdorur skripte. N\u00eb k\u00ebt\u00eb rast vendosim n\u00eb Agregimi: Num\u00ebr<\/b> (sasia totale e log\u00ebve).<\/p>\n

    Pas k\u00ebsaj ndajm\u00eb tabel\u00ebn n\u00eb segmentet (fushat), sipas t\u00eb cilave do t\u00eb llogaritet metrika. Kjo funksion do t\u00eb realizohet nga konfigurimi Buckets, i cili p\u00ebrmban 2 variante t\u00eb konfigurimit: <\/p>\n

      \n
    1. ndaj rreshtave \u2014 shtimi i kolonave dhe ndarja n\u00eb vazhdim t\u00eb tabel\u00ebs n\u00eb rreshta<\/li>\n
    2. ndaj tabel\u00ebs \u2014 ndarja n\u00eb disa tabela sipas vlerave t\u00eb nj\u00eb fushe t\u00eb caktuar. <\/li>\n<\/ol>\n

      \nN\u00eb buckets<\/b> mund t\u00eb shtoni disa ndarje p\u00ebr t\u00eb krijuar disa kolona ose tabela, kufijt\u00eb k\u00ebtu jan\u00eb m\u00eb shum\u00eb logjik\u00eb. N\u00eb agregim mund t\u00eb zgjidhni sipas \u00e7far\u00eb m\u00ebnyre do t\u00eb ndodh\u00eb ndarja n\u00eb segmente: ipv4 range, date range, Terms etj. Zgjedhja m\u00eb interesante \u00ebsht\u00eb pik\u00ebrisht Terms<\/b> dhe Vlerat e R\u00ebnd\u00ebsishme<\/b>, ndarja n\u00eb segmente b\u00ebhet sipas vlerave t\u00eb nj\u00eb fushe t\u00eb caktuar t\u00eb indeksit, ndryshimi midis tyre q\u00ebndron n\u00eb numrin e vlerave q\u00eb kthehen dhe shfaqjen e tyre. Duke qen\u00eb se duam t\u00eb ndajm\u00eb tabel\u00ebn sipas emrave t\u00eb blades, zgjidhim fush\u00ebn \u2014 product.keyword<\/b> dhe caktojm\u00eb madh\u00ebsin\u00eb n\u00eb numrin e 25 vlerave q\u00eb kthehen. <\/p>\n

      N\u00eb vend t\u00eb rreshtave n\u00eb elasticsearch p\u00ebrdoren 2 tipe t\u00eb dh\u00ebnash \u2014 text<\/b> dhe fjal\u00eb ky\u00e7e<\/b>. N\u00ebse d\u00ebshironi t\u00eb kryeni nj\u00eb k\u00ebrkim t\u00eb plot\u00eb, duhet t\u00eb p\u00ebrdorni llojin tekst, nj\u00eb gj\u00eb shum\u00eb e p\u00ebrshtatshme kur shkruani sh\u00ebrbimin tuaj t\u00eb k\u00ebrkimit, p\u00ebr shembull, k\u00ebrkoni p\u00ebrmendjen e nj\u00eb fjale n\u00eb kuptimin e caktuar t\u00eb fush\u00ebs (tekst). N\u00ebse d\u00ebshironi vet\u00ebm p\u00ebrputhje t\u00eb sakt\u00eb, duhet t\u00eb p\u00ebrdorni llojin keyword. Po ashtu, lloji i t\u00eb dh\u00ebnave keyword duhet t\u00eb p\u00ebrdoret p\u00ebr fushat q\u00eb k\u00ebrkojn\u00eb renditje ose agregim, pra, n\u00eb rastin ton\u00eb.<\/p>\n

      Si rezultat, Elasticsearch num\u00ebron numrin e logeve p\u00ebr nj\u00eb koh\u00eb t\u00eb caktuar me agregatimin sipas vler\u00ebs n\u00eb fush\u00ebn produkt. N\u00eb Custom Label vendosim emrin e kolon\u00ebs, e cila do t\u00eb shfaqet n\u00eb tabel\u00eb, p\u00ebrcaktojm\u00eb koh\u00ebn p\u00ebr t\u00eb cil\u00ebn mbledhim loget, aktivizojm\u00eb vizualizimin \u2014 Kibana d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb n\u00eb elasticsearch, pret p\u00ebrgjigjen dhe pastaj vizualizon t\u00eb dh\u00ebnat e marra. Tabela \u00ebsht\u00eb gati!<\/p>\n

      Grafiku circular mbi ngjarjet e Parandalimit t\u00eb K\u00ebrc\u00ebnimeve<\/h3>\n

      \nInformacioni p\u00ebrb\u00ebn nj\u00eb interes t\u00eb caktuar, sa p\u00ebrqindje reagimesh ka n\u00eb t\u00ebr\u00ebsi detect<\/b> dhe prevent<\/b> p\u00ebr incidentet e siguris\u00eb kibernetike n\u00eb politik\u00ebn aktuale t\u00eb siguris\u00eb. P\u00ebr k\u00ebt\u00eb rast, grafiku circular \u00ebsht\u00eb shum\u00eb i p\u00ebrshtatsh\u00ebm. Zgjidhim n\u00eb Visualize \u2014 Pie chart<\/b>. Po ashtu n\u00eb metrik\u00eb vendosim agregimin sipas numrit t\u00eb logeve. N\u00eb buckets vendosim Terms => action. <\/p>\n

      Duket gjith\u00eb kjo \u00ebsht\u00eb n\u00eb rregull, por si rezultat shfaqen vlera p\u00ebr t\u00eb gjith\u00eb bleybat, duhet filtruara vet\u00ebm p\u00ebr ata blejbat q\u00eb veprojn\u00eb n\u00eb kuad\u00ebr t\u00eb Parandalimit t\u00eb K\u00ebrc\u00ebnimeve. Prandaj domosdoshm\u00ebrisht konfigurojm\u00eb filter<\/b> p\u00ebr t\u00eb k\u00ebrkuar informacion vet\u00ebm p\u00ebr blejbat q\u00eb jan\u00eb p\u00ebrgjegj\u00ebs p\u00ebr incidentet e siguris\u00eb kibernetike \u2014 produkt: (\"Anti-Bot\" OR \"New Anti-Virus\" OR \"DDoS Protector\" OR \"SmartDefense\" OR \"Threat Emulation\"). Imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Dhe m\u00eb shum\u00eb konfigurime t\u00eb detajuara, imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Tabela mbi ngjarjet IPS<\/h3>\n

      \nM\u00eb pas, nj\u00eb gj\u00eb shum\u00eb e r\u00ebnd\u00ebsishme nga k\u00ebndv\u00ebshtrimi i siguris\u00eb kibernetike \u00ebsht\u00eb shikimi dhe kontrolli i ngjarjeve sipas bleybit IPS<\/b> dhe Threat Emulation<\/b>, q\u00eb nuk bllokohen<\/b> nga politika aktuale, p\u00ebr t\u00eb kaluar m\u00eb pas ose p\u00ebr t\u00eb kthyer n\u00ebnshkrimin n\u00eb prevent, ose n\u00ebse trafiku \u00ebsht\u00eb valid \u2014 mos ta kontrolloni n\u00ebnshkrimin. Tabel\u00ebn e krijojm\u00eb po ashtu si p\u00ebr shembullin e par\u00eb, vet\u00ebm me p\u00ebrjashtimin se krijojm\u00eb disa kolona: protections.keyword, severity.keyword, product.keyword, originsicname.keyword. Sigurisht q\u00eb konfigurojm\u00eb filtrin p\u00ebr t\u00eb k\u00ebrkuar informacion vet\u00ebm p\u00ebr blejbat q\u00eb jan\u00eb p\u00ebrgjegj\u00ebs p\u00ebr incidentet e siguris\u00eb kibernetike \u2014 produkt: (\"SmartDefense\" OR \"Threat Emulation\"). Imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      M\u00eb shum\u00eb konfigurime t\u00eb detajuara, imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Grafik\u00ebt mbi faqet m\u00eb t\u00eb njohura t\u00eb vizituara<\/h3>\n

      \nP\u00ebr k\u00ebt\u00eb krijojm\u00eb nj\u00eb figur\u00eb \u2014 Vertical Bar<\/b>. Metrixin gjithashtu e p\u00ebrdorim count (aksin Y), nd\u00ebrsa n\u00eb aksin X si vlera do t\u00eb p\u00ebrdorim emrat e faqeve t\u00eb vizituara \u2014 \u201cappi_name\u201d. K\u00ebtu ka nj\u00eb mashtrim t\u00eb vog\u00ebl, n\u00ebse e fillojm\u00eb konfigurimin n\u00eb variantin aktual, t\u00eb gjitha faqet do t\u00eb etiketohen n\u00eb grafik me nj\u00eb ngjyr\u00eb, p\u00ebr ta b\u00ebr\u00eb ato shum\u00ebngjyr\u00ebsh, p\u00ebrdorim nj\u00eb konfigurim shtes\u00eb \u2014 \u201cndaj seri\u201d, i cili lejon ndarjen e nj\u00eb kolone t\u00eb gatshme n\u00eb disa vlera t\u00eb tjera, n\u00eb var\u00ebsi t\u00eb fush\u00ebs s\u00eb zgjedhur sigurisht! Kjo ndarje mund t\u00eb p\u00ebrdoret ose si nj\u00eb kolon\u00eb me ngjyra t\u00eb ndryshme n\u00eb modin stacked, ose n\u00eb modin normal p\u00ebr t\u00eb krijuar disa kolona sipas nj\u00eb vlere t\u00eb caktuar n\u00eb aksin X. N\u00eb k\u00ebt\u00eb rast ne p\u00ebrdorim t\u00eb nj\u00ebjt\u00ebn vler\u00eb si n\u00eb aksin X, kjo na jep mund\u00ebsin\u00eb p\u00ebr t\u00eb b\u00ebr\u00eb t\u00eb gjitha kolonat shum\u00ebngjyr\u00ebshe, n\u00eb t\u00eb djatht\u00eb lart ato do t\u00eb shfaqen me ngjyra. N\u00eb filtrin vendosim \u2014 product:\u00abURL Filtering\u00bb p\u00ebr t\u00eb par\u00eb informacion vet\u00ebm p\u00ebr faqet e vizituara, imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Konfigurimet:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Diagrami mbi p\u00ebrdorimin e aplikacioneve m\u00eb t\u00eb rrezikshme<\/h3>\n

      \nP\u00ebr k\u00ebt\u00eb krijojm\u00eb nj\u00eb figur\u00eb \u2014 Vertical Bar. Metrixin gjithashtu e p\u00ebrdorim count (aksin Y), nd\u00ebrsa n\u00eb aksin X si vlera do t\u00eb p\u00ebrdorim emrat e aplikacioneve q\u00eb p\u00ebrdoren\u2014 \u201cappi_name\u201d. M\u00eb importante \u00ebsht\u00eb caktimi i filtrit \u2014 product: \u00abApplication Control\u00bb AND app_risk: (4 OR 5 OR 3) AND action:\u00abaccept\u00bb. Filtroni log\u00ebt sipas blaidit t\u00eb kontrollit t\u00eb aplikacioneve, marrim vet\u00ebm ato faqe q\u00eb jan\u00eb t\u00eb kategorizuara si faqe me rrezik Kritike, t\u00eb Lart\u00eb, Mesatare dhe vet\u00ebm n\u00eb rast se aksesit \u00ebsht\u00eb lejuar p\u00ebr k\u00ebto faqe. Imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Konfigurimet, klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      Dashboard<\/h3>\n

      \nShikimi dhe krijimi i dashboard-eve ndodhet n\u00eb nj\u00eb pik\u00eb t\u00eb ve\u00e7ant\u00eb t\u00eb menas\u00eb \u2014 Panair<\/b>. K\u00ebtu \u00ebsht\u00eb gjith\u00e7ka e thjesht\u00eb, krijohet nj\u00eb dashboard i ri, i shtohet vizualizimi, renditet n\u00eb vend dhe gjith\u00e7ka!<\/p>\n

      Krijojm\u00eb nj\u00eb dashboard, me t\u00eb cilin mund t\u00eb kuptojm\u00eb situat\u00ebn bazike t\u00eb gjendjes s\u00eb Siguris\u00eb Informative n\u00eb organizat\u00eb, e qart\u00eb, vet\u00ebm n\u00eb nivelin Check Point, imazhi \u00ebsht\u00eb klikues:<\/p>\n

      \"3.<\/a><\/noindex><\/p>\n

      N\u00eb baz\u00eb t\u00eb k\u00ebtyre grafik\u00ebve ne mund t\u00eb kuptojm\u00eb se cila n\u00ebnshkrim kritike nuk bllokohet n\u00eb nd\u00ebrmjet\u00ebsin e rrjetit, ku shkojn\u00eb p\u00ebrdoruesit, cilat jan\u00eb aplikacionet m\u00eb t\u00eb rrezikshme q\u00eb ata p\u00ebrdorin.<\/p>\n

      P\u00ebrfundim<\/h3>\n

      \nNe kemi shqyrtuar mund\u00ebsit\u00eb e visualizimit baz\u00eb n\u00eb Kibana dhe kemi nd\u00ebrtuar nj\u00eb dashboard, por kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb pjes\u00eb e vog\u00ebl. M\u00eb pas n\u00eb kurs do t\u00eb shqyrtojm\u00eb ve\u00e7mas konfigurimin e hartave, pun\u00ebn me sistemin elasticsearch, do t\u00eb njihemi me k\u00ebrkesat API, automatizimin dhe shum\u00eb gj\u00ebra t\u00eb tjera!<\/p>\n

      Prandaj, q\u00ebndroni t\u00eb informuar p\u00ebr azhurnimet (Telegram<\/a><\/noindex>, Facebook<\/a><\/noindex>, VK<\/a><\/noindex>, Blogu i Zgjidhjeve TS<\/a><\/noindex>), Yandex.Zen<\/a><\/noindex>.
      \n
      Burimi:       habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

      \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0445 \u0441\u0442\u0430\u0442\u044c\u044f\u0445 \u043c\u044b \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u043e\u0437\u043d\u0430\u043a\u043e\u043c\u0438\u043b\u0438\u0441\u044c \u0441\u043e \u0441\u0442\u0435\u043a\u043e\u043c elk \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u043e\u0439 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0433\u043e \u0444\u0430\u0439\u043b\u0430 Logstash \u0434\u043b\u044f \u043f\u0430\u0440\u0441\u0435\u0440\u0430 \u043b\u043e\u0433\u043e\u0432, \u0432 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043f\u0435\u0440\u0435\u0439\u0434\u0435\u043c \u043a \u0441\u0430\u043c\u043e\u043c\u0443 \u0432\u0430\u0436\u043d\u043e\u043c\u0443 \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u043a\u0438, \u0442\u043e \u0447\u0442\u043e \u0432\u044b \u0445\u043e\u0442\u0438\u0442\u0435 \u0443\u0432\u0438\u0434\u0435\u0442\u044c \u043e\u0442 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0438 \u0440\u0430\u0434\u0438 \u0447\u0435\u0433\u043e \u0432\u0441\u0435 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u043b\u043e\u0441\u044c \u2014 \u044d\u0442\u043e \u0433\u0440\u0430\u0444\u0438\u043a\u0438 \u0438 \u0442\u0430\u0431\u043b\u0438\u0446\u044b \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0435\u043d\u043d\u044b\u0435 \u0432 \u0434\u0430\u0448\u0431\u043e\u0440\u0434\u044b. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0431\u043b\u0438\u0436\u0435 \u043e\u0437\u043d\u0430\u043a\u043e\u043c\u0438\u043c\u0441\u044f \u0441 \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u0432\u0438\u0437\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54536","post","type-post","status-publish","format-standard","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\n","aioseo_head_json":{"title":"\ud83e\udd473. Elastic stack: analiza e logjeve t\u00eb siguris\u00eb. Dashboardet | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/3-elastic-stack-analiz-security-logov-dashbordy","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\udd473. Elastic stack: \u0430\u043d\u0430\u043b\u0438\u0437 security \u043b\u043e\u0433\u043e\u0432. \u0414\u0430\u0448\u0431\u043e\u0440\u0434\u044b | ProHoster","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/3-elastic-stack-analiz-security-logov-dashbordy","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-12-27T21:00:00+00:00","article:modified_time":"2020-02-18T11:02:33+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54536","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-24 11:45:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:03:57","updated":"2026-01-24 11:45:20","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\/54536","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=54536"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/54536\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=54536"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=54536"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=54536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}