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

# Mimecast integratsiyasini sozlash

> Elektron pochta orqali keladigan tahdidlar, bosishlar, yetkazib berish va ma’lumotlarni himoya qilish bo‘yicha faoliyat haqidagi ma’lumotlarni olish uchun Mimecast’ni Living Security bilan 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 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="Mimecast" recommendDelegated={true} />

## Ushbu integratsiya nimani taqdim etadi

Mimecast elektron pochta orqali keladigan tahdidlar, bosishlar, yetkazib berish va ma’lumotlarni himoya qilish bo‘yicha normallashtirilgan faoliyat ma’lumotlarini taqdim etishi mumkin. Ko‘rib chiqilgan misollar:

* `phishing.real.clicked` — haqiqiy fishing xatlaridagi havolalarni bosadi
* `data.transfer.blocked` — ma’lumotlarni uzatish bloklandi
* `phishing.real.delivered` — haqiqiy fishing xati kiruvchi xatlar jildiga yetkazildi

[Integratsiya ma’lumotlari qanday qilib Signals’ga aylanishi](/uz/signals/data-sources) haqida ko‘ring.

## Living Security uchun nima talab qilinadi

| Hisob ma’lumoti | Tavsif |
| - | - |
| **Client ID** | Mimecast API 2.0 xizmat ilovasining identifikatori. |
| **Client secret** | Ushbu xizmat ilovasining maxfiy kaliti. |

Ilovaga **Monitoring → URL Protection → Read** ruxsatini o‘z ichiga olgan rolni tayinlang. Living Security OAuth 2.0 client-credentials oqimidan foydalanadi va URL Protection bosishlar jurnallarini o‘qiydi.

## Sozlash

<Steps>
  <Step title="Mimecast xizmat ilovasini yaratish">
    Mimecast Administration Console’da Living Security uchun API 2.0 xizmat ilovasini yarating va client-credentials grant turidan foydalaning.
  </Step>

  <Step title="Minimal o‘qish ruxsatini tayinlash">
    **Monitoring → URL Protection → Read** ruxsatini o‘z ichiga olgan rolni tayinlang, so‘ngra client ID va client secret qiymatlarini yozib oling.
  </Step>

  <ConnectInPlatform tile="Mimecast">
    Client ID va client secret qiymatlarini kiriting, so‘ngra ulang.
  </ConnectInPlatform>
</Steps>

## Tekshirish va nosozliklarni bartaraf etish

Ulanish URL Protection jurnallarini o‘qiy olishini tekshiring. Yaqinda himoyalangan havolalar bosilmagan bo‘lsa, birinchi natijaning bo‘sh bo‘lishi kutilgan holatdir.

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Client ID yoki maxfiy kalit yaroqsiz yoxud xizmat ilovasi o‘chirilgan. Zarur bo‘lsa, maxfiy kalitni almashtiring va qayta ulang.
  </Accordion>

  <Accordion title="403 Forbidden">
    Xizmat ilovasiga tayinlangan rol **Monitoring → URL Protection → Read** ruxsatini o‘z ichiga olganiga ishonch hosil qiling.
  </Accordion>

  <Accordion title="No click activity">
    URL Protection tegishli pochta oqimi uchun yoqilganiga va rol so‘rov yuborilayotgan hisobga nisbatan qo‘llanilishiga ishonch hosil qiling.
  </Accordion>
</AccordionGroup>

Endpoint ruxsati haqida ma’lumot olish uchun [Mimecast’ning URL Protection jurnali bo‘yicha qo‘llanmasi](https://developer.services.mimecast.com/docs/securityevents/1/routes/api%2Fttp%2Furl%2Fget-logs/post)ga qarang.

<PublicIntegrationNextSteps />


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