{"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 logjeve t\u00eb siguris\u00eb. Dashboardet","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"3.
\n
\nN\u00eb artikujt e m\u00ebparsh\u00ebm ne u njoftuam pak me stack-un elk dhe konfigurimin e skedarit Logstash p\u00ebr parserin e logeve; n\u00eb k\u00ebt\u00eb artikull do t\u00eb kalojm\u00eb n\u00eb at\u00eb q\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja nga pik\u00ebpamja e analiz\u00ebs, at\u00eb q\u00eb d\u00ebshironi t\u00eb shihni nga sistemi dhe p\u00ebr t\u00eb cilin \u00ebsht\u00eb krijuar gjith\u00e7ka - grafika dhe tabela 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 shohim si t\u00eb krijojm\u00eb grafika, tabela dhe si rezultat do t\u00eb nd\u00ebrtojm\u00eb nj\u00eb dashboard t\u00eb thjesht\u00eb mbi logjet nga firewall-i Check Point.
\n<\/a><\/noindex>
\nHapi i par\u00eb n\u00eb pun\u00ebn me kibana \u00ebsht\u00eb krijimi i pattern-it t\u00eb indeksit<\/b>, logjikisht, kjo \u00ebsht\u00eb baza e indekseve t\u00eb nj\u00ebjta n\u00eb nj\u00eb parim t\u00eb caktuar. Natyrisht, kjo \u00ebsht\u00eb nj\u00eb konfigurim ekskluziv p\u00ebr t\u00eb mund\u00ebsuar q\u00eb Kibana t\u00eb k\u00ebrkoj\u00eb m\u00eb leht\u00eb informacionin n\u00eb t\u00eb gjitha indikat e nj\u00ebkohshme. Kjo vendoset duke b\u00ebr\u00eb nj\u00eb p\u00ebrputhje t\u00eb vargut, p\u00ebr shembull \u201ccheckpoint-*\u201d dhe emrin e indeksit. P\u00ebr shembull, \u00abcheckpoint-2019.12.05\u00bb do t\u00eb p\u00ebrshtatet me modelin, nd\u00ebrsa thjesht \u00abcheckpoint\u00bb jo. N\u00ebnvizohet se nuk \u00ebsht\u00eb e mundur t\u00eb k\u00ebrkosh informacion n\u00eb m\u00ebnyr\u00eb t\u00eb ndryshme p\u00ebr patterat e indekseve nj\u00ebkoh\u00ebsisht; pak m\u00eb von\u00eb n\u00eb artikujt e ardhsh\u00ebm do t\u00eb shohim se API k\u00ebrkesat b\u00ebhen ose sipas emrit t\u00eb indeksit, ose p\u00ebr nj\u00eb linj\u00eb modeli, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

Pas k\u00ebsaj kontrollojm\u00eb n\u00eb menun\u00eb Discover, q\u00eb t\u00eb gjitha logjet indeksohen dhe parseri \u00ebsht\u00eb konfiguruar sakt\u00eb. N\u00ebse zbulohen ndonj\u00eb p\u00ebrputhshm\u00ebri, p\u00ebr shembull, duke ndryshuar tipin e t\u00eb dh\u00ebnave nga nj\u00eb varg n\u00eb nj\u00eb num\u00ebr t\u00eb plot\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb redaktohet skedari i konfigurimit Logstash, dhe rezultati \u00ebsht\u00eb se logjet e reja do t\u00eb ruhen sakt\u00eb. P\u00ebr t\u00eb b\u00ebr\u00eb q\u00eb logjet e vjetra t\u00eb adoptojn\u00eb pamjen e nevojshme pas ndryshimit, ndihmon vet\u00ebm procesi i riindeksimit; n\u00eb artikujt e ardhsh\u00ebm kjo operacion do t\u00eb shqyrtohet n\u00eb detaje. T\u00eb sigurohemi se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

Logjet jan\u00eb n\u00eb vend, \u00e7ka do t\u00eb thot\u00eb q\u00eb mund t\u00eb fillojm\u00eb nd\u00ebrtimin e dashboardeve. N\u00eb baz\u00eb t\u00eb analiz\u00ebs s\u00eb dashboardeve t\u00eb produkteve t\u00eb siguris\u00eb, mund t\u00eb kuptojm\u00eb gjendjen e siguris\u00eb n\u00eb organizat\u00eb, t\u00eb shohim qart\u00eb vendet e dob\u00ebta n\u00eb politik\u00ebn aktuale, dhe n\u00eb t\u00eb ardhmen t\u00eb zhvillojm\u00eb m\u00ebnyra p\u00ebr t'i eliminur ato. Do 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. tabela p\u00ebr num\u00ebrimin e numrit total t\u00eb logeve sipas bleyve<\/li>\n
  2. tabela p\u00ebr n\u00ebnshkrimet kritike t\u00eb IPS<\/li>\n
  3. diagrami rrethor p\u00ebr ngjarjet e Parandaluar t\u00eb K\u00ebrc\u00ebnimeve<\/li>\n
  4. diagrami p\u00ebr faqet m\u00eb t\u00eb vizituara<\/li>\n
  5. diagrami p\u00ebr p\u00ebrdorimin e aplikacioneve m\u00eb t\u00eb rrezikshme<\/li>\n<\/ol>\n

    \nP\u00ebr t\u00eb krijuar figurat e vizualizimit, duhet t\u00eb shkojm\u00eb n\u00eb menun\u00eb Visualize<\/b>, dhe t\u00eb zgjedhim figur\u00ebn q\u00eb duam t\u00eb nd\u00ebrtojm\u00eb! T\u00eb ecim p\u00ebrpara.<\/p>\n

    Tabela p\u00ebr num\u00ebrimin e numrit total t\u00eb logeve sipas bleyve<\/h3>\n

    \nP\u00ebr k\u00ebt\u00eb do t\u00eb zgjedhim figur\u00ebn Tabel\u00eb t\u00eb Dh\u00ebnash<\/b>, do t\u00eb hyjm\u00eb n\u00eb mjetin p\u00ebr krijimin e grafik\u00ebve, n\u00eb t\u00eb majt\u00eb vendosim parametrat e figur\u00ebs, nd\u00ebrsa djathtas pamja e saj n\u00eb cil\u00ebsimet aktuale. Fillimisht do t\u00eb tregoj se si do t\u00eb duket tabela e gatshme, pastaj do t\u00eb kalojm\u00eb n\u00eb cil\u00ebsimet, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

    Cil\u00ebsime m\u00eb t\u00eb detajuara t\u00eb figur\u00ebs, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

    Le t\u00eb shqyrtojm\u00eb cil\u00ebsimet.<\/p>\n

    Fillimisht konfigurohet metrik\u00eb<\/b>, kjo \u00ebsht\u00eb vlera mbi t\u00eb cil\u00ebn do t\u00eb grumbullohen t\u00eb gjitha fushat. Metrit shkaktohen n\u00eb baz\u00eb t\u00eb vlerave t\u00eb nxjerra n\u00eb nj\u00eb m\u00ebnyr\u00eb ose tjetr\u00ebn nga dokumentet. Vlerat zakonisht nxirren nga fushat<\/b> e dokumentit, por gjithashtu mund t\u00eb gjenerohen duke p\u00ebrdorur skenare. N\u00eb k\u00ebt\u00eb rast vendosim n\u00eb Grumbullimi: Numri<\/b> (numri total i logeve).<\/p>\n

    Pas k\u00ebsaj ndajm\u00eb tabel\u00ebn n\u00eb segmente (fusha) mbi t\u00eb cilat do t\u00eb p\u00ebrcaktohet metrika. Kjo funksion do t\u00eb kryhet nga cil\u00ebsimi Buckets, i cili nga ana e tij p\u00ebrb\u00ebhet nga 2 lloje cil\u00ebsimi: <\/p>\n

      \n
    1. ndarje rreshtash - shtimi i kolonave dhe n\u00eb t\u00eb ardhmen ndarja e tabel\u00ebs n\u00eb rreshta<\/li>\n
    2. ndarje tabele - 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 shtohen disa ndarje p\u00ebr t\u00eb krijuar disa kolona ose tabela, kufizimet k\u00ebtu jan\u00eb m\u00eb shum\u00eb logjike. N\u00eb grumbullim mund t\u00eb zgjidhni se si do t\u00eb b\u00ebhet ndarja n\u00eb segmente: gam\u00eb ipv4, gam\u00eb datash, Terma etj. Zgjedhja m\u00eb interesante \u00ebsht\u00eb Termat<\/b> dhe Termat e R\u00ebnd\u00ebsish\u00ebm<\/b>, ndarja n\u00eb segmente b\u00ebhet sipas vlerave t\u00eb nj\u00eb fushe t\u00eb caktuar t\u00eb indeksit, ndryshimi midis tyre \u00ebsht\u00eb n\u00eb numrin e vlerave q\u00eb kthehen dhe shfaqjen e tyre. Sepse ne duam t\u00eb ndajm\u00eb tabel\u00ebn sipas emrave t\u00eb bleyve, zgjedhim fush\u00ebn - product.keyword<\/b> dhe vendosim madh\u00ebsin\u00eb n\u00eb numrin 25 t\u00eb vlerave q\u00eb kthehen. <\/p>\n

      N\u00eb vend t\u00eb rreshtave n\u00eb elasticsearch p\u00ebrdoren 2 lloje t\u00eb dh\u00ebnash - text<\/b> dhe fjal\u00eb ky\u00e7e<\/b>. N\u00ebse d\u00ebshironi t\u00eb kryeni nj\u00eb k\u00ebrkim t\u00eb plot\u00eb teksti, duhet t\u00eb p\u00ebrdorni llojin text, nj\u00eb gj\u00eb shum\u00eb e dobishme kur krijoni sh\u00ebrbimin tuaj t\u00eb k\u00ebrkimit, p\u00ebr shembull, k\u00ebrkoni p\u00ebrmendjen e fjal\u00ebs n\u00eb nj\u00eb kuptim t\u00eb caktuar t\u00eb fush\u00ebs (tekstit). 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 log\u00ebt p\u00ebr nj\u00eb periudh\u00eb t\u00eb caktuar me agregimin sipas vler\u00ebs n\u00eb fush\u00ebn product. N\u00eb Custom Label vendosim emrin e kolon\u00ebs q\u00eb do t\u00eb shfaqet n\u00eb tabel\u00eb, vendosim koh\u00ebn p\u00ebr t\u00eb cil\u00ebn mbledhim log\u00ebt, fillojm\u00eb vizualizimin \u2014 Kibana d\u00ebrgon k\u00ebrkes\u00ebn n\u00eb elasticsearch, pret p\u00ebrgjigjen dhe m\u00eb pas vizualizon t\u00eb dh\u00ebnat e marra. Tabela \u00ebsht\u00eb gati!<\/p>\n

      Grafiku n\u00eb rreth p\u00ebr ngjarjet e Parandalimit t\u00eb K\u00ebrc\u00ebnimeve<\/h3>\n

      \nInformacioni \u00ebsht\u00eb me interes t\u00eb caktuar, sa \u00ebsht\u00eb gjithsej n\u00eb p\u00ebrqindje e reagimeve detect<\/b> dhe prevent<\/b> p\u00ebr incidentet e siguris\u00eb informacionit n\u00eb politik\u00ebn aktuale t\u00eb siguris\u00eb. P\u00ebr k\u00ebt\u00eb rast, grafiku n\u00eb rreth \u00ebsht\u00eb nj\u00eb zgjidhje e mir\u00eb. Zgjedhim n\u00eb Visualize \u2014 Pie chart<\/b>. Gjithashtu n\u00eb metrik\u00eb vendosim agregimin sipas numrit t\u00eb log\u00ebve. N\u00eb buckets vendosim Terms => action. <\/p>\n

      Duket se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull, por si rezultat shfaqen vlerat p\u00ebr t\u00eb gjitha blaydet, duhet t\u00eb filtrojm\u00eb vet\u00ebm p\u00ebr ato blayde q\u00eb operojn\u00eb n\u00eb kuad\u00ebr t\u00eb Parandalimit t\u00eb K\u00ebrc\u00ebnimeve. Prandaj, \u00ebsht\u00eb thelb\u00ebsore t\u00eb konfiguroni filt\u00ebr<\/b> p\u00ebr t\u00eb k\u00ebrkuar informacion vet\u00ebm p\u00ebr blaydet q\u00eb mbulojn\u00eb incidentet e siguris\u00eb informacionit \u2014 product: (\u00abAnti-Bot\u00bb OR \u00abNew Anti-Virus\u00bb OR \u00abDDoS Protector\u00bb OR \u00abSmartDefense\u00bb OR \u00abThreat Emulation\u00bb). Imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      Dhe cil\u00ebsime m\u00eb t\u00eb detajuara, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      Tabela p\u00ebr ngjarjet IPS<\/h3>\n

      \nM\u00eb pas, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme nga pik\u00ebpamja e siguris\u00eb informacionit t\u00eb shqyrtohen dhe kontrollohen ngjarjet sipas blaydeve IPS<\/b> dhe Emulimi i K\u00ebrc\u00ebnimeve<\/b>, t\u00eb cil\u00ebt nuk bllokohen<\/b> n\u00eb politik\u00ebn aktuale, p\u00ebr t\u00eb mund\u00ebsuar q\u00eb ose t\u00eb kalojm\u00eb n\u00ebnshkrimin n\u00eb prevent, ose n\u00ebse trafiku \u00ebsht\u00eb valid \u2014 t\u00eb mos kontrollojm\u00eb n\u00ebnshkrimin. Tabel\u00ebn e krijojm\u00eb po ashtu si n\u00eb shembullin e par\u00eb, vet\u00ebm me dallimin se krijojm\u00eb disa kolona: protections.keyword, severity.keyword, product.keyword, originsicname.keyword. Me r\u00ebnd\u00ebsi \u00ebsht\u00eb t\u00eb konfiguroni filtrin p\u00ebr t\u00eb k\u00ebrkuar informacion vet\u00ebm p\u00ebr blaydet q\u00eb mbulojn\u00eb incidentet e siguris\u00eb informacionit \u2014 product: ( \u00abSmartDefense\u00bb OR \u00abThreat Emulation\u00bb). Imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      Cil\u00ebsime m\u00eb t\u00eb detajuara, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      Grafik\u00ebt p\u00ebr faqet m\u00eb t\u00eb vizituara<\/h3>\n

      \nP\u00ebr k\u00ebt\u00eb krijojm\u00eb nj\u00eb figur\u00eb \u2014 Vertical Bar<\/b>. Po ashtu, metrik\u00ebn e p\u00ebrdorim count (osi Y), dhe n\u00eb osi X si vlera do p\u00ebrdorim emrat e faqeve t\u00eb vizituara \u2014 \u201cappi_name\u201d. K\u00ebtu ka nj\u00eb hile t\u00eb vog\u00ebl, n\u00ebse e fillojm\u00eb konfigurimin n\u00eb variantin aktual, t\u00eb gjitha faqet do t\u00eb shfaqen n\u00eb grafik me nj\u00eb ngjyr\u00eb, p\u00ebr t\u00eb b\u00ebr\u00eb ato me ngjyra t\u00eb ndryshme p\u00ebrdorim konfigurim shtes\u00eb \u2014 \u201csplit series\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, natyrisht! Ky ndarje mund t\u00eb p\u00ebrdoret si nj\u00eb kolone e vetme shum\u00ebngjyr\u00ebshe n\u00eb m\u00ebnyr\u00ebn stacked, ose n\u00eb m\u00ebnyr\u00ebn normale p\u00ebr t\u00eb krijuar disa kolona sipas nj\u00eb valori t\u00eb caktuar n\u00eb osi X. N\u00eb k\u00ebt\u00eb rast, ne p\u00ebrdorim t\u00eb nj\u00ebjtin vler\u00eb si n\u00eb osi X, kjo na jep mund\u00ebsin\u00eb t\u00eb b\u00ebjm\u00eb t\u00eb gjitha kolonat shum\u00ebngjyr\u00ebshe, lart majtas 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 i klikuesh\u00ebm:<\/p>\n

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

      Cil\u00ebsimet:<\/p>\n

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

      Grafiku p\u00ebr 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. Po ashtu, metrik\u00ebn e p\u00ebrdorim count (osi Y), dhe n\u00eb osi X si vlera do p\u00ebrdorim emrat e aplikacioneve t\u00eb p\u00ebrdorura- \u201cappi_name\u201d. M\u00eb e r\u00ebnd\u00ebsishmja \u00ebsht\u00eb t\u00eb vendosim filtrin \u2014 product: \u00abApplication Control\u00bb AND app_risk: (4 OR 5 OR 3 ) AND action: \u00abaccept\u00bb. Filtroni log\u00ebt sipas blaydeve t\u00eb kontrollit t\u00eb aplikacioneve, duke marr\u00eb vet\u00ebm ato faqe q\u00eb kategorizohen si faqe me rrezik Critical, High, Medium dhe vet\u00ebm n\u00ebse akseset p\u00ebr k\u00ebto faqe jan\u00eb t\u00eb lejuara. Imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      Cil\u00ebsimet, i klikuesh\u00ebm:<\/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 menus\u00eb \u2014 Tabela e informacionit<\/b>. K\u00ebtu gjith\u00e7ka \u00ebsht\u00eb e thjesht\u00eb, krijohet nj\u00eb dashboard i ri, p\u00ebr t\u00eb cilin shtohet vizualizimi, vendoset n\u00eb vende dhe gjith\u00e7ka!<\/p>\n

      Krijoni nj\u00eb dashboard, i cili do t\u00eb mund t\u00eb kuptohet p\u00ebr situat\u00ebn themelore t\u00eb gjendjes s\u00eb siguris\u00eb informacionit n\u00eb organizat\u00eb, e kuptueshme, vet\u00ebm n\u00eb nivelin e Check Point, imazhi \u00ebsht\u00eb i klikuesh\u00ebm:<\/p>\n

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

      N\u00eb baz\u00eb t\u00eb k\u00ebtyre grafik\u00ebve ne mund t\u00eb kuptojm\u00eb cilat n\u00ebnshkrime kritike nuk bllokohen n\u00eb firewall, ku shkruajn\u00eb p\u00ebrdoruesit, cilat aplikacione m\u00eb t\u00eb rrezikshme ata p\u00ebrdorin.<\/p>\n

      P\u00ebrfundimi<\/h3>\n

      \nNe shqyrtuam mund\u00ebsit\u00eb e vizualizimit baz\u00eb n\u00eb Kibana dhe nd\u00ebrtuam 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 njohim k\u00ebrkesat API, automatizimin dhe shum\u00eb gj\u00ebra t\u00eb tjera!<\/p>\n

      Pra, ndiqni p\u00ebrdit\u00ebsimet (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 logeve 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}]}}