> ## 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.

# Abnormal Security integratsiyasini sozlash

> Elektron pochta tahdidlari va fishing kampaniyalari ma’lumotlarini import qilish uchun Abnormal Security’ni ulang.

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 EgressIpSafelist = ({system}) => <Note>
    <strong>Living Security sinxronizatsiyasining to‘rttala chiquvchi (egress) IP manzilini ham</strong> {system} tizimidagi ruxsat etilganlar ro‘yxatiga (allowlist) qo‘shing.{' '}
    Agar {system} CIDR yozuvini talab qilsa, har birini <code>/32</code> bilan alohida xost sifatida kiriting:
    <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 />
    Trafik to‘rttasining istalganidan chiqishi mumkin, shuning uchun ularning faqat bir qismini ruxsat etilganlar ro‘yxatiga kiritish sinxronizatsiyada vaqti-vaqti bilan uzilishlarga sabab bo‘ladi. Bu to‘rtta manzil Living Security’ning barcha mintaqalarida bir xil. To‘liq ro‘yxat, o‘zgartirish siyosati va nosozliklarni bartaraf etish bo‘yicha{' '}
    <a href="/uz/integrations/managing/egress-ip-addresses">
      Configuring Integration Egress IP Addresses
    </a>{' '}
    bo‘limiga qarang.
  </Note>;

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="Abnormal Security" />

## Ushbu integratsiya nimalarni taqdim etadi

Abnormal Security normallashtirilgan elektron pochta tahdidlari, yetkazib berish, bloklash va xodimlar tomonidan xabar berish faoliyati haqidagi ma’lumotlarni taqdim etishi mumkin. Ko‘rib chiqilgan misollar:

* `phishing.real.blocked` — yetkazib berilishidan oldin bloklangan haqiqiy fishing
* `phishing.real.delivered` — kirish qutisiga yetkazib berilgan haqiqiy fishing
* `phishing.real.reported` — haqiqiy fishing xatlari haqida xabar beradi

Ushbu misollar Living Security foydalana oladigan normallashtirilgan faoliyat turlarini ko‘rsatadi. [Integratsiya ma’lumotlari qanday qilib Signals’ga aylanishi](/uz/signals/data-sources) bilan tanishing.

## Living Security uchun nima talab qilinadi

| Credential | Description |
| - | - |
| **API key** | Abnormal Portal orqali yaratilgan REST API bearer tokeni |
| **Regional API host** | Abnormal Security muhitingiz uchun xost nomi |

**Scopes:** `Abuse Campaigns (AI Security Mailbox)` va `Threats` uchun **Read** huquqi bilan Custom Access

**Talab etiladigan rol:** Abnormal Security’da **Security Admin** yoki **Super Admin**

### Old shartlar

* API tokenlarini yaratish va boshqarish uchun Abnormal Security’da sizda **Security Admin** yoki **Super Admin** huquqi bo‘lishi kerak.

***

## A qism — Abnormal Security’da

*Ushbu amallarni Abnormal Security administratoringiz bajaradi.*

