{"id":84184,"date":"2020-06-05T19:42:31","date_gmt":"2020-06-05T17:42:31","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/smertnye-grehi-bezopasnosti-sajta-chto-my-uznali-iz-statistiki-skanera-uyazvimostej-za-god"},"modified":"2020-06-05T19:42:31","modified_gmt":"2020-06-05T17:42:31","slug":"smertnye-grehi-bezopasnosti-sajta-chto-my-uznali-iz-statistiki-skanera-uyazvimostej-za-god","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/smertnye-grehi-bezopasnosti-sajta-chto-my-uznali-iz-statistiki-skanera-uyazvimostej-za-god","title":{"rendered":"G\u00fcn\u0446\u0438\u0442\u0435 fatale t\u00eb siguris\u00eb s\u00eb faqes: \u00e7far\u00eb m\u00ebsuam nga statistikat e skanerit t\u00eb dob\u00ebsive gjat\u00eb vitit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Rreth nj\u00eb vit m\u00eb par\u00eb, ne n\u00eb DataLine lan\u00e7uam sh\u00ebrbim<\/a><\/noindex> p\u00ebr k\u00ebrkimin dhe analizimin e dob\u00ebsive n\u00eb aplikacionet IT. Baza e sh\u00ebrbimit \u00ebsht\u00eb zgjidhja cloud Qualys, p\u00ebr t\u00eb cil\u00ebn ne kemi biseduar tashm\u00eb<\/a><\/noindex>. Gjat\u00eb nj\u00eb viti p\u00ebrdorimi t\u00eb zgjidhjes, ne kemi kryer 291 skanime p\u00ebr faqe t\u00eb ndryshme dhe kemi grumbulluar statistika mbi dob\u00ebsit\u00eb e zakonshme n\u00eb aplikacionet web.\u00a0<\/p>\n

N\u00eb artikullin m\u00eb posht\u00eb do t\u00eb tregoj se cilat pik\u00ebpamje t\u00eb siguris\u00eb s\u00eb faqeve fshihen pas niveleve t\u00eb ndryshme t\u00eb r\u00ebnd\u00ebsis\u00eb. Le t\u00eb shohim cilat dob\u00ebsi i ka gjetur skaneri m\u00eb shpesh, pse ato mund t\u00eb ndodhin dhe si mund t\u00eb mbroni veten.\u00a0<\/p>\n

\"G\u00fcn\u0446\u0438\u0442\u0435
\n<\/a><\/noindex>
\nT\u00eb gjitha dob\u00ebsit\u00eb e aplikacioneve web Qualys i ndan n\u00eb tri nivele r\u00ebnd\u00ebsie: t\u00eb ul\u00ebta, t\u00eb mesme dhe t\u00eb larta. N\u00ebse shikojm\u00eb shp\u00ebrndarjen sipas \"pesh\u00ebs\", duket se gjendja nuk \u00ebsht\u00eb kaq e keqe. Dob\u00ebsit\u00eb me nivel t\u00eb lart\u00eb r\u00ebnd\u00ebsie jan\u00eb t\u00eb pakta, kryesisht t\u00eb gjitha jan\u00eb jo kritike:\u00a0<\/p>\n

\"G\u00fcn\u0446\u0438\u0442\u0435
\n
\nPor jo kritik nuk do t\u00eb thot\u00eb pa rrezik. Ato gjithashtu mund t\u00eb shkaktojn\u00eb d\u00ebme serioze.\u00a0<\/p>\n

T\u00eb dh\u00ebnat kryesore t\u00eb dob\u00ebsive \"jo kritike\"<\/h2>\n

<\/p>\n

    \n
  1. Dob\u00ebsit\u00eb q\u00eb lidhen me p\u00ebrmbajtjen e p\u00ebrzier.<\/b>\n

    Standardi i siguris\u00eb p\u00ebr faqet web konsiderohet t\u00eb jet\u00eb transmetimi i t\u00eb dh\u00ebnave midis klientit dhe serverit n\u00ebp\u00ebrmjet protokolit HTTPS, i cili mb\u00ebshtet enkriptimin dhe mbron informacionin nga kapja.\u00a0<\/p>\n

    Disa faqe p\u00ebrdorin p\u00ebrmbajtje t\u00eb p\u00ebrzier<\/i>: transmetojn\u00eb nj\u00eb pjes\u00eb t\u00eb t\u00eb dh\u00ebnave p\u00ebrmes protokollit t\u00eb pasigurt HTTP. Shpesh k\u00ebshtu transmetohet p\u00ebrmbajtja pasive<\/i> \u2013 informacione q\u00eb ndikojn\u00eb vet\u00ebm n\u00eb shfaqjen e faqes: imazhe, stilet css. Por ndonj\u00ebher\u00eb k\u00ebshtu transmetohet dhe p\u00ebrmbajtja aktive<\/i>: skriptet q\u00eb menaxhojn\u00eb sjelljen e faqes. N\u00eb k\u00ebt\u00eb rast, me ndihm\u00ebn e softuerit t\u00eb ve\u00e7ant\u00eb, \u00ebsht\u00eb e mundur t\u00eb analizohet informacija q\u00eb vjen nga serveri me p\u00ebrmbajtje aktive, t\u00eb modifikohet n\u00eb koh\u00eb reale p\u00ebrgjigjet e saj dhe t\u00eb detyrohet makina t\u00eb funksionoj\u00eb ndryshe nga si ishte parashikuar nga krijuesit e saj.\u00a0<\/p>\n

    Broswerat e versioneve t\u00eb reja paralajm\u00ebrojn\u00eb p\u00ebrdoruesit se faqet me p\u00ebrmbajtje t\u00eb p\u00ebrzier nuk jan\u00eb t\u00eb sigurta dhe bllokojn\u00eb p\u00ebrmbajtjen. Zhvilluesit e faqeve gjithashtu marrin paralajm\u00ebrime nga brosweri n\u00eb konsol\u00eb. Ja si duket kjo n\u00eb Firefox<\/a><\/noindex>:\u00a0<\/p>\n

    \"G\u00fcn\u0446\u0438\u0442\u0435
    \n
    \n\u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: Kriminel\u00ebt p\u00ebrdorin protokollin e pasigurt p\u00ebr t\u00eb kapur informacionin rreth p\u00ebrdoruesit, p\u00ebr t\u00eb z\u00ebvend\u00ebsuar skriptet dhe p\u00ebr t\u00eb d\u00ebrguar k\u00ebrkesa n\u00eb sit n\u00eb emrin e tij. Edhe n\u00ebse vizitori i faqes nuk ka futur t\u00eb dh\u00ebna, kjo nuk e mbron at\u00eb nga phishing <\/i>- grumbullimi i informacionit t\u00eb ndjesh\u00ebm me metoda mashtruese. P\u00ebr shembull, me ndihm\u00ebn e nj\u00eb skripti, mund t\u00eb ridrejtohet p\u00ebrdoruesi n\u00eb nj\u00eb faqe t\u00eb pasigurt, e cila maskohet si nj\u00eb faqe e njohur p\u00ebr p\u00ebrdoruesin. N\u00eb raste t\u00eb ve\u00e7anta, faqja e keqe duket madje m\u00eb mir\u00eb se origjinali, dhe p\u00ebrdoruesi mund ta plot\u00ebsoj\u00eb form\u00ebn dhe t'i p\u00ebrcjell\u00eb t\u00eb dh\u00ebnat e ndjeshme.\u00a0<\/p>\n

    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Edhe n\u00ebse administratori i faqes ka instaluar dhe konfiguruar certifikat\u00ebn SSL\/TLS, dob\u00ebsit\u00eb mund t\u00eb ndodhin p\u00ebr shkak t\u00eb faktor\u00ebve njer\u00ebzor\u00eb. P\u00ebr shembull, n\u00ebse n\u00eb ndonj\u00eb nga faqet \u00ebsht\u00eb vendosur nj\u00eb lidhje jo relative, por absolute me http, dhe p\u00ebrve\u00e7 k\u00ebsaj nuk jan\u00eb konfiguruar ridrejtime nga http n\u00eb https.\u00a0<\/p>\n

    P\u00ebr t\u00eb zbuluar p\u00ebrmbajtje t\u00eb p\u00ebrzier n\u00eb faqe, mund t\u00eb p\u00ebrdorni broswerin: t\u00eb k\u00ebrkoni n\u00eb kodin burimor t\u00eb faqes, t\u00eb lexoni njoftimet n\u00eb konsol\u00ebn e zhvilluesit. Megjithat\u00eb, zhvilluesi do t\u00eb duhet t\u00eb p\u00ebrballet me nj\u00eb kod t\u00eb gjat\u00eb dhe t\u00eb mundimsh\u00ebm. Procesin mund ta shpejtoj\u00eb mjete t\u00eb automatizuara analize, p\u00ebr shembull: SSL Check<\/a><\/noindex>, softueri i lir\u00eb Lighthouse ose softueri me pages\u00eb Screaming Frog SEO Spider.<\/p>\n

    Gjithashtu, dob\u00ebsit\u00eb mund t\u00eb ndodhin p\u00ebr shkak t\u00eb problemeve me kodin e trash\u00ebguar \u2013 kodin q\u00eb u kalua nga brezi n\u00eb brez. P\u00ebr shembull, n\u00ebse disa faqe gjenerohen nga nj\u00eb model t\u00eb vjet\u00ebr, ku nuk merret parasysh kalimi i faqeve n\u00eb https.\u00a0\u00a0\u00a0\u00a0\n<\/li>\n

  2. Cookies pa flamujt \u00abHTTPOnly\u00bb dhe \u00absecure\u00bb.<\/b>\n

    Atributi \u00abHTTPOnly\u00bb mbron skedar\u00ebt e cookies nga p\u00ebrpunimi i skripteve q\u00eb kriminel\u00ebt p\u00ebrdorin p\u00ebr t\u00eb vjedhur t\u00eb dh\u00ebnat e p\u00ebrdoruesve. Flamuri \u00absecure\u00bb nuk lejon d\u00ebrgimin e cookies n\u00eb form\u00eb t\u00eb hapur. Shk\u00ebmbimi i t\u00eb dh\u00ebnave do t\u00eb jet\u00eb i lejuar vet\u00ebm n\u00ebse p\u00ebr d\u00ebrgimin e cookies p\u00ebrdoret protokolli i sigurt HTTPS.\u00a0<\/p>\n

    T\u00eb dy atributet shkruhen n\u00eb pronat e cookies:<\/p>\n

    Set-Cookie: Secure; HttpOnly<\/code><\/pre>\n
    \n\u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: N\u00ebse zhvilluesi i faqes nuk ka specifikuar k\u00ebto atribute, nj\u00eb kriminel mund t\u00eb kap\u00eb informacionin e p\u00ebrdoruesit nga cookies dhe ta shfryt\u00ebzoj\u00eb at\u00eb. N\u00ebse cookies p\u00ebrdoren p\u00ebr autentikimin dhe autorizimin, ai do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb dyfishoj\u00eb seanc\u00ebn e p\u00ebrdoruesit dhe t\u00eb kryej\u00eb veprime n\u00eb faqe n\u00eb emrin e tij.\u00a0<\/p>\n
    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Si rregull, n\u00eb framework-et e njohura k\u00ebto atribute p\u00ebrcaktohen automatikisht. Por p\u00ebrs\u00ebri, kontrolloni konfigurimin e serverit tuaj web dhe vendosni flamurin: Set-Cookie HttpOnly; Secure. <\/p>\n
    P\u00ebr m\u00eb tep\u00ebr, atributi \u00abHTTPOnly\u00bb do t'i b\u00ebj\u00eb cookies t\u00eb padukshme edhe p\u00ebr JavaScript-in tuaj.\u00a0\u00a0\n<\/li>\n
  3. Dob\u00ebsit\u00eb e bazuara n\u00eb rrug\u00eb (\u00abdob\u00ebsi rrugore\u00bb).<\/b>\n
    Skeneri njofton p\u00ebr nj\u00eb dob\u00ebsi t\u00eb till\u00eb n\u00ebse gjen nj\u00eb skedar ose direktor t\u00eb disponuesh\u00ebm publik n\u00eb faqen e internetit me informacione potencialisht konfidenciale. P\u00ebr shembull, zbulon skedar\u00eb t\u00eb ve\u00e7ant\u00eb me konfigurimin e sistemit ose qasje t\u00eb gjithanshme n\u00eb sistemin e skedareve. Kjo situat\u00eb \u00ebsht\u00eb e mundur n\u00ebse jan\u00eb vendosur keq t\u00eb drejtat e aksesit n\u00eb faqe.<\/p>\n
    \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: N\u00ebse sistemi i skedar\u00ebve \"doli jasht\u00eb\", nj\u00eb sulmues mund t\u00eb dep\u00ebrtoj\u00eb n\u00eb nd\u00ebrfaqen e sistemit operativ dhe t\u00eb p\u00ebrpiqet t\u00eb gjej\u00eb dosje me fjal\u00ebkalime, n\u00ebse ato ruhen n\u00eb m\u00ebnyr\u00eb t\u00eb hapur (mos e b\u00ebni k\u00ebt\u00eb!). Ose mund t\u00eb vjedh\u00eb hash-\u00ebt e fjal\u00ebkalimeve dhe t\u00eb provoj\u00eb t\u00eb gjej\u00eb fjal\u00ebkalimin, si dhe t\u00eb p\u00ebrpiqet t\u00eb rris\u00eb privilegjet n\u00eb sistem dhe t\u00eb avancoj\u00eb brenda infrastruktur\u00ebs.\u00a0\u00a0<\/p>\n
    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Mos haroni p\u00ebr t\u00eb drejtat e aksesit dhe konfiguroni platform\u00ebn, serverin web, aplikacionin web, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mos jet\u00eb e mundur \"t\u00eb shp\u00ebtohet\" nga direktoria web.\n<\/li>\n
  4. Format p\u00ebr hyrjen e t\u00eb dh\u00ebnave konfidenciale me funksionin e autoshkurtimit t\u00eb aktivizuar.<\/b>\n
    N\u00ebse nj\u00eb p\u00ebrdorues shpesh plot\u00ebson forma n\u00eb faqe, shfletuesi i tij ruan k\u00ebt\u00eb informacion p\u00ebrmes funksionit t\u00eb autoshkurtimit.\u00a0<\/p>\n
    Format n\u00eb faqet e internetit mund t\u00eb p\u00ebrmbajn\u00eb fusha me informacione konfidenciale, p\u00ebr shembull, fjal\u00ebkalime ose numra kartash krediti. P\u00ebr k\u00ebto fusha, \u00ebsht\u00eb e rekomandueshme t\u00eb \u00e7aktivizohet funksioni i autoshkurtimit t\u00eb formave n\u00eb faqen e internetit.\u00a0<\/p>\n
    \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: N\u00ebse shfletuesi i p\u00ebrdoruesit ruan informacionin konfidencial, nj\u00eb sulmues mund ta kap\u00eb at\u00eb m\u00eb von\u00eb, p\u00ebr shembull, p\u00ebrmes phishing-ut. N\u00eb thelb, nj\u00eb zhvillues web-i q\u00eb t\u00eb harroj\u00eb k\u00ebt\u00eb aspekt rrezikon p\u00ebrdoruesit e tij.\u00a0<\/p>\n
    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: N\u00eb k\u00ebt\u00eb rast kemi nj\u00eb konflikt klasik: komoditeti vs. siguria. N\u00ebse nj\u00eb zhvillues web-i mendon p\u00ebr komoditetin e p\u00ebrdoruesit, ai mund t\u00eb zgjedh\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb vet\u00ebdijshme autoshkurtimin. P\u00ebr shembull, n\u00ebse \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb ndiqet Udh\u00ebzimet p\u00ebr Aksesueshm\u00ebrin\u00eb e P\u00ebmbajtjes Web<\/a><\/noindex> \u2013 rekomandime p\u00ebr aksesueshm\u00ebrin\u00eb e p\u00ebrmbajtjes p\u00ebr p\u00ebrdoruesit me aft\u00ebsi t\u00eb kufizuara.\u00a0<\/p>\n
    P\u00ebr shumic\u00ebn e shfletoreshave, mund t\u00eb \u00e7aktivizohet autoshkurtimi p\u00ebrmes atributit autocompete=\"off\", p\u00ebr shembull:<\/p>\n
    \u00a0<body>\n    <form action="\/sq\/form\/submit\/" method="get" autocomplete="off" data-trp-original-action="\/form\/submit">\n      <div>\n        <input type="text" placeholder="Emri">\n      <\/div>\n      <div>\n        <input type="text" id="lname" placeholder="Emri i fundit" autocomplete="on">\n      <\/div>\n      <div>\n        <input type="number" placeholder="Numri i kartës së kreditit">\n      <\/div>\n      <input type="submit">\n    <input type="hidden" name="trp-form-language" value="sq"\/><\/form>\n  <\/body><\/code><\/pre>\n
    \nPor p\u00ebr Chrome, kjo nuk do t\u00eb funksionoj\u00eb. Kjo kalohet p\u00ebrmes JavaScript-it, nj\u00eb variant mund t\u00eb gjendet k\u00ebtu<\/a><\/noindex>.\u00a0\n<\/li>\n
  5. N\u00eb kodin e faqes nuk \u00ebsht\u00eb caktuar titulli X-Frame-Options.\u00a0<\/b>\n
    Ky titull ndikon n\u00eb etiketat frame, iframe, embed ose object. Me t\u00eb, mund t\u00eb ndalohet plot\u00ebsisht p\u00ebrfshirja e faqes suaj brenda nj\u00eb framer. P\u00ebr k\u00ebt\u00eb duhet t\u00eb p\u00ebrcaktohet vlera X-Frame-Options: deny. Ose mund t\u00eb p\u00ebrcaktohet X-Frame-Options: sameorigin, n\u00eb k\u00ebt\u00eb rast p\u00ebrfshirja n\u00eb iframe do t\u00eb jet\u00eb e disponueshme vet\u00ebm n\u00eb domainin tuaj.<\/p>\n
    \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: Mungesa e k\u00ebtij titulli mund t\u00eb p\u00ebrdoret n\u00eb faqe t\u00eb d\u00ebmshme p\u00ebr klikatake.<\/i>. P\u00ebr nj\u00eb sulm t\u00eb till\u00eb, nj\u00eb sulmues krijon nj\u00eb frame t\u00eb qart\u00eb mbi butonat dhe e mashtron p\u00ebrdoruesin. P\u00ebr shembull: mashtruesit vendosin n\u00eb frame n\u00eb faqe dhe faqet e rrjeteve sociale. P\u00ebrdoruesi mendon se po klikon nj\u00eb buton n\u00eb k\u00ebt\u00eb faqe. N\u00eb vend t\u00eb k\u00ebsaj, klikimi kapet dhe d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb t\u00eb p\u00ebrdoruesit n\u00eb rrjetin social, ku ka nj\u00eb sesion aktiv. K\u00ebshtu, sulmuesit shp\u00ebrndajn\u00eb spamin n\u00eb em\u00ebr t\u00eb p\u00ebrdoruesit ose rrisin ndjek\u00ebsit dhe like-t.\u00a0<\/p>\n
    N\u00ebse nuk e ndaloni nj\u00eb mund\u00ebsi t\u00eb till\u00eb, nj\u00eb sulmues mund t\u00eb vendos\u00eb butonin e aplikacionit tuaj n\u00eb nj\u00eb faqe t\u00eb d\u00ebmshme. Ai mund t\u00eb jet\u00eb i interesuar p\u00ebr programin tuaj t\u00eb referimit ose p\u00ebr p\u00ebrdoruesit tuaj.\u00a0\u00a0<\/p>\n
    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Dob\u00ebsia mund t\u00eb shfaqet n\u00ebse X-Frame-Options me nj\u00eb vler\u00eb n\u00eb konflikt \u00ebsht\u00eb caktuar n\u00eb serverin web ose balancuesin e ngarkes\u00ebs. N\u00eb k\u00ebt\u00eb rast, serveri dhe balancuesi thjesht do t\u00eb rifreskojn\u00eb titullin, pasi kan\u00eb prioritet m\u00eb t\u00eb lart\u00eb krahasuar me kodin e pjes\u00ebs backend.\u00a0\u00a0<\/p>\n
    Vlerat deny dhe sameorigin t\u00eb titullit X-Frame-Options do t\u00eb pengojn\u00eb funksionimin e webvizorit t\u00eb Yandex. P\u00ebr t\u00eb lejuar p\u00ebrdorimin e iframe p\u00ebr webvizorin, duhet t\u00eb shkruani nj\u00eb rregull t\u00eb ve\u00e7ant\u00eb n\u00eb konfigurime. P\u00ebr shembull, p\u00ebr nginx, mund t\u00eb konfigurohet k\u00ebshtu:<\/p>\n
    http{\n...\n map $http_referer $frame_options {\n \"~webvisor.com\" \"ALLOW-FROM http:\/\/webvisor.com\";\n default \"SAMEORIGIN\";\n }\n add_header X-Frame-Options $frame_options;\n...\n}\n\n<\/code><\/pre>\n
    \n<\/li>\n
  6. Dob\u00ebsit\u00eb PRSSI (Importimi i stilit relativ ndaj rrug\u00ebs).\u00a0\u00a0<\/b>\n
    Kjo \u00ebsht\u00eb nj\u00eb vulnerabilitet n\u00eb stilet e faqes. Ai ndodh kur p\u00ebr t\u00eb aksesuar skedar\u00ebt e stileve p\u00ebrdoren lidhje relative si href=\"\/somefolder\/styles.css\/\". Nj\u00eb sulmues do ta shfryt\u00ebzoj\u00eb k\u00ebt\u00eb, n\u00ebse gjen nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb drejtuar p\u00ebrdoruesin n\u00eb nj\u00eb faqe keqdash\u00ebse.Faqja do t\u00eb vendos\u00eb lidhjen relative n\u00eb URL-n\u00eb e saj dhe do t\u00eb imitoj\u00eb qasjen n\u00eb stilet. K\u00ebshtu do t\u00eb rezultoj\u00eb nj\u00eb k\u00ebrkes\u00eb t\u00eb ngjashme me badsite.ru\/\u2026\/somefolder\/styles.css\/, e cila n\u00ebn petkun e stilit mund t\u00eb kryej\u00eb veprime t\u00eb d\u00ebmshme.\u00a0<\/p>\n
    \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: Nj\u00eb mashtrues do t\u00eb mund ta shfryt\u00ebzoj\u00eb k\u00ebt\u00eb dob\u00ebsi n\u00ebse gjen nj\u00eb tjet\u00ebr vrim\u00eb n\u00eb siguri. Si rezultat, mund t\u00eb vjedhin t\u00eb dh\u00ebnat e p\u00ebrdoruesve nga cookie ose token\u00ebt.<\/p>\n
    \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Caktoni titullin X-Content-Type-Options: nosniff. N\u00eb k\u00ebt\u00eb rast, shfletuesi do t\u00eb kontrolloj\u00eb llojin e p\u00ebrmbajtjes p\u00ebr stilin. N\u00ebse lloji ndryshon nga text\/css, shfletuesi do t\u00eb bllokoj\u00eb k\u00ebrkes\u00ebn.\n<\/li>\n<\/ol>\n
    <\/p>\n
    Dob\u00ebsi kritike<\/h2>\n
    <\/p>\n
      \n
    1. Faqja me fush\u00ebn p\u00ebr fjal\u00ebkalim kalon nga serveri p\u00ebrmes nj\u00eb kanali t\u00eb papajisur (HTML form containing password field(s) is served over HTTP).<\/b>\n
      P\u00ebrgjigjja nga serveri n\u00eb nj\u00eb kanal t\u00eb paenkriptuar \u00ebsht\u00eb e ndjeshme ndaj sulmeve t\u00eb tipit \u00abMan in the middle\u00bb. Nj\u00eb sulmues mund t\u00eb kap\u00eb trafikun dhe t\u00eb nd\u00ebrhyj\u00eb mes klientit dhe serverit, kur faqja kalon nga serveri te klienti.\u00a0<\/p>\n
      \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: Nj\u00eb mashtrues mund t\u00eb p\u00ebrmbys\u00eb faqen dhe t'i d\u00ebrgoj\u00eb p\u00ebrdoruesit nj\u00eb formular p\u00ebr t\u00eb dh\u00ebna konfidenciale, t\u00eb cilat do t\u00eb shkojn\u00eb n\u00eb serverin e sulmuesit.\u00a0<\/p>\n
      \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Disa faqe, n\u00eb vend t\u00eb fjal\u00ebkalimit, u d\u00ebrgojn\u00eb p\u00ebrdoruesve nj\u00eb kod t\u00eb nj\u00ebhersh\u00ebm p\u00ebr email\/telefon. N\u00eb k\u00ebt\u00eb rast, ndjeshm\u00ebria nuk \u00ebsht\u00eb aq kritike, por mekanizmi do t'i komplikohet jet\u00ebn p\u00ebrdoruesve.\n<\/li>\n
    2. D\u00ebrgimi i formularit me login dhe fjal\u00ebkalim p\u00ebrmes nj\u00eb kanali t\u00eb papajisur (Login Form Is Not Submitted Via HTTPS).<\/b>\n
      N\u00eb k\u00ebt\u00eb rast, nga p\u00ebrdoruesi d\u00ebrgohet n\u00eb server nj\u00eb formular me login dhe fjal\u00ebkalim n\u00eb nj\u00eb kanal t\u00eb paenkriptuar.<\/p>\n
      \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: P\u00ebrshtatje me rastin e m\u00ebparsh\u00ebm, kjo tashm\u00eb \u00ebsht\u00eb nj\u00eb ndjeshm\u00ebri kritike. \u00cbsht\u00eb m\u00eb e leht\u00eb t\u00eb kap\u00ebsh t\u00eb dh\u00ebnat konfidenciale, pasi nuk nevojitet t\u00eb shkruani kod p\u00ebr k\u00ebt\u00eb.\u00a0\n<\/li>\n
    3. P\u00ebrdorimi i bibliotekave JavaScript me ndjeshm\u00ebri t\u00eb njohura.<\/b>\n
      Gjat\u00eb skanimit, biblioteka m\u00eb e p\u00ebrdorur u b\u00eb jQuery me nj\u00eb gam\u00eb t\u00eb gjer\u00eb versionesh. N\u00eb \u00e7do version ka t\u00eb pakt\u00ebn nj\u00eb ose m\u00eb shum\u00eb ndjeshm\u00ebri t\u00eb njohura. Ndikimi mund t\u00eb jet\u00eb i ndrysh\u00ebm - varet nga natyra e ndjeshm\u00ebris\u00eb.<\/p>\n
      \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: P\u00ebr ndjeshm\u00ebri t\u00eb njohura ka eksploitate, p\u00ebr shembull:<\/p>\n
      \"G\u00fcn\u0446\u0438\u0442\u0435
      \n
      \n\u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Kthehuni rregullisht n\u00eb ciklin: k\u00ebrkoni ndjeshm\u00ebri t\u00eb njohura \u2013 eliminohuni \u2013 kontrolloni. N\u00ebse e p\u00ebrdorni bibliotekat e p\u00ebrmendura n\u00eb m\u00ebnyr\u00eb t\u00eb q\u00ebllimshme, p\u00ebr shembull p\u00ebr t\u00eb mb\u00ebshtetur shfletuesit e vjet\u00ebr ose p\u00ebr t\u00eb kursyer buxhetin, k\u00ebrkoni mund\u00ebsi p\u00ebr t\u00eb eliminuar ndjeshm\u00ebrin\u00eb e njohur.\u00a0\n<\/li>\n
    4. Skripte nd\u00ebrfaqesh (XSS).\u00a0<\/b>
      \nCross-Site Scripting (XSS), ose skripte nd\u00ebrfaqesh, jan\u00eb sulme ndaj aplikacioneve n\u00eb ueb, kur si rezultat n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave shfaqet malware. N\u00ebse Qualys gjen nj\u00eb ndjeshm\u00ebri t\u00eb till\u00eb, do t\u00eb thot\u00eb q\u00eb nj\u00eb sulmues potencial mund t\u00eb integroj\u00eb ose tashm\u00eb ka integruar nj\u00eb skript js n\u00eb kodin e faqes p\u00ebr t\u00eb kryer veprime t\u00eb d\u00ebmshme.<\/p>\n
      XSS t\u00eb ruajtura (Stored XSS)<\/b> jan\u00eb m\u00eb t\u00eb rrezikshme, pasi skripti integron n\u00eb server dhe ekzekutohet \u00e7do her\u00eb kur hapet faqeja e sulmuar n\u00eb shfletues.<\/p>\n
      XSS t\u00eb reflektuar (Reflected XSS)<\/b> \u00ebsht\u00eb m\u00eb e leht\u00eb p\u00ebr t'u realizuar, pasi skripti keqdash\u00ebs mund t\u00eb integrohet n\u00eb k\u00ebrkes\u00ebn HTTP. Aplikacioni merr k\u00ebrkes\u00ebn HTTP, nuk verifikon t\u00eb dh\u00ebnat, i paketoni ato dhe menj\u00ebher\u00eb i d\u00ebrgon. N\u00ebse sulmuesi kap trafikun dhe vendos nj\u00eb skript t\u00eb till\u00eb <\/p>\n
      <script>\/*+\u0447\u0442\u043e+\u0442\u043e+\u043f\u043b\u043e\u0445\u043e\u0435+*\/<\/script> <\/code><\/pre>\n
      \nat\u00ebher\u00eb do t\u00eb d\u00ebrgohet nj\u00eb k\u00ebrkes\u00eb keqdash\u00ebse sipas emrit t\u00eb klientit.<\/p>\n
      Nj\u00eb shembull i qart\u00eb i XSS: js-sniffers, t\u00eb cil\u00ebt imitojn\u00eb faqet p\u00ebr futjen e CVC, t\u00eb dat\u00ebs s\u00eb skadenc\u00ebs s\u00eb kart\u00ebs dhe k\u00ebshtu me radh\u00eb.\u00a0<\/p>\n
      \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: N\u00eb titullin Content-Security-Policy p\u00ebrdorni atributin script-src, n\u00eb m\u00ebnyr\u00eb q\u00eb shfletuesi i klientit t\u00eb ngarkoj\u00eb dhe ekzekutoj\u00eb vet\u00ebm kodin nga nj\u00eb burim t\u00eb besuesh\u00ebm. P\u00ebr shembull, script-src 'self' autorizon t\u00eb gjitha skriptet vet\u00ebm nga faqja jon\u00eb.\u00a0
      \nPraktika m\u00eb e mir\u00eb \u00ebsht\u00eb kodimi Inline: lejoni vet\u00ebm javascript-in inline me vler\u00ebn unsafe-inline. Kjo vler\u00eb lejon p\u00ebrdorimin e js\/css inline, por nuk ndalon lidhjen e skedar\u00ebve js. N\u00eb kombinim me script-src 'self', ne ndalojm\u00eb ekzekutimin e skripteve t\u00eb jashtme.<\/p>\n
      Sigurohuni q\u00eb t\u00eb regjistroni gjith\u00e7ka me report-uri dhe shqyrtoni p\u00ebrpjekjet p\u00ebr integrimin n\u00eb faqe.\n<\/li>\n
    5. SQL-injeksionet.<\/b>
      \nNdjeshm\u00ebria flet p\u00ebr mund\u00ebsin\u00eb e integrimit t\u00eb kodit SQL n\u00eb faqen e internetit, i cili i qaset direkt baz\u00ebs s\u00eb t\u00eb dh\u00ebnave t\u00eb faqes. SQL-injeksioni \u00ebsht\u00eb i mundur, n\u00ebse t\u00eb dh\u00ebnat nga p\u00ebrdoruesi nuk b\u00ebhen escaping: nuk kontrollohen p\u00ebr sakt\u00ebsi dhe p\u00ebrdoren direkt n\u00eb k\u00ebrkes\u00eb. P\u00ebr shembull, k\u00ebshtu ndodh, n\u00ebse formulari n\u00eb faqen e internetit nuk kontrollon p\u00ebrputhshm\u00ebrin\u00eb e hyrjes me tipin e t\u00eb dh\u00ebnave.\u00a0<\/p>\n
      \u00c7far\u00eb \u00ebsht\u00eb e rrezikshme<\/b>: N\u00ebse nj\u00eb sulmues fut nj\u00eb k\u00ebrkes\u00eb SQL n\u00eb nj\u00eb formular t\u00eb till\u00eb, ai mund t\u00eb rr\u00ebzoj\u00eb baz\u00ebn e t\u00eb dh\u00ebnave ose t\u00eb nxjerr\u00eb informacione konfidenciale.\u00a0<\/p>\n
      \u00c7far\u00eb duhet t\u00eb mbaj\u00eb mend nj\u00eb zhvillues i uebit<\/b>: Mos i besoni asaj q\u00eb vjen nga shfletuesi. Duhet t\u00eb mbroheni si n\u00eb an\u00ebn e klientit, ashtu edhe n\u00eb an\u00ebn e serverit.\u00a0<\/p>\n
      N\u00eb an\u00ebn e klientit shkruani nj\u00eb kontroll t\u00eb fushave me JavaScript.\u00a0<\/p>\n
      Funksionet e integruara n\u00eb framework\u00ebt e njohura gjithashtu ndihmojn\u00eb n\u00eb escaping simbolet e dyshimta n\u00eb server. N\u00eb server gjithashtu rekomandohet p\u00ebrdorimi i k\u00ebrkesave parametrike n\u00eb bazat e t\u00eb dh\u00ebnave.<\/p>\n
      P\u00ebrcaktoni se ku ndodh nd\u00ebrveprimi me baz\u00ebn e t\u00eb dh\u00ebnave n\u00eb aplikacionin web.\u00a0<\/p>\n
      Nd\u00ebrveprimi ndodh kur marrim ndonj\u00eb informacion: k\u00ebrkesa me id (ndryshimi i id), krijimi i nj\u00eb p\u00ebrdoruesi t\u00eb ri, nj\u00eb koment t\u00eb ri - regjistrime t\u00eb reja n\u00eb baz\u00eb. K\u00ebtu mund t\u00eb ndodhin SQL-injeksione. Edhe n\u00ebse e largojm\u00eb nj\u00eb regjistrim nga baza, ndiqet SQL-injeksioni.\n<\/li>\n<\/ol>\n
      <\/p>\n
      Rekomandime t\u00eb P\u00ebrgjithshme<\/h2>\n
      \nMos shpikni bi\u00e7iklet\u00ebn - p\u00ebrdorni framework\u00eb t\u00eb provuar<\/b>. Zakonisht, framework-et e njohura jan\u00eb m\u00eb t\u00eb sigurta. P\u00ebr .NET \u2013 \u00ebsht\u00eb ASP.NET MVC dhe ASP.NET Core, p\u00ebr Python \u2013 Django ose Flask, p\u00ebr Ruby \u2013 Ruby on Rails, p\u00ebr PHP \u2013 Symfony, Laravel, Yii, p\u00ebr JavaScript \u2013 Node.JS- Express.js, p\u00ebr Java \u2013 Spring MVC.<\/p>\n
      Mbani nj\u00eb sy mbi p\u00ebrdit\u00ebsimet e furnizuesit dhe p\u00ebrdit\u00ebsoni rregullisht.<\/b>. Do t\u00eb zbulohet nj\u00eb dob\u00ebsi, pastaj do t\u00eb shkruhet nj\u00eb eksploatues, do t\u00eb publikohet p\u00ebr publikun, dhe gjith\u00e7ka do t\u00eb p\u00ebrs\u00ebritet s\u00ebrish. Abonohuni p\u00ebr p\u00ebrdit\u00ebsimet deri n\u00eb versionet stabile nga furnizuesi i softuerit.<\/p>\n
      Kontrolloni t\u00eb drejtat e aksesit.<\/b>. Nga ana e serverit, gjithmon\u00eb duhet ta trajtoni kodin tuaj sikur ai t\u00eb jet\u00eb shkruar nga armiku juaj m\u00eb i urryer, q\u00eb d\u00ebshiron t\u00eb d\u00ebmtoj\u00eb faqen tuaj dhe t\u00eb d\u00ebmtoj\u00eb integritetin e t\u00eb dh\u00ebnave tuaja. Aq m\u00eb tep\u00ebr, ndonj\u00ebher\u00eb kjo v\u00ebrtet ndodh.<\/p>\n
      P\u00ebrdorni klon\u00eb, ambiente testimi, dhe pastaj aplikoni n\u00eb prodhim.<\/b>. Kjo do t\u00eb ndihmoj\u00eb, s\u00eb pari, t\u00eb evitoni gabime dhe l\u00ebshime n\u00eb ambientin e prodhimit: ambienti i prodhimit sjell para, nd\u00ebrprerja e ambientit t\u00eb prodhimit \u00ebsht\u00eb kritike. Kur shtoni, rregulloni apo zgjidhni ndonj\u00eb problem, duhet t\u00eb kryeni punime n\u00eb ambientin testues, pastaj t\u00eb kontrolloni funksionalitetin dhe dob\u00ebsit\u00eb e gjetura, dhe m\u00eb pas t\u00eb planifikoni pun\u00ebt n\u00eb ambientin e prodhimit.\u00a0<\/p>\n
      Mbroni aplikacionin web me Web Application Firewall<\/a><\/noindex> dhe integrojeni me raportet nga skaneri i dob\u00ebsive.<\/b>. P\u00ebr shembull, n\u00eb DataLine, si lidhje sh\u00ebrbimesh p\u00ebrdoren Qualys dhe FortiWeb.
      \n
      Burimi:       habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
      \u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u0433\u043e\u0434 \u043d\u0430\u0437\u0430\u0434 \u043c\u044b \u0432 DataLine \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0441\u0435\u0440\u0432\u0438\u0441 \u0434\u043b\u044f \u043f\u043e\u0438\u0441\u043a\u0430 \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 \u0418\u0422-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u0445. \u0412 \u043e\u0441\u043d\u043e\u0432\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u2013 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Qualys, \u043f\u0440\u043e \u0440\u0430\u0431\u043e\u0442\u0443 \u043a\u043e\u0442\u043e\u0440\u043e\u0433\u043e \u043c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u043b\u0438. \u0417\u0430 \u0433\u043e\u0434 \u0440\u0430\u0431\u043e\u0442\u044b \u0441 \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u043c\u044b \u043f\u0440\u043e\u0432\u0435\u043b\u0438 291 \u0441\u043a\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u0434\u043b\u044f \u0440\u0430\u0437\u043d\u044b\u0445 \u0441\u0430\u0439\u0442\u043e\u0432 \u0438 \u043d\u0430\u043a\u043e\u043f\u0438\u043b\u0438 \u0441\u0442\u0430\u0442\u0438\u0441\u0442\u0438\u043a\u0443 \u043f\u043e \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u043d\u044b\u043c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u043c \u0432 \u0432\u0435\u0431-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u0445.\u00a0 \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u043d\u0438\u0436\u0435 \u044f \u043f\u043e\u043a\u0430\u0436\u0443, \u043a\u0430\u043a\u0438\u0435 \u0438\u043c\u0435\u043d\u043d\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":84185,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-84184","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\udd47Gjat\u00eb gabueseve fatale t\u00eb siguris\u00eb s\u00eb faqes: \u00e7far\u00eb kemi m\u00ebsuar nga statistika e skanerit t\u00eb dob\u00ebsive p\u00ebr nj\u00eb vit | ProHoster","description":"Rreth nj\u00eb vit m\u00eb par\u00eb, ne n\u00eb DataLine lancuam nj\u00eb sh\u00ebrbim p\u00ebr t\u00eb k\u00ebrkuar dhe analizuar dob\u00ebsit\u00eb n\u00eb aplikacionet IT.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/smertnye-grehi-bezopasnosti-sajta-chto-my-uznali-iz-statistiki-skanera-uyazvimostej-za-god","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\u0421\u043c\u0435\u0440\u0442\u043d\u044b\u0435 \u0433\u0440\u0435\u0445\u0438 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0441\u0430\u0439\u0442\u0430: \u0447\u0442\u043e \u043c\u044b \u0443\u0437\u043d\u0430\u043b\u0438 \u0438\u0437 \u0441\u0442\u0430\u0442\u0438\u0441\u0442\u0438\u043a\u0438 \u0441\u043a\u0430\u043d\u0435\u0440\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0437\u0430 \u0433\u043e\u0434 | ProHoster","og:description":"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u0433\u043e\u0434 \u043d\u0430\u0437\u0430\u0434 \u043c\u044b \u0432 DataLine \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0441\u0435\u0440\u0432\u0438\u0441 \u0434\u043b\u044f \u043f\u043e\u0438\u0441\u043a\u0430 \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 \u0418\u0422-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u0445.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/smertnye-grehi-bezopasnosti-sajta-chto-my-uznali-iz-statistiki-skanera-uyazvimostej-za-god","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":"2020-06-05T17:42:31+00:00","article:modified_time":"2020-06-05T17:42:31+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"84184","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 15:03:50","updated":"2022-09-30 12:56: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\/84184","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=84184"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/84184\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/84185"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=84184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=84184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=84184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}