Go jump in a lake: Measuring the data lake effect on your SIEM
ID: 3c8a5165-dc35-51ad-954b-20935b0cc3ca
STIX ID: report--3c8a5165-dc35-51ad-954b-20935b0cc3ca
Feed Name: Red Canary
This article discusses how SIEM costs escalate with growing telemetry and illustrates, using an OpenSearch example, that compute drives most expense while storage is comparatively cheap; it proposes shifting to a data lake model that decouples storage (object storage) from compute (serverless) to reduce costs, scale on demand, and maintain visibility, setting up a follow-up on implementation details.
Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.
