> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cofense Triage integratsiyasini sozlash

> Xodimlar tomonidan xabar qilingan elektron pochta xabarlari va tekshiruv natijalari (Outcomes) uchun Cofense Triage'ni Living Security bilan ulang.

export const EgressIpAllowlistBothSets = ({system}) => <Warning>
    <strong>{system} uchun bitta emas, ikki guruh manzil kerak.</strong> Living Security ushbu integratsiyaning kirish tokenini o‘z infratuzilmasida yaratadi va uni uzluksiz yangilab turadi, shu sababli sozlash trafigi va sinxronizatsiya trafigi turli tarmoqlardan chiqadi. Ikkala guruhni ham {system} tizimidagi ruxsat etilganlar ro‘yxatiga kiriting va ikkalasini ham saqlab qo‘ying — bu faqat sozlash bosqichiga tegishli talab emas.
    <br />
    <br />
    <strong>Integratsiya sinxronizatsiyasi trafigi</strong> — barcha mintaqalarda bir xil:
    <br />
    <code>52.34.139.153/32</code>, <code>54.69.127.183/32</code>, <code>44.247.133.183/32</code>,{' '}
    <code>52.26.211.56/32</code>
    <br />
    <br />
    <strong>Platforma trafigi</strong> — faqat tashkilotingiz joylashgan mintaqaga tegishli qatordan foydalaning:
    <br />
    AQSh: <code>98.91.60.249/32</code>, <code>13.216.91.102/32</code>
    <br />
    Yevropa Ittifoqi: <code>34.246.236.210/32</code>, <code>52.31.102.238/32</code>
    <br />
    <br />
    Faqat sinxronizatsiya guruhi ruxsat etilsa, sozlash hech qachon yakunlanmaydi. Faqat platforma guruhi ruxsat etilsa, sozlash muvaffaqiyatli bo‘ladi, ammo barcha sinxronizatsiyalar xato bilan tugaydi. Ikkala nosozlik belgilari va o‘zgartirish siyosati bo‘yicha{' '}
    <a href="/uz/integrations/managing/egress-ip-addresses">
      Configuring Integration Egress IP Addresses
    </a>{' '}
    bo‘limiga qarang.
  </Warning>;

export const PublicIntegrationNextSteps = () => <>
    <hr />
    <h2>Tegishli resurslar</h2>
    <ul>
      <li>
        <a href="/uz/signals/data-sources">Integrations ma'lumotlari Human Risk Management signallariga qanday aylanishini bilib oling</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/integrations">Living Security integratsiyalarini o'rganing</a>
      </li>
      <li>
        <a href="https://app.livingsecurity.ai/">Living Security Platform'ni oching</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/request-demo/">Living Security demosini so'rang</a>
      </li>
    </ul>
  </>;

