Consolidate when four things are true at once. The fix for what an assessment found sits in a different budget from the assessment. The evidence an insurer or a major client asks for is assembled by somebody who does not run your systems. The framework work arrived as a report, and nothing maintains it. And no single party's scope covers the chain from a control to the evidence that it works. inSUPPORT runs managed IT services in Australia for businesses of roughly 30 to 300 users. Support is priced per user per month at $68, $100 or $135, with insurance, backup and security-awareness training quoted separately.
If you are the CFO, you did not get here from a technology opinion. You got here from a pile of invoices. One bills every month, and one billed once for a document. The policy sits with a broker you have never met. Nobody is doing anything wrong. You still cannot describe the arrangement to a board.
Consolidating is not a discount. It decides who answers for one chain of work. It earns its disruption only when that chain is visibly broken. You can run three capable suppliers well.
So what follows is the test itself, built from documents you already hold and questions a provider can answer in writing. It ends with the cases that go the other way.
TL;DR: When consolidation is actually the answer
- ✅ Four conditions, and they have to arrive together: the fix in a different budget from the finding, evidence assembled by somebody who does not run the systems, framework work that stopped at a report, and nobody owning the whole chain.
- ✅ A provider needing access to your systems and data changes your cyber security risk profile, which is the Australian Signals Directorate's point rather than ours. ASD's five questions for a managed service provider have to be answered by each one separately. Three relationships is three of everything.
- ✅ Test the contract, not the pitch. Which schedule says the remediation is inside the fee, what maintains the framework position between reviews, and which party actually holds the financial services licence.
- ✅ One provider does not mean one number. Support is per user per month, and insurance, backup and security-awareness training are quoted as their own lines. That is the point: you can see what each one costs and decline the ones you do not want.
- ✅ Keep three when an assessment has to be independent, when a broker relationship carries real market access, or when the only thing on offer is a lower total.
Contents
- The Four Conditions, and Why They Arrive Together
- Test the Contract, Not the Pitch
- When Keeping Three Specialists Is Still the Right Answer
- Questions a CFO asks before merging three IT relationships into one
The Four Conditions, and Why They Arrive Together
Any one of these on its own is an argument for a conversation, not a restructure. All four at once describe something different. It is a business carrying three commercial relationships for one operating outcome, and every seam between them is a place a cost can appear. Each condition below is checkable from documents you already hold. That is the only reason to trust it.
- The fix and the finding sit in different budgets. You paid for an assessment. It produced findings. The findings produced a second proposal. Go back through last financial year and work out how much of what you spent outside the monthly fee was closing a gap an assessment had already named. That figure is the condition, in dollars you can show somebody.
- The evidence is assembled by somebody who does not run the systems. A proposal form turns up, or a client's security schedule does. Somebody then has to describe the current state of your controls. If that person has to go and ask your IT provider for screenshots, what you submit is a reconstruction. It is accurate as at the week it was built, and no longer.
- The framework work was a report, and nothing maintains it. A point-in-time assessment describes the environment on the day it was done. Environments move. People join, devices change, and settings get relaxed for a deadline. Ask who holds the position between reviews, and ask for the document that says so.
- Nobody's scope covers the chain. Each party's responsibility ends where the next one's begins. ASD makes the same point in security language rather than commercial language: know where the boundaries are between you and your provider, identify which systems each one can reach and how, and keep that record current.
The Security Version of the Same Count
There is a version of this argument with no money in it at all, and it is the version that needs no translation for a board. ASD's guidance for organisations engaging a managed service provider says it plainly. A provider needing access to systems, networks and sensitive data changes your organisation's cyber security risk profile, and somebody has to manage that change carefully.
A separate ASD publication sets out five questions to put to such a provider. Is it implementing better practice cyber security itself? Is it securely administering its systems and services? Is it monitoring activity on them? Is it regularly assessing them? And is it prepared to respond to an incident?
Read that list as a workload rather than a checklist. Those five questions are per provider, not per business. So is deciding which parts of your network each one may reach, so is the contract clause, and so is the access register you are supposed to keep current. Three relationships is three of everything, every year.
Test the Contract, Not the Pitch
Any provider in this market can write the sentence about doing IT, compliance and insurance together. The sentence is free. What separates an operating model from a brochure is whether the incentive is written into a document you could enforce. Here are the three places worth looking.
Which schedule says the remediation is inside the fee
Ask for the clause, not the claim. The position is published on the managed IT services page. The remediation your audit finds is included in your support fee, not billed back as a surprise project. That one can be held against a published price list, and it survives a CFO reading it twice where an adjective would not.
Then ask the harder half. Every fee has a limit: some work sits inside it and some does not. A provider who says nothing falls outside theirs has told you the scope is not written down. Ask which schedule names the scope, and ask what falls outside it. The line-by-line version of that boundary is already set out in what sits inside the fee and what gets quoted separately, so the job here is narrower: get the answer attached to the agreement you will sign. A provider whose money runs the other way is not disqualified by any of this. They need to say so before you sign, and you need to budget for it.
What maintains the framework between reviews
A framework position is a state rather than an event, so what you are paying for is somebody keeping it there. Ask who holds it between assessments, what they watch, and what happens when a control drifts. Ask for the name of the framework and the scope it covers while you are there. A provider that names the framework it aligns to and the scope it covers has answered you. One who offers a single reassuring word has not, and that word cost them nothing.
ASD's guidance tells customers to make the contract require their provider to maintain a good internal security culture and to implement cyber security guidance such as the Essential Eight in its own business. That is a fair thing to ask of a party about to hold your evidence as well as your systems. On the framework itself, read the current guidance before any name or target goes into a contract, including the ones in this article. When ASD's published answers were captured on 20 October 2026, ASD said it would advise on expectations for transitioning from the Essential 8 to the ASD Essentials in due course. It also said efforts already completed under the Essential 8 remain relevant.
Which party holds the financial services licence
The third test is the cleanest one on the list, and it is the one nobody volunteers. Arranging insurance is a licensed activity. The Australian Securities and Investments Commission (ASIC) states that an Australian financial services licence is required to conduct a financial services business. Its example of dealing in a financial product is buying or selling shares on behalf of a client, and it separately lists general insurance as a financial product. So an IT provider telling you it handles your cyber insurance is either licensed, working with somebody who is, or saying something it should not.
inSUPPORT does not hold an Australian financial services licence. Cyber insurance is arranged through its licensed insurance partners and underwritten by the insurer. Cover is subject to the insurer's assessment. What consolidates on the IT side is the part that was always an IT job. Somebody sets the controls, keeps them in place, and produces the evidence that makes a business insurable, and that somebody is the team running the environment rather than a person reassembling it at renewal. Be pedantic about the difference, because the difference is what you are buying. You can check the licence half yourself in about a minute, because ASIC's professional registers show which organisations are registered or licensed to provide a service.
When Keeping Three Specialists Is Still the Right Answer
Give the other side its due. Anybody who argues for consolidation and cannot name where it stops is selling, not advising. There are four situations where three suppliers is the correct number and collapsing them into one would leave you worse off.
- When an assessment has to be independent. An obligation may require the assessment to come from a party that is not doing the remediation. Where it does, holding the assessor and the remediator apart is the entire point, and consolidating defeats it. Read what your own obligation actually says before you assume either way, because asking for an assessment and asking for an independent one are two different requirements.
- When the broker relationship carries real market access. A broker who knows your sector, has placed cover through a hard market and can approach more than one underwriter is holding something an IT provider is not licensed to replace. Consolidating the control and evidence work does not require you to give that up. A provider who suggests otherwise is overreaching.
- When the environment is genuinely more than one environment. Think of several jurisdictions, an acquired business still running its own stack, or operational technology sitting beside the office network. One provider across all of that is a scope question long before it is a saving. The honest answer may be two providers with a written boundary between them.
- When the only gain on offer is a lower total. Then you are shopping, not restructuring, and you should shop properly. Put the work out to tender and compare. Before you change how the work is run, ask what the change fixes that money alone would not.
The Version to Take Into the Room
Count the suppliers last. What matters first is whether anybody owns the chain from a control to the evidence that it is working, and whether the money points the same way as that job. Where one party owns that chain and a document says so, three names on the invoice list is a filing problem, and you should leave it alone. Where nobody owns it, adding a fourth name will not help, and replacing three with one helps only if the new agreement actually assigns the chain.
None of this requires you to form a view about technology. It requires four answers from your own records and three clauses from whoever you are signing with. If you do decide to move, the sequence and the real risks are set out in how long it takes to change IT providers. The short version is that the work that goes wrong is the work nobody wrote down.
Questions a CFO asks before merging three IT relationships into one
When should we consolidate IT, compliance and the cyber insurance pathway with one provider?
When all four conditions are true together. The remediation for an assessment's findings sits in a different budget from the assessment, and the control evidence an insurer or a client asks for is assembled by somebody who does not run your systems. The framework work was a report that nothing maintains, and no single party's scope covers the chain from a control to its evidence. Fewer than four and you are usually shopping on price instead, not changing how the work is run. One caution on the insurance side, because consolidating does not reach as far as it sounds. The licensed partners arrange the policy and the insurer underwrites it. Insurance, backup and security-awareness training stay as separately quoted lines and do not disappear into one fee.
Do we still need an independent assessor if one provider does both the audit and the remediation?
It depends on what your own obligation says, so read it before you act on a memory of it. If a regulator, a government contract or a major customer requires the assessment to come from a party that is not doing the remediation, keep the two apart. Consolidating would remove the thing the requirement exists to create. Where the requirement is simply for an assessment, the party that runs the environment is often the one holding the evidence anyway. Ask the organisation that imposed the requirement, in writing, before you restructure around a guess.
What order does the work happen in once it is with one provider?
The 6 Step Cyber Strength System sets the order: Consult, Audit, Remediate, Comply, Insure and Support. The Insure stage is the evidence work that makes a business insurable. The licensed partners arrange the policy and the insurer underwrites it. Discovery first, then an audit of the environment against the compliance frameworks that apply to your industry, then an agreed remediation plan. Then the standing support and maintenance that keeps the position current. The maintenance is what produces the evidence, so it is a by-product of the work and never its own project. Treat any duration you are offered as a scope question and have it written down next to what it covers. What finishes when depends on what the audit turns up in your environment.
What is the first step if we think the four conditions apply to us?
Do the two cheap things first, in this order. Pull last financial year's invoices and separate the monthly fee from everything billed outside it, with a cause written against each line. Then ask each current supplier for the clause that says who pays to close a gap an assessment finds. Those two answers usually settle the question without anybody being sold anything. If they say the conditions are real, the next step is a documented view of your own environment. Every option you are weighing up needs one.
If three or four of those conditions describe your arrangement, the cheapest next move is a documented view of your own environment. A Cyber Strength Audit records what is actually configured and assesses it against the compliance frameworks that apply to your industry, with internal and external penetration testing. It then sets out the gaps with the remediation steps against each one. Take managed support afterwards and the remediation that audit identifies sits inside the support fee. Either way you walk out holding a document instead of an impression, and every proposal you read after that has something to be measured against.
Book a Cyber Strength Audit →Citations
- "How to manage your security when engaging a managed service provider", the Australian Signals Directorate's guidance for organisations that outsource IT. Used above for two statements it makes directly: a managed service provider needing access to systems, networks and sensitive data changes your organisation's cyber security risk profile and needs careful management, and organisations should know where the boundaries are between themselves and their provider by identifying which systems each provider can access and how, and keeping that record up to date. It also tells customers to require their provider to implement cyber security guidance such as the Essential Eight in its own business. Published 21 December 2018, last reviewed 5 April 2023. Read 16 November 2026. cyber.gov.au
- "Questions to ask managed service providers", the Australian Signals Directorate's short publication for organisations selecting, managing or reviewing a provider. The five questions named above are its five headings: are you implementing better practice cyber security, are you securely administering your systems and services, are you monitoring activity on your systems and services, are you regularly assessing your systems and services, and are you prepared for and able to respond to cyber security incidents. Published 24 March 2017, last reviewed 24 March 2023. Read 16 November 2026. cyber.gov.au
- "Check if you need an AFS licence", ASIC's own page on Australian financial services licensing. The three statements used above come straight from it: an AFS licence is required to conduct a financial services business, you provide a financial service if you deal in a financial product, for example by buying or selling shares on behalf of a client, and financial products include general insurance. This is the source of the licence test a finance team can apply to any provider that says it handles cyber insurance. Read 16 November 2026. asic.gov.au
- "Search ASIC registers", ASIC's register index, used above for a practical step and not for a legal point. Its professional registers search is described on the page as the way to find out about a person or an organisation registered or licensed with ASIC to provide a service, which is how a business checks for itself who in an arrangement actually holds a licence. Read 16 November 2026. asic.gov.au
- "Frequently asked questions, ASD Essentials", the Australian Signals Directorate's FAQ for the ASD Essentials, which it published on 15 October 2026 as the replacement for the Essential Eight. Used above for exactly two statements it makes: ASD will advise on expectations for transitioning to the new framework in due course, and efforts already completed under the Essential Eight remain relevant and will directly support alignment with the Essentials series. Published and last reviewed 15 October 2026. Answers captured at source 20 October 2026. cyber.gov.au
Related Reading
- Managed IT Services
- What Does a Managed IT Support Fee Actually Cover in Australia?
- Twelve Questions to Ask Your IT Provider Before You Renew
- What Happens in a Cyber Strength Audit
- The 6 Step Cyber Strength System
About the author: Kane Nawrocki is the founder and CEO of inSUPPORT. He has spent more than 25 years in IT and built inSUPPORT to give Australian businesses managed IT, security and compliance as one model, with the remediation an audit finds included in the support fee rather than billed back as a surprise project.
Content reviewed by Probably Genius for accuracy and relevance.
inSUPPORT provides managed IT and cyber security services. It is not an insurer, insurance broker or underwriter and does not hold an Australian Financial Services Licence. Where cyber insurance forms part of a plan, it is arranged through licensed insurance partners and underwritten by the insurer. Cover is subject to the insurer's assessment, the policy terms and the Product Disclosure Statement and Target Market Determination. This article is general information about IT and security practice, not financial product advice, and it does not take account of your objectives, financial situation or needs.
CLICK HERE


