Why are there so many cyber security standards — and how is a business meant to keep up?
- danielbuckton8
- Mar 22
- 4 min read
Over the last 12 months, I have spent a lot of time looking at different cyber security standards, frameworks and sector requirements. The more you look, the more one thing becomes obvious: Australian businesses are not short on guidance. They are drowning in it.
There is ISO/IEC 27001, still one of the best-known information security management system standards. There is the ASD’s Essential Eight and the ASD’s Information Security Manual (ISM). There is CIRMP for critical infrastructure, VPDSS for the Victorian public sector, RACGP standards for general practice, and minimum cybersecurity expectations for Victorian law practices. Then alongside all of that sits SMB1001, which was built specifically as a staged cyber maturity pathway for small and medium-sized businesses.
That is exactly why so many business owners, boards and managers feel overwhelmed. They are being asked harder questions by customers, insurers, sector bodies, government agencies and procurement teams, but the answers are spread across frameworks that were never designed to be read as one simple playbook.
And that raises a fair question.
Why are there so many standards?
The answer is not that the industry has made things complicated for no reason. The answer is that these frameworks were built for different jobs.
Some are management system standards. Some are technical baselines. Some are government security frameworks. Some are sector-specific expectations. Some are designed for large organisations, infrastructure operators or public sector environments. Others, like SMB1001, are far more practical for smaller organisations trying to build maturity step by step.
So the real issue is not simply that there are a lot of cyber standards. It is that businesses are often exposed to them as if they are interchangeable.
They are not.
A regional manufacturer supporting critical infrastructure, a GP clinic, a law firm, a Victorian government supplier and a mid-sized professional services firm may all need stronger cyber security. But they do not start with the same obligations, the same language, the same evidence requirements or the same level of maturity. Treating every framework like a universal answer only adds to the confusion.
That is also why I think SMB1001 deserves more attention in this conversation.
SMB1001 is not perfect, and it is not complete. But for many SMBs, it may be one of the most practical starting points available because it was built specifically for small and medium-sized businesses and structured across five levels of increasing maturity. That matters. It gives smaller organisations something many other frameworks do not: a clearer pathway, rather than a deep technical or regulatory document dropped on the desk with an expectation that the business will just work it out.
That does not mean SMB1001 should be treated as a silver bullet. It should not. No single framework is complete for every business, every sector or every risk profile. In practice, many organisations will still need to layer on customer requirements, sector-specific expectations, privacy obligations or more advanced control sets over time. But that is very different from saying the starting point must always be the most complex framework on the market.
That is where the market sometimes loses businesses.
When organisations are overwhelmed, they often assume the safest answer is to chase the biggest name. Sometimes that means jumping straight to ISO 27001 because it is widely recognised. Sometimes it means being pointed at the ISM because it is detailed and authoritative. Sometimes it means trying to interpret Essential Eight, sector guidance and customer questionnaires all at once. Sometimes it means being told that if a customer is in government, healthcare, legal services or critical infrastructure, then the supplier should simply “meet that standard too.”
But cyber maturity does not improve just because a business is handed a more complex framework.
It improves when the business is given a path that is practical, proportionate and achievable.
That is why I keep coming back to a simple idea:
Most businesses do not need more standards. They need better translation. They need to know what applies directly, what applies indirectly through contracts or sector expectations, what can sensibly be used as a baseline, and what should be layered in later as the organisation grows.
For many SMBs, that baseline may well be SMB1001. Not because it replaces every other framework. Not because it is the end of the journey. But because it offers a structured starting point in a landscape that is otherwise becoming harder to interpret.
There is one important caveat, though. A maturity pathway still needs judgement. The ASD’s guidance continues to reinforce practical basics such as multi-factor authentication, software updates, backups and the Essential Eight. That is a reminder that even when a framework provides staged uplift, some protections may need to be brought forward earlier where the risk is obvious.
That point matters. Which is one of the reasons SMB1001 works well as a starting framework is that it gives businesses a way to begin. But starting does not mean stopping. It does not remove the need for common sense, risk-based decisions or earlier implementation of obvious safeguards where the threat environment demands it. In that sense, SMB1001 is not the whole answer. It is the beginning of a more structured answer.
For many businesses, especially SMBs, the challenge is not a lack of standards. It is a lack of practical translation.
The question is no longer whether cyber standards matter. They do. The real question is how businesses can simplify the noise into a path that is practical, proportionate and achievable. That is where the next part of the discussion needs to go.




Comments