A Cybersecurity Starting Plan for Australian Small Businesses with Limited Resources

Cybersecurity for Australian small businesses can feel too large to start when the same person manages bookings, invoices and customer service. A useful response is to organise a small first week of work with clear owners and visible outcomes. The purpose is to reduce obvious exposure and make the next decisions easier.

Consider a hypothetical repair business with an owner, two staff and an external IT provider used occasionally. Its email, accounting software and shared files are essential. The scenario below illustrates a starting process; it is not an account of a real business or a complete security assessment.

Monday: identify what must keep working

The owner lists the systems needed to take bookings, contact customers and receive payment. For each one, the list records who administers it, which provider hosts it and how support is contacted. The exercise reveals that one former staff member still appears in an account and that nobody knows who controls a website renewal.

Rather than changing everything immediately, the owner verifies responsibilities with the provider and records the necessary actions. Access removal is coordinated so essential services are not accidentally interrupted. A basic inventory now exists, and the owner can tell which accounts deserve attention first.

The Australian Cyber Security Centre’s small business guide identifies multi-factor authentication, software updates and backups as starting measures. The business uses those priorities to structure the week while seeking qualified help for anything it cannot safely manage.

Tuesday: improve the accounts that unlock other accounts

The owner begins with business email and administrator access, because losing them could affect several services. Staff enable available multi-factor authentication through the official account settings, with support where needed. Each person learns how normal sign-in works and what to do if their usual authentication method becomes unavailable.

They also stop sharing a single everyday login where individual accounts are supported. Recovery arrangements are documented securely and access is limited to the people who need it. The owner checks that business recovery details do not depend entirely on an employee’s personal contact information.

The task is complete when the business has tested ordinary access and knows who can recover an account. Simply ticking an enabled setting is insufficient if nobody understands the recovery process or if a critical shared service becomes inaccessible.

Wednesday: schedule updates around operations

The team identifies the laptops, phones and software used for work. Automatic updates are enabled where appropriate, and the IT provider checks anything that is unsupported or difficult to update. Changes affecting essential equipment are scheduled with a fallback so customer work is not disrupted unnecessarily.

One device needs a restart to finish an update. Another has specialist software the owner is reluctant to change. That second issue goes to the provider for advice instead of being ignored indefinitely or updated blindly. The inventory now distinguishes completed actions from unresolved technical decisions.

Thursday: find out whether recovery actually works

The business asks what its current backup service includes, how often it runs and whether a compromised ordinary account could delete the backups. A cloud folder is not assumed to be a sufficient recovery plan merely because files appear on more than one device.

  • Identify the information needed to resume essential work.
  • Confirm who manages backups and receives failure alerts.
  • Check that the backup includes the intended systems and files.
  • Arrange a controlled test restoring a suitable sample.
  • Record the result, missing items and the next test date.

The provider performs the test without overwriting live information. A missing folder is discovered and added to the backup scope. This small correction makes the exercise useful: the business has evidence about recovery rather than only a subscription receipt for a backup product.

Friday: agree what happens when something looks wrong

The owner creates a short contact list and explains how staff should report suspicious messages, unexpected account changes or payment requests. The list includes the IT provider and essential service contacts, with a copy available if email is unavailable. Staff know they can report a mistake promptly without being discouraged from speaking up.

Business.gov.au’s cybersecurity checklist includes planning how to manage the business during and after an incident. The repair business turns that into a brief discussion of who makes decisions, how customers can be contacted and which operations could continue temporarily.

The staff also practise verifying a changed supplier bank account through an established contact. They agree who can approve payments and how an urgent request is checked. This connects technical security to the ordinary administrative decisions through which the business moves money.

End the week with an owned task list

The owner reviews completed work and assigns unresolved items a person and date. Future tasks may include supplier access, staff training and a fuller security assessment. The first week has not made the business immune to attack. It has created clearer ownership, tested essential controls and a practical foundation for sustained improvement.