{"id":243,"date":"2026-11-14T09:04:00","date_gmt":"2026-11-14T09:04:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/?p=243"},"modified":"2026-11-14T09:04:00","modified_gmt":"2026-11-14T09:04:00","slug":"owasp-api-security-top-10-rehber","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/14\/owasp-api-security-top-10-rehber\/","title":{"rendered":"OWASP API Security Top 10: Backend Geli\u015ftirici \u0130\u00e7in T\u00fcrk\u00e7e Rehber"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>OWASP API Security Top 10<\/strong>, API&#8217;lerde en s\u0131k g\u00f6r\u00fclen ve en \u00e7ok istismar edilen g\u00fcvenlik risklerini s\u0131ralayan, OWASP toplulu\u011funun haz\u0131rlad\u0131\u011f\u0131 bir listedir. Son s\u00fcr\u00fcm\u00fc 2023&#8217;te yay\u0131nland\u0131. Klasik OWASP Top 10 web uygulamalar\u0131na odaklan\u0131rken, bu liste \u00f6zellikle REST ve GraphQL gibi API&#8217;lerin kendine \u00f6zg\u00fc zay\u0131fl\u0131klar\u0131n\u0131 anlat\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yaz\u0131da on maddenin her birini backend geli\u015ftirici g\u00f6z\u00fcyle, somut bir \u00f6rnek ve uygulanabilir bir \u00f6nlemle anlataca\u011f\u0131m. Baz\u0131 maddeleri daha \u00f6nce ayr\u0131 yaz\u0131larda detayl\u0131 ele alm\u0131\u015ft\u0131m. Onlara ilgili b\u00f6l\u00fcmlerde ba\u011flant\u0131 verdim.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Liste neden web uygulamas\u0131 listesinden ayr\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Klasik web uygulamalar\u0131nda sunucu HTML \u00fcretir ve kullan\u0131c\u0131n\u0131n neyi g\u00f6rebilece\u011fini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde sunucu belirler. API&#8217;lerde ise client, ham veriye do\u011frudan eri\u015fir. Hangi nesneyi isteyece\u011fini, hangi alanlar\u0131 g\u00f6nderece\u011fini, ka\u00e7 kay\u0131t alaca\u011f\u0131n\u0131 kendisi belirler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu fark, sald\u0131r\u0131 y\u00fczeyini de\u011fi\u015ftiriyor. API&#8217;lerde en yayg\u0131n a\u00e7\u0131klar karma\u015f\u0131k enjeksiyon sald\u0131r\u0131lar\u0131 de\u011fil, yetkilendirmenin nesne ve alan seviyesinde eksik kalmas\u0131d\u0131r. Listenin ilk \u00fc\u00e7 maddesinin yetkilendirme ile ilgili olmas\u0131 tesad\u00fcf de\u011fil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">OWASP API Security Top 10 maddeleri nelerdir?<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Kod<\/th><th>Risk<\/th><th>K\u0131saca<\/th><\/tr><\/thead><tbody><tr><td>API1<\/td><td>Broken Object Level Authorization<\/td><td>Ba\u015fkas\u0131n\u0131n nesnesine ID ile eri\u015fmek<\/td><\/tr><tr><td>API2<\/td><td>Broken Authentication<\/td><td>Zay\u0131f veya hatal\u0131 kimlik do\u011frulama<\/td><\/tr><tr><td>API3<\/td><td>Broken Object Property Level Authorization<\/td><td>G\u00f6r\u00fclmemesi veya de\u011fi\u015ftirilmemesi gereken alanlar<\/td><\/tr><tr><td>API4<\/td><td>Unrestricted Resource Consumption<\/td><td>Limitsiz istek, boyut ve maliyet<\/td><\/tr><tr><td>API5<\/td><td>Broken Function Level Authorization<\/td><td>Yetkisiz kullan\u0131c\u0131n\u0131n y\u00f6netici fonksiyonlar\u0131na eri\u015fmesi<\/td><\/tr><tr><td>API6<\/td><td>Unrestricted Access to Sensitive Business Flows<\/td><td>\u0130\u015f ak\u0131\u015flar\u0131n\u0131n otomasyonla k\u00f6t\u00fcye kullan\u0131lmas\u0131<\/td><\/tr><tr><td>API7<\/td><td>Server Side Request Forgery<\/td><td>Sunucunun kullan\u0131c\u0131 ad\u0131na istenmeyen adrese istek atmas\u0131<\/td><\/tr><tr><td>API8<\/td><td>Security Misconfiguration<\/td><td>Hatal\u0131 konfig\u00fcrasyon, a\u00e7\u0131k debug, eksik header<\/td><\/tr><tr><td>API9<\/td><td>Improper Inventory Management<\/td><td>Unutulmu\u015f eski versiyonlar ve test endpoint&#8217;leri<\/td><\/tr><tr><td>API10<\/td><td>Unsafe Consumption of APIs<\/td><td>\u00dc\u00e7\u00fcnc\u00fc taraf API cevaplar\u0131na k\u00f6r\u00fc k\u00f6r\u00fcne g\u00fcvenmek<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">API1: Nesne seviyesinde yetkilendirme<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Listenin ilk s\u0131ras\u0131ndaki risk, giri\u015f yapm\u0131\u015f bir kullan\u0131c\u0131n\u0131n URL&#8217;deki veya request body&#8217;deki ID&#8217;yi de\u011fi\u015ftirerek ba\u015fka bir kullan\u0131c\u0131n\u0131n verisine eri\u015febilmesidir. <code>GET \/invoices\/1043<\/code> iste\u011fi, faturan\u0131n ger\u00e7ekten o kullan\u0131c\u0131ya ait olup olmad\u0131\u011f\u0131 kontrol edilmeden cevaplan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nlem, nesneyi her zaman kullan\u0131c\u0131n\u0131n ba\u011flam\u0131nda sorgulamakt\u0131r. <code>findById(id)<\/code> yerine <code>findByIdAndOwnerId(id, currentUser)<\/code>. Bu a\u00e7\u0131\u011f\u0131 ve sistematik \u00f6nlemlerini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/07\/idor-broken-object-level-authorization\/\">IDOR ve nesne seviyesinde yetkilendirme<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 anlatt\u0131m. Multi-tenant sistemlerde ayn\u0131 problemin veritaban\u0131 seviyesindeki \u00e7\u00f6z\u00fcm\u00fc i\u00e7in <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/21\/multi-tenant-saas-data-isolation\/\">multi-tenant veri izolasyonu<\/a> yaz\u0131s\u0131na bakabilirsiniz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API2: Kimlik do\u011frulama hatalar\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu madde, kimlik do\u011frulama mekanizmas\u0131n\u0131n kendisindeki zay\u0131fl\u0131klar\u0131 kapsar. Brute force korumas\u0131 olmayan login endpoint&#8217;leri, imzas\u0131 do\u011frulanmayan veya <code>alg: none<\/code> kabul eden JWT k\u00fct\u00fcphaneleri, s\u00fcresiz token&#8217;lar ve parola s\u0131f\u0131rlama ak\u0131\u015flar\u0131ndaki tahmin edilebilir kodlar en yayg\u0131n \u00f6rnekler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pratik \u00f6nlemler:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Login, parola s\u0131f\u0131rlama ve OTP endpoint&#8217;lerinde s\u0131k\u0131 rate limit uygulamak.<\/li>\n\n\n<li>JWT do\u011frulamas\u0131nda kabul edilen algoritmay\u0131 a\u00e7\u0131k\u00e7a belirlemek.<\/li>\n\n\n<li>Access token \u00f6mr\u00fcn\u00fc k\u0131sa tutmak ve refresh token&#8217;lar\u0131 iptal edilebilir yapmak.<\/li>\n\n\n<li>Parolalar\u0131 yava\u015f ve tuzlu bir algoritmayla saklamak.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Token iptali konusunu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/22\/jwt-logout-token-revocation\/\">JWT ile logout problemi<\/a>, parola saklamay\u0131 da <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/06\/password-hashing-bcrypt-argon2\/\">bcrypt ve Argon2<\/a> yaz\u0131lar\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API3: Nesne \u00f6zelli\u011fi seviyesinde yetkilendirme<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">2023 s\u00fcr\u00fcm\u00fcnde eski &#8220;Excessive Data Exposure&#8221; ve &#8220;Mass Assignment&#8221; maddeleri tek bir ba\u015fl\u0131kta birle\u015ftirildi. \u0130ki y\u00f6n\u00fc var.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Okuma taraf\u0131nda API, kullan\u0131c\u0131n\u0131n g\u00f6rmemesi gereken alanlar\u0131 d\u00f6nd\u00fcr\u00fcr. Entity do\u011frudan JSON&#8217;a serialize edildi\u011finde <code>passwordHash<\/code>, i\u00e7 notlar veya ba\u015fka kullan\u0131c\u0131lar\u0131n e-posta adresleri cevaba girebilir. Frontend bu alanlar\u0131 g\u00f6stermese bile, a\u011f trafi\u011finde a\u00e7\u0131k\u00e7a durur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yazma taraf\u0131nda ise kullan\u0131c\u0131, de\u011fi\u015ftirmemesi gereken alanlar\u0131 request body&#8217;ye ekleyerek g\u00fcnceller. <code>\"role\": \"ADMIN\"<\/code> eklenmi\u015f bir profil g\u00fcncelleme iste\u011fi klasik \u00f6rnektir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her iki y\u00f6nde de en etkili \u00f6nlem, entity yerine i\u015fleme \u00f6zel DTO&#8217;lar kullanmakt\u0131r. Bu konuyu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/05\/mass-assignment-input-validation\/\">mass assignment<\/a> yaz\u0131s\u0131nda \u00f6rneklerle anlatt\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API4: S\u0131n\u0131rs\u0131z kaynak t\u00fcketimi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir API&#8217;nin kaynak t\u00fcketimi s\u0131n\u0131rlanmad\u0131\u011f\u0131nda, tek bir client b\u00fct\u00fcn sistemi yava\u015flatabilir veya maliyeti patlatabilir. Bu madde sadece istek say\u0131s\u0131 ile ilgili de\u011fil.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sayfa boyutu: <code>?size=1000000<\/code> kabul eden bir liste endpoint&#8217;i.<\/li>\n\n\n<li>Dosya boyutu: s\u0131n\u0131rs\u0131z y\u00fckleme kabul eden bir endpoint.<\/li>\n\n\n<li>\u0130\u015flem maliyeti: tek istekte binlerce SMS g\u00f6nderen veya pahal\u0131 bir rapor \u00fcreten bir i\u015flem.<\/li>\n\n\n<li>GraphQL&#8217;de i\u00e7 i\u00e7e sorgular\u0131n derinli\u011fi ve karma\u015f\u0131kl\u0131\u011f\u0131.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nlemler katmanl\u0131d\u0131r: istek say\u0131s\u0131 i\u00e7in rate limiting, boyut ve sayfa limitleri, timeout&#8217;lar ve pahal\u0131 i\u015flemler i\u00e7in ayr\u0131 kotalar. Rate limiting algoritmalar\u0131n\u0131n farklar\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/02\/rate-limiting-token-bucket-sliding-window\/\">token bucket ve sliding window<\/a> yaz\u0131s\u0131nda ele alm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API5: Fonksiyon seviyesinde yetkilendirme<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">API1 nesneye eri\u015fimle ilgiliyken, API5 fonksiyona eri\u015fimle ilgilidir. Normal bir kullan\u0131c\u0131n\u0131n <code>DELETE \/admin\/users\/42<\/code> veya <code>POST \/api\/reports\/export-all<\/code> gibi y\u00f6netici i\u015flemlerini \u00e7a\u011f\u0131rabilmesi bu kategoriye girer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu a\u00e7\u0131k genellikle y\u00f6netici endpoint&#8217;lerinin frontend&#8217;de gizlenmesine g\u00fcvenilmesinden kaynaklan\u0131r. Men\u00fcde g\u00f6r\u00fcnmeyen bir butonun arkas\u0131ndaki endpoint, URL&#8217;yi bilen herkes taraf\u0131ndan \u00e7a\u011fr\u0131labilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Security&#8217;de varsay\u0131lan olarak her endpoint&#8217;i yetki gerektirecek \u015fekilde kapat\u0131p, sadece a\u00e7\u0131k olmas\u0131 gerekenleri a\u00e7\u0131k\u00e7a izinli yapmak bu riski b\u00fcy\u00fck \u00f6l\u00e7\u00fcde azalt\u0131r. Y\u00f6netici i\u015flemlerini ayr\u0131 bir path alt\u0131nda toplamak ve bu path i\u00e7in ayr\u0131 bir kural tan\u0131mlamak da denetimi kolayla\u015ft\u0131r\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API6: Hassas i\u015f ak\u0131\u015flar\u0131na s\u0131n\u0131rs\u0131z eri\u015fim<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu madde teknik bir a\u00e7\u0131ktan \u00e7ok, i\u015f mant\u0131\u011f\u0131n\u0131n otomasyonla k\u00f6t\u00fcye kullan\u0131lmas\u0131yla ilgilidir. S\u0131n\u0131rl\u0131 stoklu bir \u00fcr\u00fcn\u00fcn botlar taraf\u0131ndan saniyeler i\u00e7inde toplanmas\u0131, kampanya kodlar\u0131n\u0131n denenerek bulunmas\u0131, sahte hesaplarla davet \u00f6d\u00fcllerinin toplanmas\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her istek teknik olarak ge\u00e7erlidir. Problem, ak\u0131\u015f\u0131n insan h\u0131z\u0131n\u0131n \u00e7ok \u00fczerinde ve b\u00fcy\u00fck \u00f6l\u00e7ekte kullan\u0131lmas\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nlemler i\u015f ak\u0131\u015f\u0131na \u00f6zeldir: cihaz ve davran\u0131\u015f bazl\u0131 sinyaller, hesap ba\u015f\u0131na s\u0131n\u0131rlar, \u015f\u00fcpheli desenlerde ek do\u011frulama. Hangi ak\u0131\u015flar\u0131n hassas oldu\u011funu belirlemek \u00fcr\u00fcn ekibiyle birlikte yap\u0131lmas\u0131 gereken bir i\u015f.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API7: Server Side Request Forgery<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131n\u0131n verdi\u011fi bir URL&#8217;ye sunucunun istek att\u0131\u011f\u0131 her \u00f6zellik SSRF riski ta\u015f\u0131r. Profil foto\u011fraf\u0131n\u0131 URL&#8217;den y\u00fckleme, webhook adresi tan\u0131mlama, link \u00f6nizlemesi olu\u015fturma.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sald\u0131rgan, URL olarak sunucunun i\u00e7 a\u011f\u0131ndaki bir adresi verir. Bulut ortamlar\u0131nda klasik hedef, instance metadata servisidir: <code>http:\/\/169.254.169.254\/<\/code>. Bu adres bulut kimlik bilgilerini d\u00f6nd\u00fcrebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nlemler:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>M\u00fcmk\u00fcnse izin verilen alan adlar\u0131ndan olu\u015fan bir liste kullanmak.<\/li>\n\n\n<li>DNS \u00e7\u00f6z\u00fcmlemesinden sonra IP adresini kontrol edip \u00f6zel ve link-local aral\u0131klar\u0131 reddetmek.<\/li>\n\n\n<li>Y\u00f6nlendirmeleri takip etmemek veya her y\u00f6nlendirmede kontrol\u00fc tekrar yapmak.<\/li>\n\n\n<li>Bu istekleri, i\u00e7 a\u011fa eri\u015fimi olmayan izole bir servisten g\u00f6ndermek.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook g\u00f6nderen sistemlerde bu kontroller \u00f6zellikle \u00f6nemli. Webhook tasar\u0131m\u0131n\u0131n di\u011fer y\u00f6nlerini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/03\/webhook-design-signing-retry\/\">g\u00fcvenilir webhook g\u00f6nderimi<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API8: G\u00fcvenlik konfig\u00fcrasyon hatalar\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Production&#8217;da a\u00e7\u0131k kalan stack trace&#8217;ler, varsay\u0131lan parolalar, gereksiz a\u00e7\u0131k HTTP metotlar\u0131, eksik g\u00fcvenlik header&#8217;lar\u0131, herkese a\u00e7\u0131k actuator endpoint&#8217;leri ve yanl\u0131\u015f CORS ayarlar\u0131 bu ba\u015fl\u0131\u011fa girer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot projelerinde s\u0131k g\u00f6rd\u00fc\u011f\u00fcm iki \u00f6rnek var. Birincisi, <code>\/actuator\/env<\/code> veya <code>\/actuator\/heapdump<\/code> endpoint&#8217;lerinin d\u0131\u015far\u0131ya a\u00e7\u0131k kalmas\u0131. Heap dump, bellekteki parolalar\u0131 ve token&#8217;lar\u0131 i\u00e7erebilir. \u0130kincisi, CORS&#8217;ta gelen origin&#8217;in oldu\u011fu gibi yans\u0131t\u0131lmas\u0131. Bu ikinci hatan\u0131n neden tehlikeli oldu\u011funu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/29\/cors-misconceptions\/\">CORS yaz\u0131s\u0131nda<\/a> anlatt\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hata cevaplar\u0131nda i\u00e7 detay s\u0131zd\u0131rmamak da bu kategoriye girer. Tutarl\u0131 ve g\u00fcvenli hata cevab\u0131 format\u0131 i\u00e7in <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/28\/api-error-response-problem-details\/\">RFC 9457 Problem Details<\/a> iyi bir ba\u015flang\u0131\u00e7.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API9: Envanter y\u00f6netimi eksikli\u011fi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unutulan bir <code>\/v1<\/code> endpoint&#8217;i, test i\u00e7in a\u00e7\u0131l\u0131p kapat\u0131lmayan bir debug API&#8217;si, staging ortam\u0131n\u0131n production verisine ba\u011fl\u0131 kalmas\u0131. Bu madde, bir organizasyonun hangi API&#8217;leri \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131 bilmemesinden do\u011fan riskleri kapsar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Eski versiyonlar genellikle yeni g\u00fcvenlik d\u00fczeltmelerini almaz. Sald\u0131rgan, yeni versiyonda kapat\u0131lm\u0131\u015f bir a\u00e7\u0131\u011f\u0131 h\u00e2l\u00e2 \u00e7al\u0131\u015fan eski versiyonda kullan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her API&#8217;nin bir sahibi, bir dok\u00fcmantasyonu ve bir ya\u015fam d\u00f6ng\u00fcs\u00fc olmal\u0131. OpenAPI \u015femalar\u0131n\u0131n merkezi bir yerde tutulmas\u0131 ve eski versiyonlar\u0131n planl\u0131 \u015fekilde kapat\u0131lmas\u0131 bu riski azalt\u0131r. Eski versiyonlar\u0131 kapatma stratejisini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/25\/api-backward-compatibility-versioning\/\">geriye uyumluluk ve versiyonlama<\/a> yaz\u0131s\u0131nda ele alm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API10: \u00dc\u00e7\u00fcnc\u00fc taraf API&#8217;lerin g\u00fcvensiz kullan\u0131m\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Geli\u015ftiriciler kullan\u0131c\u0131 girdisine \u015f\u00fcpheyle yakla\u015f\u0131r ama entegre olduklar\u0131 servislerden gelen veriye genellikle g\u00fcvenir. Bir \u00f6deme sa\u011flay\u0131c\u0131s\u0131n\u0131n veya adres do\u011frulama servisinin cevab\u0131 do\u011frulanmadan veritaban\u0131na yaz\u0131l\u0131r, bir sorguya eklenir veya kullan\u0131c\u0131ya g\u00f6sterilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00dc\u00e7\u00fcnc\u00fc taraf servis ele ge\u00e7irilirse veya beklenmedik bir cevap d\u00f6nerse, bu g\u00fcven bir sald\u0131r\u0131 yoluna d\u00f6n\u00fc\u015f\u00fcr. D\u0131\u015f servis cevaplar\u0131 da kullan\u0131c\u0131 girdisi gibi do\u011frulanmal\u0131, timeout ve boyut limitleriyle \u00e7a\u011fr\u0131lmal\u0131 ve y\u00f6nlendirmeler kontroll\u00fc takip edilmeli.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bu listeyi projede nas\u0131l kullanmal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Listeyi bir kez okuyup kenara koymak yerine, geli\u015ftirme s\u00fcrecinin farkl\u0131 noktalar\u0131na yerle\u015ftirmek daha etkili oluyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tasar\u0131m a\u015famas\u0131nda<\/strong>, her yeni endpoint i\u00e7in \u015fu \u00fc\u00e7 soruyu soruyorum: Kim \u00e7a\u011f\u0131rabilir? Hangi nesnelere eri\u015febilir? Hangi alanlar\u0131 okuyup de\u011fi\u015ftirebilir?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Code review&#8217;da<\/strong>, yetki kontrol\u00fc, DTO kullan\u0131m\u0131 ve limitler kontrol listesinin sabit maddeleri. Hangi sorular\u0131n review&#8217;da sorulmas\u0131 gerekti\u011fini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/31\/code-review-what-to-look-for\/\">kod incelemesinde neye bakmal\u0131<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Testlerde<\/strong>, her kaynak i\u00e7in &#8220;ba\u015fka bir kullan\u0131c\u0131 bu kayna\u011fa eri\u015fmeye \u00e7al\u0131\u015f\u0131rsa&#8221; senaryosu. Bu testler API1 ve API5 a\u00e7\u0131klar\u0131n\u0131n b\u00fcy\u00fck k\u0131sm\u0131n\u0131 production&#8217;a \u00e7\u0131kmadan yakalar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Operasyonda<\/strong>, a\u00e7\u0131k endpoint&#8217;lerin envanterini d\u00fczenli olarak g\u00f6zden ge\u00e7irmek ve kullan\u0131lmayan versiyonlar\u0131 kapatmak.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Listenin resmi metni ve her maddenin detayl\u0131 a\u00e7\u0131klamas\u0131 <a href=\"https:\/\/owasp.org\/API-Security\/editions\/2023\/en\/0x11-t10\/\" target=\"_blank\" rel=\"noopener\">OWASP API Security Top 10 2023<\/a> sayfas\u0131nda yer al\u0131yor. Her madde i\u00e7in sald\u0131r\u0131 senaryolar\u0131 ve \u00f6nleme y\u00f6ntemleri orada daha ayr\u0131nt\u0131l\u0131 anlat\u0131l\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu listedeki risklerin \u00e7o\u011fu karma\u015f\u0131k sald\u0131r\u0131 teknikleri gerektirmiyor. Bir taray\u0131c\u0131, biraz merak ve unutulmu\u015f bir yetki kontrol\u00fc yeterli. Bu y\u00fczden \u00f6nlemlerin de karma\u015f\u0131k olmas\u0131 gerekmiyor. Sadece her endpoint i\u00e7in tutarl\u0131 \u015fekilde uygulanmas\u0131 gerekiyor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>OWASP API Security Top 10, API&#8217;lerde en s\u0131k istismar edilen a\u00e7\u0131klar\u0131 listeler. On maddenin her biri i\u00e7in k\u0131sa a\u00e7\u0131klama, ger\u00e7ek \u00f6rnek ve Spring taraf\u0131nda \u00f6nlem.<\/p>\n","protected":false},"author":1,"featured_media":242,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-243","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\/243","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=243"}],"version-history":[{"count":1,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/243\/revisions"}],"predecessor-version":[{"id":279,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/243\/revisions\/279"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/242"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=243"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=243"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}