← All work

An Australian financial services licensee · 2026

Cloud cost reduction that funded the security work

The usual reason security work does not happen is that there is no budget line for it. In most small estates a meaningful part of that budget is already being spent on infrastructure delivering nothing.

How to tell whether you have this

Ask for your cloud spend broken down by resource, then ask what each line is for.

That is a cheap conversation and in most small estates it finds something. If nobody can account for a line item, that is not a billing question. It is a configuration question with a bill attached.

Why it happens

Provisioning is a decision somebody makes in a hurry to unblock something. Deprovisioning is a decision nobody is ever assigned. Cloud spend accretes for that reason alone, and it does not require anyone to have made a mistake.

Why this belongs on a security site

Because the most common reason this work does not happen at a firm your size is not disagreement about whether it should. It is that there is no budget line for it, and asking a principal to find new money for a risk that has not materialised is a hard conversation.

This is the answer to that. Money already being spent on infrastructure delivering nothing can fund the monitoring, the identity work and the documentation without anyone finding new budget. On the engagement below, the monitoring platform that replaced part of the removed spend runs at about A$160 a month.

How I would approach it

  1. Separate three different things that look alike on an invoice: genuinely unused, over-provisioned for a load that never arrived, and correctly sized but the wrong service for the job.
  2. Document a reverse command and a business rationale for every change, so nothing is removed on the strength of my judgement alone and anything contested goes back in a minute.
  3. Handle the third category last, because it carries the actual risk. Switching off something unused is housekeeping. Replacing something that works with something cheaper that works better is a judgement call.
  4. Set a budget with forecast alerting and an action group, so the position holds instead of drifting back within a year.

What you end up with

A recurring saving rather than a one-off, and somebody finding out about drift in the month it happens rather than at the next annual review.

The framing that matters is not cost cutting. Infrastructure delivering nothing is money you have already decided to spend. It can be spent on something that reduces risk instead.

What it looked like in practice

delivered

Figures from the engagement described above, not a projection of what your estate would produce. Yours will look different.

RefFoundNowWhat the figure refers to
01A$1,826A$340monthly Azure run-rate, a reduction of about 81 per cent
02~A$18,000recurring annual saving, not a one-off

Is this yours?

If any of the above sounds like your estate, say so and I will tell you what checking would involve. Most of these start as a short look rather than a project.

Not sure it is this one? The rest of the work covers monitoring, identity, deployment, cost, AI use and compliance documentation.

Related work

All work