Sentinel cost optimisation

You are paying a premium for data nothing ever reads.

Microsoft Sentinel bills for every gigabyte you ingest. Most of it sits at the premium analytics rate serving detections that never touch it. We prove which data earns its keep, and cut the rest without losing a single detection.

A short, no-cost call confirms fit. We measure against your own data before we quote a number.

The pain

The bill only ever climbs, and nobody can say what it buys.

Every new source, every new agent, every new log type adds to the monthly invoice. Almost none of it is questioned, because questioning it feels like questioning your own security.

01

You pay a premium rate to store silence

Analytics-tier data is priced for searching and alerting. Most tables are never queried by a detection at all. You are paying the fast rate for data that simply sits there.

02

Nobody can point at what is safe to cut

Trimming a table means someone has to prove no detection depends on it. Without that proof the safe answer is always to keep paying, so the bill never comes down.

03

Cutting blind costs you coverage

The usual advice is to drop noisy sources or sample them. Do that without knowing which events feed which rule and you silently break detections. The saving shows up on the invoice; the gap shows up during an incident.

The honest problem

Cost and coverage are usually treated as a trade. Finance wants the bill down, the security team wants everything kept, and the argument stalls because neither side has the evidence to settle it. That evidence is the actual deliverable here.

The promise

Detection coverage comes first. The saving is what falls out of doing that properly.

We never trade coverage for cost. Detecting the attack scenarios that matter to you is the deliverable; the lower bill is a by-product of knowing exactly which events your detections depend on.

Where the spend actually goes

Table by table, in your own environment, with the cost drivers named rather than estimated.

Proof of which data earns its keep

We identify the exact events each detection depends on, so nothing a rule needs is ever tiered down, filtered or sampled away.

A ranked plan, not a list of opinions

Every change ordered by what it saves against what it costs to do, so you can stop wherever the return stops making sense.

Techniques that keep the evidence

Splitting a table so the full data lands in cheap storage while the detection slice keeps working. Stripping the one heavy column that dominates a busy table. The events survive; the premium rate does not.

Read-only until you say otherwise

The review changes nothing in your workspace. You see the ranked plan first, and you choose whether to make the changes yourself or have us do them for you.

The proof

Evidence, not adjectives.

Outcomes from real engagements, anonymised. Every figure is measured against a client's own data before we quote it.

£100,000+
taken off a single estate’s annual Sentinel bill, a 53% cut, delivered and closed.
275m
events in a single table in one month, of which just 161 drove the detections using it.
£245k+
removed from customers’ annual bills across seven delivered engagements, recurring every year.
From a recent review

A single high-volume table held over 275 million events in a month, of which just 161 drove the detections that used it. We moved the rest to a lower-cost tier, cutting the bill without touching a single event. That is the method: find the fraction of your data that earns its place in the analytics tier, and stop paying a premium to store the rest.

Worked example

Six high-volume tables, one engagement.

A recent engagement, anonymised. We sent only the events that actually drive the enabled detection rules to the premium analytics tier, and moved everything else to low-cost storage.

BeforeAll six tables at the premium analytics rate
100% at the premium rate
AfterSame six tables, same detections
17%
83% moved to low-cost storage, still searchable
The 17% that stays is the slice the detection rules actually read. Nothing was sampled, filtered or deleted.
83%+
less data at the premium analytics rate
55%+
lower annual cost for those tables
Zero
detections lost, and none weakened
The table that barely moved

One of the six reduced by only 15%, because its detection rules genuinely used the data. We left it alone. That is the method working rather than failing: the rules decide what stays, so a table that earns its place keeps it.

Measured on a live engagement and anonymised. These are first-reading figures taken on a weekday-only average, which is the busiest part of the week, so the final measured saving is expected to be higher rather than lower. We quote what we have measured, not what we hope for.

The return

Put your own number in.

The saving is a percentage of your ingestion bill, so the higher your volume the more it returns in absolute terms. Move the slider to see the range we measure in practice.

£
Per month, approximate. Nothing is sent anywhere; this calculates in your browser.
20% (conservative)50% (typical)64% (best measured)
Saved per year £120,000
Saved per month £10,000
New annual run rate £180,000

This is an illustration, not a quote. It applies the range we have measured on other estates to a number you typed in. Your actual saving is measured against your own data before we quote anything, so the figure you get is yours rather than a model.

How it works

A review first. You decide what happens next.

Review

We analyse your ingestion table by table and map every detection to the events it actually depends on. Read-only throughout, and nothing changes in your workspace.

Ranked plan

You get an ordered set of changes with the saving and the effort against each, plus the evidence behind every recommendation so your security team can challenge it.

Implement

Make the changes yourself, or have us do them. Either way we confirm coverage is intact with a measured before and after.

Request the review

Find out what your data is actually costing you.

Tell us what you run and we will come back to arrange a short, no-cost call. If we do not think we can save you money, we will tell you that too.

  • A short call to confirm fit, at no cost and no obligation.
  • We measure against your own data before quoting a saving.
  • Your details are used to contact you about this enquiry only.
Please tell us your name.
Please enter a valid work email address.
Please tell us where you work.
Not sure is a perfectly good answer. Working it out is part of the review.

We reply within one working day.

Mock-up only, nothing was sent

This is the payload the page would POST to the Azure Function once wired up:


        

Thank you, that is with us.

We will come back to you within one working day to arrange a short call.

The saving recurs every year. The engagement does not.

A short call is enough to tell whether there is money to find in your estate. If there is not, we will say so.

Request the review