<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Murat Eksi</title><link>https://murateksi.com/tags/security/</link><description>Recent content in Security on Murat Eksi</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Apr 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://murateksi.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>The Deals That Stall on Security Were Already Lost</title><link>https://murateksi.com/posts/security-posture-as-sales-accelerant/</link><pubDate>Wed, 22 Apr 2026 09:00:00 +0200</pubDate><guid>https://murateksi.com/posts/security-posture-as-sales-accelerant/</guid><description>Every enterprise AE has a version of this story. The deal has been running for three months. Commercial terms are agreed. The implementation team has done a discovery session. You are writing the statement of work. Then the customer&amp;rsquo;s CISO asks to do a security review.
Four weeks later, the deal is dead. The review found issues with data residency, or encryption at rest, or the customer&amp;rsquo;s interpretation of their own regulatory obligations around where compute runs.</description></item><item><title>Open-sourcing a Security Hub Solution Across Fortune 500</title><link>https://murateksi.com/case-studies/security-hub-open-source/</link><pubDate>Thu, 01 Sep 2022 10:00:00 +0200</pubDate><guid>https://murateksi.com/case-studies/security-hub-open-source/</guid><description>Context The original customer was a large European financial services firm operating across eight AWS accounts, three regions, and two compliance regimes. They needed a unified view of their security posture: findings aggregated, normalized, prioritized, and routed to the right team without manual intervention. AWS Security Hub existed. Their multi-account setup, with a complex organizational structure that had grown through acquisition, meant that the out-of-the-box deployment did not fit.
They also had no product budget for a third-party SIEM.</description></item></channel></rss>