<Steps>
  <Step title="API Token Management bo‘limiga o‘tish">
    1. Abnormal Security portaliga kiring.
    2. Chap navigatsiya panelida **Settings** tugmasini bosing, so‘ng **Integrations** bandini tanlang.

    <img src="https://mintcdn.com/livingsecurity/TnbD8Y_d8KdapRc2/integrations/images/abnormal-security/settings-integrations.webp?fit=max&auto=format&n=TnbD8Y_d8KdapRc2&q=85&s=7f5d7a616acdcf72a9048f16c6706b5e" alt="Integrations bandi ko‘rsatilgan Abnormal Security Settings menyusi" width="1999" height="1680" data-path="integrations/images/abnormal-security/settings-integrations.webp" />

    3. Integrations sahifasining pastki qismidagi **API Token Management** bo‘limigacha pastga aylantiring.
    4. **+ Create New Token** tugmasini bosing.

    <img src="https://mintcdn.com/livingsecurity/TnbD8Y_d8KdapRc2/integrations/images/abnormal-security/api-token-management.avif?fit=max&auto=format&n=TnbD8Y_d8KdapRc2&q=85&s=13cfdfb7ced9b3f3fca67c781ee7e844" alt="Create New Token tugmasi ko‘rsatilgan API Token Management bo‘limi" width="1239" height="1151" data-path="integrations/images/abnormal-security/api-token-management.avif" />
  </Step>

  <Step title="Integratsiya turini tanlash">
    Integratsiya turi sifatida **REST API** ni tanlang, so‘ng **Next** tugmasini bosing.
  </Step>

  <Step title="Token qamrovini tanlash">
    Token qamrovini tanlang, so‘ng **Next** tugmasini bosing:

    * **Customer (All Current and Future Tenants)** — Abnormal hisobingiz bir nechta tenantni boshqarsa, shuni tanlang. Bu token barcha mavjud va kelajakdagi tenantlarni avtomatik qamrab oladi.
    * **Tenant (Single Tenant)** — Tokenni bitta aniq tenant bilan cheklash uchun shuni tanlang.

    Bitta Abnormal tenantiga ega ko‘pchilik tashkilotlar uchun ikkala variant ham mos keladi. Ikkilansangiz, **Customer** ni tanlang.
  </Step>

  <Step title="Kerakli kirish huquqini berish">
    **Custom Access** ni tanlang va ikkala endpoint guruhi uchun **Read** ni yoqing:

    | Endpoint group | Required access level |
    | - | - |
    | **Abuse Campaigns (AI Security Mailbox)** | Read |
    | **Threats** | Read |

    So‘ng **Next** tugmasini bosing.

    <Note>
      **Read** huquqi maxfiy bo‘lmagan tahdid va kampaniya ma’lumotlarini qaytaradi. **Read Sensitive** qo‘shimcha ravishda PII, ilovalar va xodimlar ma’lumotlarini ham ochib beradi. **Write** bartaraf etish amallarini yuboradi. Foydalanish holatingiz aniq ravishda ko‘proq talab qilmasa, faqat **Read** huquqini bering.
    </Note>
  </Step>

  <Step title="Token tafsilotlari va IP safelist’ni sozlash">
    Quyidagi maydonlarni to‘ldiring:

    * **Token Name** — Ta’riflovchi nom (masalan, `Living Security Platform`)
    * **Description** — Ixtiyoriy izoh (masalan, `Read access for Living Security HRM platform`)
    * **Token Expiry** — Almashtirish siyosatingizga mos ravishda **90**, **180** yoki **365 days** ni tanlang. Token muddati tugashidan oldin uni almashtirish uchun kalendarda eslatma o‘rnating.
    * **IP Safelist** — Living Security egress IP diapazonlarini har bir yozuvga bittadan kiriting. Har biridan keyin **Add** tugmasini bosing.

    <EgressIpSafelist system="Abnormal Security" />

    <Warning>
      **IP safelist majburiy.** Abnormal Security safelist’da bo‘lmagan manzillardan kelgan barcha API so‘rovlarini rad etadi. Ulanish oynasi muvaffaqiyatli yakunlanadi, biroq to‘g‘ri IP manzillar safelist’ga kiritilmaguncha ma’lumotlar sinxronizatsiyasi `401 Unauthorized` xatosi bilan bajarilmaydi.
    </Warning>

    So‘ng **Next** tugmasini bosing.
  </Step>

  <Step title="Tokenni ko‘rib chiqish va yaratish">
    Token konfiguratsiyasining xulosasini ko‘rib chiqing, so‘ng **Create Token** tugmasini bosing.

    <img src="https://mintcdn.com/livingsecurity/TnbD8Y_d8KdapRc2/integrations/images/abnormal-security/review-token.avif?fit=max&auto=format&n=TnbD8Y_d8KdapRc2&q=85&s=6935f488f5778fcea3f6907629aa1316" alt="Token konfiguratsiyasini ko‘rib chiqish ekrani" style={{maxWidth: "550px"}} width="1910" height="726" data-path="integrations/images/abnormal-security/review-token.avif" />
  </Step>

  <Step title="Tokenni nusxalash va saqlash">
    **Tokenni darhol nusxalang** va xavfsiz joyda (masalan, parollar seyfi yoki maxfiy ma’lumotlar menejerida) saqlang, so‘ng **Done** tugmasini bosing.

    <img src="https://mintcdn.com/livingsecurity/TnbD8Y_d8KdapRc2/integrations/images/abnormal-security/copy-token.avif?fit=max&auto=format&n=TnbD8Y_d8KdapRc2&q=85&s=fa752c333af664ad5b3ed037dbb67143" alt="Yaratilgan token ko‘rsatilgan tokenni nusxalash oynasi" style={{maxWidth: "550px"}} width="1999" height="329" data-path="integrations/images/abnormal-security/copy-token.avif" />

    <Warning>
      Abnormal Portal token qiymatini **faqat bir marta** ko‘rsatadi. Uni nusxalamasdan boshqa sahifaga o‘tib ketsangiz, yangi token yaratishingiz va eskisini bekor qilishingiz kerak bo‘ladi.
    </Warning>
  </Step>

  <Step title="Regional API xostini aniqlash">
    Abnormal Security muhitingiz uchun to‘g‘ri API xostini aniqlang:

    | Environment | Regional API host |
    | - | - |
    | Default (US commercial) | `api.abnormalplatform.com` |
    | EU | `eu.rest.abnormalsecurity.com` |
    | FedRAMP | `rest.abnormalsecurity.us` |

    **Faqat xostni** kiriting — `https://` prefiksisiz va oxirida slashsiz.

    Tashkilotingiz qaysi muhitdan foydalanishiga ishonchingiz komil bo‘lmasa, Abnormal portalingiz URL manzilini tekshiring yoki Abnormal Security hisob jamoasiga murojaat qiling.
  </Step>