export const ConnectInPlatform = ({tile, children}) => <Step title="Living Security Platform'da hisob ma'lumotlarini kiriting">
    <p>
      Living Security'ga kirish huquqiga ega bo'lgan shaxs — dastur egasi yoki (agar taklif qilingan bo'lsa)
      tizim administratori tomonidan bajariladi (topshirilgan sozlash).
    </p>
    <ol>
      <li>
        <strong>Settings → Integrations → Catalog</strong> bo'limiga o'ting, <strong>{tile}</strong>{' '}
        kartasini toping va <strong>Connect</strong> tugmasini bosing.
      </li>
      <li>
        Quyidagi maydonlarni to'ldiring, so'ng <strong>Connect</strong> tugmasini bosing.
      </li>
    </ol>
    {children}
  </Step>;

export const SystemAdminBanner = ({system, recommendDelegated}) => <Note>
    <p>
      <strong>Ushbu qo‘llanma {system} administratoriga mo‘ljallangan.</strong> Unda {system} ichida API
      hisob ma’lumotlarini yaratish tartibi bayon etilgan; buning uchun {system} tizimiga administrator
      sifatida kirish huquqi talab etiladi, Living Security Platform’ga esa talab etilmaydi.
    </p>
    <p>
      Agar siz Living Security’da <strong>dastur egasi</strong> bo‘lsangiz va {system} tizimini
      boshqarmasangiz, ushbu sahifani uni boshqaradigan shaxsga yuboring. U A qismini bajaradi va hisob ma’lumotlarini sizga qaytaradi
      (yoki agar siz uni platformaga taklif qilgan bo‘lsangiz, ularni bevosita o‘zi kiritadi).
      {recommendDelegated && <>
          {' '}Sozlash jarayonida maxfiy kalit ma’lumotlari hosil bo‘lgani uchun, maxfiy kalit sizga qayta yuborilmasligi uchun{' '}
          <strong>delegated setup</strong> usulidan foydalanishni tavsiya etamiz.
        </>}
    </p>
  </Note>;

<SystemAdminBanner system="Cofense Triage" recommendDelegated={true} />

## Ushbu integratsiya nimani taqdim etadi

Cofense Triage xodimlar tomonidan xabar qilingan elektron pochta xabarlari va tekshiruv natijalari (Outcomes) bo‘yicha normallashtirilgan ma’lumotlarni taqdim etishi mumkin. Ko‘rib chiqilgan misollar quyidagilarni o‘z ichiga oladi:

* `phishing.real.reported` — haqiqiy fishing xatlari haqida xabar beradi
* `email.suspicious.reported` — shubhali elektron xatlar haqida xabar beradi
* `phishing.real.targeted` — haqiqiy fishing kampaniyalari nishoniga aylangan

[Integratsiya ma’lumotlari qanday qilib Signals’ga aylanishi](/uz/signals/data-sources) bilan tanishing.

## Sizga nima kerak

Cofense Triage OAuth2 client credentials usulidan foydalanadi. Triage tenantingizda API ilovasini yarating va uning client ID hamda client secret qiymatlarini nusxalang. Brauzerda rozilik berish bosqichi yo‘q — ikkala qiymatni Living Security’ga kiritasiz, token so‘rovini esa tizimning o‘zi yuboradi.

## Sozlash

<Steps>
  <Step title="Alohida Cofense credential yarating">
    Cofense Triage’da hisobotlarni o‘qiy oladigan API ilovasini yarating. Credential faqat hisobotlarga kirish bilan cheklansin. **client ID** va **client secret** qiymatlarini yozib oling — Triage secret qiymatini faqat bir marta ko‘rsatadi.
  </Step>

  <Step title="Triage hostname’ini tasdiqlang">
    Tenantingizning to‘liq hostname’ini, masalan `acme.managedphishme.com` yoki Cofense muhitingizga berilgan hostname’ni yozib oling. Living Security’ga kiritishda `https://` qismini qoldirib ketiling.
  </Step>

  <ConnectInPlatform tile="Cofense Triage">
    **Client ID**, **Client secret** va **Triage hostname** qiymatlarini kiriting.
  </ConnectInPlatform>
</Steps>

## Tekshirish va nosozliklarni bartaraf etish

Birinchi sinxronlashni kutishdan oldin ulanish testi joriy foydalanuvchi va hisobotlarni o‘qiy olishini tekshiring.

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Client secret qiymatini almashtiring — u yangilangan yoki bekor qilingan bo‘lishi mumkin. Hostname credential bergan tenantga tegishli ekanini tasdiqlang.
  </Accordion>

  <Accordion title="403 Forbidden">
    Credential hisobotlarni o‘qiy olmaydi. Cofense tenantingiz talab qiladigan minimal hisobot ruxsatini bering, so‘ng qayta ulaning.
  </Accordion>

  <Accordion title="Triage hostname’iga ulanib bo‘lmayapti">
    Agar Triage tenantingiz API’ga kirishni manba IP manzili bo‘yicha cheklasa, ushbu integratsiya uchun manzillarning **ikki** to‘plami ruxsat etilganlar ro‘yxatiga kiritilishi kerak. Living Security access token’ni o‘zi yaratadi va uni uzluksiz yangilab turadi, shuning uchun token so‘rovlari va rejalashtirilgan sinxronlashlar turli tarmoqlardan yuboriladi — Triage’da esa ular bir xil hostname’ga yetib boradi.

    <EgressIpAllowlistBothSets system="Cofense Triage" />
  </Accordion>

  <Accordion title="Hisobotlar ko‘rinadi, lekin xabar beruvchilar ko‘rinmaydi">
    Xabar beruvchilar bo‘yicha boyitish faqat reporter endpoint’ini taqdim etadigan ulanish variantlarida mavjud. Hisobotlardan olingan Signals esa qo‘llab-quvvatlanadigan hisobot ma’lumotlari asosida baribir to‘ldirilishi mumkin.
  </Accordion>
</AccordionGroup>

<PublicIntegrationNextSteps />


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.