<rss xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
  <atom:link href="https://nxlog.co/news-and-blog/index.xml" rel="self" type="application/rss+xml" />
  <title>Financial services</title>
    <link>https://nxlog.co/news-and-blog/tags/financial-services/</link>
    <description>Recent content in Financial services on NXLog Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
  <lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate>
  
  <item>
    <title>Where your SIEM ingestion bill comes from: a financial services cost breakdown</title>
    <link>https://nxlog.co/news-and-blog/posts/siem-ingestion-cost-breakdown-financial-services/</link>
    <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
    
    <enclosure url="https://nxlog.co/news-and-blog/images/categories/siem.webp" type="image/webp" />
    <atom:logo>https://nxlog.co/news-and-blog/images/categories/siem.webp</atom:logo>
    
    <guid>https://nxlog.co/news-and-blog/posts/siem-ingestion-cost-breakdown-financial-services/</guid>
    <description>
    
    &lt;img src=&#34;https://nxlog.co/news-and-blog/images/categories/siem.webp&#34; width=500 /&gt;
    
    Most security leaders can tell you their SIEM bill to the dollar. Far fewer can tell you, line by line, what they’re paying for. That’s a problem because in financial services, that bill grows faster than the security coverage it’s supposed to buy. Let’s break it down.
The bill is a function of volume, and volume is not your friend Ingestion-priced SIEMs charge by how much data you send. That makes your security budget a direct function of log volume.
    </description>
    
    <dc:creator><![CDATA[ João Correia ]]></dc:creator>
    
  </item>
   
  </channel>
</rss>
