{"id":91,"date":"2026-10-09T17:20:00","date_gmt":"2026-10-09T17:20:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/09\/secret-management-api-keys-git\/"},"modified":"2026-10-09T17:20:00","modified_gmt":"2026-10-09T17:20:00","slug":"secret-management-api-keys-git","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/09\/secret-management-api-keys-git\/","title":{"rendered":"API Anahtar\u0131 Git Ge\u00e7mi\u015finde Kal\u0131r: Secret Y\u00f6netimi \u00dczerine"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir geli\u015ftirici yanl\u0131\u015fl\u0131kla <code>.env<\/code> dosyas\u0131n\u0131 commit ediyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fark ediyor. Hemen dosyay\u0131 silip yeni bir commit at\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Problem \u00e7\u00f6z\u00fclm\u00fc\u015f gibi g\u00f6r\u00fcn\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama de\u011fil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Anahtar git ge\u00e7mi\u015finde duruyor. Repository&#8217;yi klonlayan herkes <code>git log -p<\/code> ile onu g\u00f6rebilir. Repository herkese a\u00e7\u0131ksa, otomatik taray\u0131c\u0131lar bu t\u00fcr anahtarlar\u0131 dakikalar i\u00e7inde bulabiliyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00d6nce rotation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir secret s\u0131zd\u0131\u011f\u0131nda ilk soru &#8220;ge\u00e7mi\u015ften nas\u0131l silerim?&#8221; olmamal\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130lk soru \u015fu olmal\u0131: <strong>bu anahtar\u0131 nas\u0131l iptal ederim?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131zm\u0131\u015f bir anahtar art\u0131k g\u00fcvenli de\u011fildir. Ge\u00e7mi\u015ften silmek, onu daha \u00f6nce g\u00f6rm\u00fc\u015f birinin elinden almaz. Fork&#8217;larda, klonlarda, CI cache&#8217;lerinde veya log&#8217;larda kalm\u0131\u015f olabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do\u011fru s\u0131ra:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Anahtar\u0131 iptal et ve yenisini \u00fcret.<\/li>\n\n\n<li>Yeni anahtar\u0131 uygulamalara da\u011f\u0131t.<\/li>\n\n\n<li>Eski anahtarla yap\u0131lan i\u015flemleri sa\u011flay\u0131c\u0131n\u0131n loglar\u0131ndan kontrol et.<\/li>\n\n\n<li>Sonra, istenirse, ge\u00e7mi\u015fi temizle.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ge\u00e7mi\u015fi <code>git filter-repo<\/code> gibi bir ara\u00e7la temizlemek m\u00fcmk\u00fcn. Ama herkesin klonunu yeniden almas\u0131 gerekir ve hosting platformlar\u0131nda eski commit&#8217;ler bir s\u00fcre eri\u015filebilir kalabilir. Bu ad\u0131m bir temizlik, g\u00fcvenlik \u00f6nlemi de\u011fil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Rotation zor olmamal\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131z\u0131nt\u0131 an\u0131nda ya\u015fanan as\u0131l problem, \u00e7o\u011fu zaman anahtar\u0131 de\u011fi\u015ftirmenin ne kadar zor oldu\u011funun ortaya \u00e7\u0131kmas\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Anahtar be\u015f farkl\u0131 servisin konfig\u00fcrasyonunda, iki farkl\u0131 CI pipeline&#8217;\u0131nda ve bir geli\u015ftiricinin yerel makinesindeki bir script&#8217;te kullan\u0131l\u0131yor. Kimse tam listeyi bilmiyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rotation&#8217;\u0131 acil durum i\u00e7in de\u011fil, rutin bir i\u015flem olarak tasarlamak bu y\u00fczden \u00f6nemli. D\u00fczenli olarak de\u011fi\u015ftirilen bir anahtar\u0131n nerede kullan\u0131ld\u0131\u011f\u0131 bilinir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">M\u00fcmk\u00fcn oldu\u011funda iki anahtar\u0131n ayn\u0131 anda ge\u00e7erli olabildi\u011fi bir d\u00f6nem tan\u0131mlamak da kesintisiz ge\u00e7i\u015fi sa\u011flar. Yeni anahtar da\u011f\u0131t\u0131l\u0131r, eski anahtar ancak t\u00fcm servisler ge\u00e7tikten sonra iptal edilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Secret&#8217;lar koda ait de\u011fil<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Temel kural basit: secret&#8217;lar kaynak kodda veya kodla birlikte versiyonlanan dosyalarda durmamal\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.gitignore<\/code> ilk savunma hatt\u0131 ama tek ba\u015f\u0131na yetmiyor. Bir dosya bir kez commit edildiyse, sonradan <code>.gitignore<\/code>&#8216;a eklenmesi onu ge\u00e7mi\u015ften \u00e7\u0131karmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Commit \u00f6ncesi tarama yapan ara\u00e7lar, gitleaks gibi, bir pre-commit hook veya CI ad\u0131m\u0131 olarak eklenebilir. GitHub&#8217;\u0131n push protection \u00f6zelli\u011fi de bilinen sa\u011flay\u0131c\u0131lar\u0131n anahtar formatlar\u0131n\u0131 push an\u0131nda engelleyebiliyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Nerede saklanmal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Production&#8217;da secret&#8217;lar\u0131n merkezi bir yerde tutulmas\u0131 gerekir. HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager veya Kubernetes ortam\u0131nda External Secrets gibi \u00e7\u00f6z\u00fcmler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ara\u00e7lar\u0131n sa\u011flad\u0131\u011f\u0131 as\u0131l de\u011fer depolama de\u011fil. Eri\u015fim kontrol\u00fc, audit log ve rotation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hangi servisin hangi secret&#8217;a ne zaman eri\u015fti\u011fi bilinir. Bir secret de\u011fi\u015fti\u011finde uygulamalar yeniden ba\u015flat\u0131lmadan yeni de\u011feri alabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Daha da iyisi, m\u00fcmk\u00fcn olan yerlerde uzun \u00f6m\u00fcrl\u00fc secret&#8217;lar\u0131 tamamen ortadan kald\u0131rmak. Bulut sa\u011flay\u0131c\u0131lar\u0131n\u0131n workload identity mekanizmalar\u0131, uygulaman\u0131n statik bir anahtar yerine k\u0131sa \u00f6m\u00fcrl\u00fc, otomatik yenilenen kimlik bilgileri kullanmas\u0131n\u0131 sa\u011fl\u0131yor. Saklanmayan bir anahtar s\u0131zamaz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Log&#8217;lar da s\u0131zd\u0131r\u0131r<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Secret&#8217;lar sadece repository&#8217;den s\u0131zmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir HTTP client&#8217;\u0131n debug log&#8217;u <code>Authorization<\/code> header&#8217;\u0131n\u0131 yazabilir. Bir exception mesaj\u0131 connection string&#8217;i i\u00e7erebilir. Bir hata raporlama arac\u0131 request body&#8217;sini oldu\u011fu gibi g\u00f6nderebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Log&#8217;larda hassas alanlar\u0131 maskelemek ve hangi bilgilerin log&#8217;a yaz\u0131ld\u0131\u011f\u0131n\u0131 d\u00fczenli olarak kontrol etmek, secret y\u00f6netiminin az konu\u015fulan bir par\u00e7as\u0131.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">En az yetki<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131z\u0131nt\u0131n\u0131n etkisini azaltman\u0131n son yolu, her anahtar\u0131n sadece ihtiya\u00e7 duydu\u011fu yetkiye sahip olmas\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sadece okuma yapan bir rapor servisine tam yetkili bir veritaban\u0131 kullan\u0131c\u0131s\u0131 vermek, o servisin s\u0131zan bir anahtar\u0131n\u0131 \u00e7ok daha tehlikeli hale getirir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Secret s\u0131z\u0131nt\u0131lar\u0131 b\u00fcy\u00fck ihtimalle bir g\u00fcn ya\u015fanacak.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As\u0131l soru, ya\u015fand\u0131\u011f\u0131nda ka\u00e7 dakika i\u00e7inde etkisiz hale getirilebilece\u011fi.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>.env dosyas\u0131 commit edildi, sonra silindi. Ama anahtar h\u00e2l\u00e2 git ge\u00e7mi\u015finde. Secret s\u0131z\u0131nt\u0131s\u0131 oldu\u011funda do\u011fru tepki, rotation ve secret&#8217;lar\u0131 koddan ay\u0131rman\u0131n yollar\u0131.<\/p>\n","protected":false},"author":1,"featured_media":90,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-91","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-api-tasarimi"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/90"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}