{"id":161,"date":"2026-10-17T09:01:08","date_gmt":"2026-10-17T06:01:08","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/kurumsal-epostada-yetkilendirme-least-privilege-shared-mailbox-delegate-send-as\/"},"modified":"2026-10-17T09:01:08","modified_gmt":"2026-10-17T06:01:08","slug":"kurumsal-epostada-yetkilendirme-least-privilege-shared-mailbox-delegate-send-as","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/kurumsal-epostada-yetkilendirme-least-privilege-shared-mailbox-delegate-send-as\/","title":{"rendered":"Kurumsal E-Postada Yetkilendirme ve \u201cLeast Privilege\u201d Rehberi: Shared Mailbox, Delegate, Send As, Send on Behalf ve Klas\u00f6r Payla\u015f\u0131m\u0131"},"content":{"rendered":"<h2>Neden \u201cleast privilege\u201d (en az yetki) kurumsal e-postada kritiktir?<\/h2>\n<p>Kurumsal e-posta hesaplar\u0131; teklif, fatura, m\u00fc\u015fteri yaz\u0131\u015fmalar\u0131, s\u00f6zle\u015fme ekleri ve eri\u015fim ba\u011flant\u0131lar\u0131 gibi y\u00fcksek de\u011ferli i\u00e7erikler ta\u015f\u0131r. Bu nedenle e-posta yetkilendirmesi \u201ckim kime, ne kadar ve ne kadar s\u00fcreyle eri\u015fecek?\u201d sorular\u0131na net cevaplar vermelidir. En az yetki prensibi, bir ki\u015finin i\u015fini yapmas\u0131 i\u00e7in gerekli minimum eri\u015fimi vermeyi hedefler. B\u00f6ylece hem hata riski hem de k\u00f6t\u00fcye kullan\u0131m etkisi s\u0131n\u0131rlan\u0131r.<\/p>\n<p>Pratikte en yayg\u0131n sorun \u015fudur: Bir i\u015fi h\u0131zland\u0131rmak i\u00e7in fazla yetki verilir (\u00f6rne\u011fin t\u00fcm posta kutusuna tam eri\u015fim) ve bu yetki daha sonra geri al\u0131nmaz. Zamanla hesaplar, ekipler de\u011fi\u015fir; eski yetkiler unutulur ve kurumun sald\u0131r\u0131 y\u00fczeyi b\u00fcy\u00fcr. Do\u011fru model se\u00e7imi, d\u00fczenli g\u00f6zden ge\u00e7irme ve kay\u0131t alt\u0131na alma ile bu riskler azalt\u0131labilir.<\/p>\n<h2>Temel eri\u015fim modelleri: Ayn\u0131 ama\u00e7 i\u00e7in farkl\u0131 ara\u00e7lar<\/h2>\n<p>Kurumsal e-posta altyap\u0131lar\u0131nda s\u0131k g\u00f6r\u00fclen eri\u015fim modelleri genelde \u015fu kavramlar\u0131n etraf\u0131nda \u015fekillenir: shared mailbox (payla\u015f\u0131ml\u0131 posta kutusu), delegasyon (tam eri\u015fim veya belirli yetkiler), \u201cSend As\u201d, \u201cSend on Behalf\u201d, forwarding (y\u00f6nlendirme) ve klas\u00f6r payla\u015f\u0131m\u0131. Bu kavramlar benzer g\u00f6r\u00fcnse de g\u00fcvenlik, izlenebilirlik ve i\u015f ak\u0131\u015f\u0131 a\u00e7\u0131s\u0131ndan farkl\u0131 sonu\u00e7lar do\u011furur.<\/p>\n<h3>Shared mailbox (payla\u015f\u0131ml\u0131 posta kutusu) ne zaman do\u011fru se\u00e7imdir?<\/h3>\n<p>Shared mailbox genellikle bir ki\u015finin de\u011fil bir ekibin sahip oldu\u011fu adresler i\u00e7in uygundur: destek, sat\u0131\u015f, muhasebe gibi. Burada ama\u00e7, gelen kutusunun bir ki\u015fiyle \u201c\u00f6zde\u015fle\u015fmemesi\u201d ve i\u015f s\u00fcreklili\u011finin ekip \u00fczerinden y\u00fcr\u00fcmesidir. Shared yap\u0131, \u00e7al\u0131\u015fan ayr\u0131l\u0131\u015flar\u0131nda \u201ckimin kutusu?\u201d tart\u0131\u015fmas\u0131n\u0131 azalt\u0131r ve eri\u015fim y\u00f6netimini ekip \u00fcyeli\u011fi \u00fczerinden daha d\u00fczenli hale getirebilir.<\/p>\n<p>Ancak shared mailbox kullan\u0131rken de en az yetki ge\u00e7erlidir. Her ekip \u00fcyesinin her klas\u00f6re eri\u015fmesi gerekmeyebilir. \u00d6rne\u011fin muhasebe@ adresinde tahsilat, tedarik\u00e7i, bordro gibi ayr\u0131\u015fm\u0131\u015f klas\u00f6rler varsa, bordro i\u00e7eri\u011fine yaln\u0131zca belirli ki\u015filer eri\u015fmelidir.<\/p>\n<h3>Delegation (delegasyon) ve tam eri\u015fim ne zaman gerekir?<\/h3>\n<p>Delegasyon, bir kullan\u0131c\u0131n\u0131n ba\u015fka bir kullan\u0131c\u0131n\u0131n posta kutusuna eri\u015fim yetkisi almas\u0131d\u0131r. En riskli ve ayn\u0131 zamanda en g\u00fc\u00e7l\u00fc senaryo \u201ctam eri\u015fim\u201ddir; \u00e7\u00fcnk\u00fc yetki verilen ki\u015fi, posta kutusundaki \u00e7ok geni\u015f i\u00e7eriklere ula\u015fabilir. Tam eri\u015fim, yaln\u0131zca net gerek\u00e7e varsa ve s\u00fcre\/\u00e7er\u00e7eve belirlenerek verildi\u011finde anlaml\u0131d\u0131r: y\u00f6netici asistan\u0131n\u0131n ajanda ve yaz\u0131\u015fmalar\u0131 y\u00f6netmesi, ge\u00e7ici izin d\u00f6neminde kritik bir rol\u00fcn devral\u0131nmas\u0131 gibi.<\/p>\n<p>Delegasyon verirken \u015fu sorular\u0131 sormak gerekir: Ger\u00e7ekten t\u00fcm posta kutusuna m\u0131 ihtiya\u00e7 var, yoksa belirli klas\u00f6rlere mi? G\u00f6nderim yetkisi gerekiyor mu? Yetki kal\u0131c\u0131 m\u0131, s\u00fcreli mi? S\u00fcreli yetkiler i\u00e7in bir biti\u015f tarihi ve geri alma plan\u0131 mutlaka tan\u0131mlanmal\u0131d\u0131r.<\/p>\n<h3>\u201cSend As\u201d ile \u201cSend on Behalf\u201d aras\u0131ndaki fark<\/h3>\n<p>Bu iki g\u00f6nderim modeli, e-postan\u0131n al\u0131c\u0131 taraf\u0131nda \u201cg\u00f6nderenin kim g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc\u201d belirler ve yanl\u0131\u015f se\u00e7ildi\u011finde hem i\u00e7 kontrol hem de m\u00fc\u015fteri ileti\u015fimi a\u00e7\u0131s\u0131ndan sorun \u00e7\u0131karabilir.<\/p>\n<ul>\n<li><strong>Send As:<\/strong> Mesaj, do\u011frudan yetki verilen adres ad\u0131na g\u00f6nderilmi\u015f gibi g\u00f6r\u00fcn\u00fcr. \u00d6rne\u011fin ekip \u00fcyesi, destek@ ad\u0131na yan\u0131tlar ve al\u0131c\u0131 \u201cg\u00f6nderen\u201d alan\u0131nda destek@ g\u00f6r\u00fcr.<\/li>\n<li><strong>Send on Behalf:<\/strong> Mesaj, \u201cX ad\u0131na Y g\u00f6nderdi\u201d mant\u0131\u011f\u0131yla g\u00f6r\u00fcn\u00fcr. Bu, \u015feffafl\u0131k ve i\u00e7 kontrol a\u00e7\u0131s\u0131ndan baz\u0131 kurumlarda tercih edilir. M\u00fc\u015fteri ileti\u015fiminde ise kimi zaman gereksiz karma\u015fa yaratabilir.<\/li>\n<\/ul>\n<p>En az yetki a\u00e7\u0131s\u0131ndan bak\u0131ld\u0131\u011f\u0131nda; bir ki\u015finin sadece temsil yetkisine ihtiyac\u0131 varsa \u201cSend As\/On Behalf\u201d d\u00fc\u015f\u00fcn\u00fclebilir, fakat bunun yan\u0131nda gereksiz \u201ctam eri\u015fim\u201d vermek \u00e7o\u011fu zaman fazlad\u0131r. G\u00f6nderim yetkisi ile okuma\/eri\u015fim yetkisi birbirinden ayr\u0131 ele al\u0131nmal\u0131d\u0131r.<\/p>\n<h3>Klas\u00f6r payla\u015f\u0131m\u0131: T\u00fcm posta kutusunu a\u00e7madan i\u015f y\u00fcr\u00fctmek<\/h3>\n<p>Bazen ihtiya\u00e7, bir posta kutusunun tamam\u0131n\u0131 payla\u015fmak de\u011fil, yaln\u0131zca belirli klas\u00f6rlerde i\u015f yapmakt\u0131r. \u00d6rne\u011fin y\u00f6netici; \u201cS\u00f6zle\u015fmeler\u201d klas\u00f6r\u00fcn\u00fc hukuk ekibiyle, \u201cSeyahat\u201d klas\u00f6r\u00fcn\u00fc asistanla payla\u015fmak isteyebilir. Klas\u00f6r bazl\u0131 payla\u015f\u0131m, en az yetki prensibine \u00e7ok uygundur; \u00e7\u00fcnk\u00fc eri\u015fim kapsam\u0131n\u0131 daralt\u0131r.<\/p>\n<p>Bu modelin zay\u0131f taraf\u0131 operasyonel karma\u015f\u0131kl\u0131kt\u0131r: Klas\u00f6r yap\u0131s\u0131 de\u011fi\u015ftik\u00e7e yetkiler g\u00fcncellenmelidir. Bu nedenle klas\u00f6r payla\u015f\u0131m\u0131 uygulanacaksa standart bir klas\u00f6r mimarisi ve sahiplik kurallar\u0131 belirlemek i\u015f y\u00fck\u00fcn\u00fc azalt\u0131r.<\/p>\n<h2>Y\u00f6nlendirme (forwarding) neden \u201ceri\u015fim modeli\u201d de\u011fildir?<\/h2>\n<p>Forwarding, \u00e7o\u011fu zaman \u201cbirine eri\u015fim verelim\u201d yerine h\u0131zl\u0131 \u00e7\u00f6z\u00fcm gibi g\u00f6r\u00fcl\u00fcr. Oysa y\u00f6nlendirme, hem teslim edilebilirlik ve kimlik do\u011frulama zincirlerinde teknik yan etkilere neden olabilir hem de verinin kontrols\u00fcz \u00e7o\u011falmas\u0131na yol a\u00e7ar. Kurumsal kontrol a\u00e7\u0131s\u0131ndan en kritik sorun ise \u015fudur: Yaz\u0131\u015fmalar\u0131n kurumsal posta kutusu d\u0131\u015f\u0131nda ba\u015fka kutulara (ki\u015fisel hesaplar dahil) akmas\u0131, veri s\u0131n\u0131fland\u0131rmas\u0131 ve saklama disiplinini zorla\u015ft\u0131r\u0131r.<\/p>\n<p>Bu nedenle forwarding, bir ekip eri\u015fim \u00e7\u00f6z\u00fcm\u00fcnden \u00e7ok istisnai bir ta\u015f\u0131ma\/aktar\u0131m mekanizmas\u0131 olarak d\u00fc\u015f\u00fcn\u00fclmelidir. Eri\u015fim ihtiyac\u0131nda shared mailbox, delegasyon veya klas\u00f6r payla\u015f\u0131m\u0131 gibi daha kontroll\u00fc y\u00f6ntemler tercih edilir.<\/p>\n<h2>Senaryo bazl\u0131 do\u011fru model se\u00e7imi<\/h2>\n<h3>1) support@ gibi ekip adresi<\/h3>\n<ul>\n<li>\u00d6neri: Shared mailbox veya ekip tabanl\u0131 yap\u0131.<\/li>\n<li>G\u00f6nderim: Genellikle \u201cSend As\u201d (m\u00fc\u015fteri deneyimi i\u00e7in).<\/li>\n<li>Ek kontrol: Kimin hangi bileti yan\u0131tlad\u0131\u011f\u0131n\u0131 takip etmek i\u00e7in s\u00fcre\u00e7 kural\u0131 (konu etiketi, kategori, not vb.).<\/li>\n<\/ul>\n<h3>2) Y\u00f6netici asistan\u0131 eri\u015fimi<\/h3>\n<ul>\n<li>\u00d6neri: \u00d6nce klas\u00f6r ve takvim bazl\u0131 payla\u015f\u0131m; yetmezse s\u00fcreli delegasyon.<\/li>\n<li>G\u00f6nderim: Kurum k\u00fclt\u00fcr\u00fcne g\u00f6re \u201cSend on Behalf\u201d \u015feffafl\u0131k i\u00e7in uygun olabilir.<\/li>\n<li>G\u00fcvenlik: Yetki kapsam\u0131 ve s\u00fcre net olmal\u0131, d\u00fczenli g\u00f6zden ge\u00e7irilmeli.<\/li>\n<\/ul>\n<h3>3) Muhasebe s\u00fcre\u00e7leri (fatura@, tahsilat@)<\/h3>\n<ul>\n<li>\u00d6neri: Shared mailbox, fakat klas\u00f6r ayr\u0131m\u0131 ve rol bazl\u0131 eri\u015fim.<\/li>\n<li>G\u00f6nderim: \u201cSend As\u201d s\u0131k kullan\u0131l\u0131r; i\u00e7erik eri\u015fimi s\u0131n\u0131rlanmal\u0131d\u0131r.<\/li>\n<li>Risk: Hassas ekler i\u00e7in ayr\u0131 klas\u00f6r ve s\u0131n\u0131rl\u0131 eri\u015fim.<\/li>\n<\/ul>\n<h3>4) \u00c7al\u0131\u015fan ayr\u0131l\u0131\u015f\u0131 ve devir<\/h3>\n<p>\u00c7al\u0131\u015fan ayr\u0131ld\u0131\u011f\u0131nda ilk refleks bazen \u201cher \u015feyi y\u00f6nlendir\u201d olur. Daha g\u00fcvenli yakla\u015f\u0131m; posta kutusunu kilitlemek, eri\u015fimi kontroll\u00fc bir \u015fekilde devretmek ve gerekli ileti\u015fim kanallar\u0131n\u0131 rol bazl\u0131 adreslere ta\u015f\u0131makt\u0131r. Devir s\u00fcresince kimin hangi yetkiyle eri\u015fti\u011fi kay\u0131t alt\u0131na al\u0131nmal\u0131, s\u00fcre\u00e7 bitince yetkiler geri al\u0131nmal\u0131d\u0131r.<\/p>\n<h2>Yetkilendirme y\u00f6netimi i\u00e7in pratik kontrol listesi<\/h2>\n<ul>\n<li><strong>\u0130\u015f gerek\u00e7esi:<\/strong> Yetki neden veriliyor? Hangi i\u015fi m\u00fcmk\u00fcn k\u0131l\u0131yor?<\/li>\n<li><strong>Kapsam:<\/strong> Tam posta kutusu mu, klas\u00f6r m\u00fc, sadece g\u00f6nderim mi?<\/li>\n<li><strong>S\u00fcre:<\/strong> Biti\u015f tarihi var m\u0131? Yoksa neden kal\u0131c\u0131?<\/li>\n<li><strong>Onay:<\/strong> Yetki kim taraf\u0131ndan talep edildi, kim onaylad\u0131?<\/li>\n<li><strong>G\u00f6zden ge\u00e7irme:<\/strong> Belirli aral\u0131klarla (\u00f6r. \u00fc\u00e7 ayda bir) yetki listesi kontrol ediliyor mu?<\/li>\n<li><strong>Ayr\u0131l\u0131\u015f senaryosu:<\/strong> Kullan\u0131c\u0131 i\u015ften ayr\u0131ld\u0131\u011f\u0131nda bu yetki otomatik\/manuel nas\u0131l kald\u0131r\u0131lacak?<\/li>\n<\/ul>\n<h2>En s\u0131k yap\u0131lan hatalar ve nas\u0131l \u00f6nlenir?<\/h2>\n<h3>\u201cHerkese tam eri\u015fim verelim, sonra bakar\u0131z\u201d yakla\u015f\u0131m\u0131<\/h3>\n<p>Bu yakla\u015f\u0131m genellikle kal\u0131c\u0131 hale gelir. Alternatif olarak \u00f6nce en dar model (klas\u00f6r payla\u015f\u0131m\u0131 veya sadece g\u00f6nderim) ile ba\u015flay\u0131p, ger\u00e7ekten ihtiya\u00e7 ortaya \u00e7\u0131karsa geni\u015fletmek daha do\u011fru bir g\u00fcvenlik prati\u011fidir.<\/p>\n<h3>G\u00f6nderim yetkisi ile okuma yetkisini kar\u0131\u015ft\u0131rmak<\/h3>\n<p>Bir ki\u015finin bir adres ad\u0131na e-posta g\u00f6ndermesi gerekebilir, fakat ge\u00e7mi\u015f yaz\u0131\u015fmalar\u0131n tamam\u0131n\u0131 g\u00f6rmesi gerekmeyebilir. G\u00f6nderim ve okuma yetkileri m\u00fcmk\u00fcn oldu\u011funca ayr\u0131 tasarlanmal\u0131d\u0131r.<\/p>\n<h3>Rol bazl\u0131 adresleri ki\u015fiye ba\u011flamak<\/h3>\n<p>info@, sales@ gibi adresler bir ki\u015fiye ba\u011fl\u0131 y\u00fcr\u00fct\u00fcl\u00fcrse o ki\u015fi izne \u00e7\u0131kt\u0131\u011f\u0131nda veya ayr\u0131ld\u0131\u011f\u0131nda s\u00fcre\u00e7 kilitlenir. Rol bazl\u0131 adreslerin ekip s\u00fcre\u00e7lerine ba\u011flanmas\u0131 s\u00fcreklilik sa\u011flar.<\/p>\n<h2>Sonu\u00e7: Daha g\u00fcvenli, daha y\u00f6netilebilir bir e-posta organizasyonu<\/h2>\n<p>Kurumsal e-postada do\u011fru yetkilendirme modeli; yaln\u0131zca g\u00fcvenli\u011fi art\u0131rmakla kalmaz, ayn\u0131 zamanda i\u015f s\u00fcreklili\u011fini ve ekip verimlili\u011fini de y\u00fckseltir. Shared mailbox, delegasyon, Send As\/Send on Behalf ve klas\u00f6r payla\u015f\u0131m\u0131 aras\u0131ndaki farklar\u0131 netle\u015ftirip en az yetki prensibiyle uygulad\u0131\u011f\u0131n\u0131zda, hem denetim hem de operasyon taraf\u0131nda daha s\u00fcrd\u00fcr\u00fclebilir bir yap\u0131 olu\u015fur.<\/p>\n<p>Kurulu\u015funuz MX1Mail gibi profesyonel bir e-posta platformu kullan\u0131yorsa, yetki ve eri\u015fim ihtiya\u00e7lar\u0131n\u0131 belirlerken \u00f6nce organizasyonel modeli (rol adresleri, ekip posta kutular\u0131, devir s\u00fcre\u00e7leri) netle\u015ftirmek; ard\u0131ndan eri\u015fimi kapsam\/s\u00fcre\/onay ilkeleriyle standartla\u015ft\u0131rmak iyi bir ba\u015flang\u0131\u00e7 olacakt\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kurumsal e-postada en az yetki prensibiyle do\u011fru eri\u015fim modeli nas\u0131l se\u00e7ilir? Shared mailbox, delegasyon, Send As\/Send on Behalf ve klas\u00f6r payla\u015f\u0131m\u0131 senaryolar\u0131n\u0131 pratik \u00f6rneklerle \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[188],"tags":[406,408,357],"class_list":["post-161","post","type-post","status-publish","format-standard","hentry","category-e-posta-yonetimi","tag-erisim-yonetimi","tag-kurumsal-e-posta-guvenligi","tag-yetkilendirme"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=161"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/161\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}