</Steps>

***

## B qism — Living Security Platform’da

*Bu amalni dastur egasi yoki (vakolat berilgan sozlash ishlatilsa) tizim administratori bajaradi.*

<Steps>
  <ConnectInPlatform tile="Abnormal Security">
    | Field | Value |
    | - | - |
    | **API key** | A qismdagi 7-bosqichda nusxalangan token |
    | **Regional API host** | A qismdagi 8-bosqichdagi xost (AQSh uchun standart: `api.abnormalplatform.com`) |

    <img src="https://mintcdn.com/livingsecurity/oVkrOMkYmNevekTI/integrations/images/abnormal-security/connect-dialog.png?fit=max&auto=format&n=oVkrOMkYmNevekTI&q=85&s=46afa66685c5f59483324c863fd4fa86" alt="Abnormal Security uchun Living Security ulanish oynasi" style={{maxWidth: "450px"}} width="576" height="638" data-path="integrations/images/abnormal-security/connect-dialog.png" />
  </ConnectInPlatform>
</Steps>

Endi Abnormal Security’ga ulandingiz.

***

## Nosozliklarni bartaraf etish

<AccordionGroup>
  <Accordion title="403 Forbidden — Bu amalni bajarishga ruxsatingiz yo‘q">
    Tokenda talab etiladigan kirish huquqlaridan biri yoki ikkalasi (**Abuse Campaigns** yoki **Threats**) yo‘q. Integratsiya turi, qamrov va kirish darajasini token yaratilgandan keyin o‘zgartirib bo‘lmaydi — to‘g‘ri sozlamalar bilan yangi token yaratishingiz va eskisini bekor qilishingiz kerak.
  </Accordion>

  <Accordion title="401 Unauthorized">
    Yoki token yaroqsiz/muddati o‘tgan, yoki so‘rov yuborilgan IP safelist’da emas. Quyidagilarni tekshiring:

    1. Token bekor qilinmagan yoki muddati tugamagan
    2. [Living Security egress IP manzillari](/uz/integrations/managing/egress-ip-addresses)ning barchasi to‘rttasi safelist’da mavjud

    Agar sinxronizatsiya ilgari ishlagan, hozir esa `401` xatosi bilan bajarilmayotgan bo‘lsa, egress IP manzillari o‘zgargan bo‘lishi mumkin — [Integratsiya egress IP manzillarini sozlash](/uz/integrations/managing/egress-ip-addresses) sahifasini ko‘rib chiqing va safelist unga mos ekanini tekshiring.
  </Accordion>

  <Accordion title="Eski tokenlar muddati tugashi (2027-yil 30-aprel)">
    Tashkilotingizda o‘z-o‘ziga xizmat ko‘rsatuvchi Token Management imkoniyati joriy etilishidan oldin yaratilgan API tokenlari bo‘lsa, ular dashboard’da **Legacy** sifatida ko‘rinadi. Legacy tokenlar ishlashda davom etadi, biroq ularni almashtirib bo‘lmaydi — faqat ularning IP safelist’ini yangilash mumkin. Barcha legacy tokenlarning muddati **2027-yil 30-aprel** kuni avtomatik ravishda tugaydi. Legacy tokenlarni shu sanadan oldin yangi tokenlar bilan almashtirishni rejalashtiring.
  </Accordion>
</AccordionGroup>

<PublicIntegrationNextSteps />


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