Cybersecurity for Australian businesses is easier to understand when each safeguard has a clear job. Account protection controls who can enter. Device security reduces opportunities to compromise a system. Backups provide a way to recover information when something still goes wrong. These layers support each other, but none replaces the others.
A business does not become secure merely by buying a security product. It needs to understand where important information lives, who can change it and how work would continue after an incident. This explainer connects the main controls to the problems they address.
Accounts are doors into the business
Email, accounting, payroll, file storage and website administration can all be reached through accounts. If someone takes control of email, they may also intercept password resets or imitate a trusted colleague. The significance of an account depends on what it can access, rather than how often its owner signs in.
Use separate accounts for individual staff so access can be adjusted and removed clearly. Administrative permissions deserve particular attention because they may allow software installation, account creation or changes affecting everyone. Ordinary daily work should not require broad privileges simply because that arrangement was convenient during setup.
Authentication needs more than a familiar password
A long, unique password helps prevent one exposed credential being reused elsewhere. A password manager can support that practice, but its own recovery and administrative arrangements need planning. Avoid treating a shared spreadsheet of passwords as equivalent to a properly managed password system.
Multi-factor authentication adds another verification requirement. The Australian Cyber Security Centre’s implementation guidance favours phishing-resistant methods where possible. The available method depends on the service. Ask an IT provider about supported options, enrolment, recovery and what happens when someone loses a device. Staff should never approve an unexpected authentication request simply to make a notification disappear.
Devices are part of a changing system
A laptop is connected to operating systems, browsers, applications, extensions and sometimes remote administration tools. An update may fix a weakness in any of those layers. Keeping only one application current leaves other routes open, and unsupported software may stop receiving relevant fixes.
Maintain a device and software inventory with an owner for each item. Automatic updates can reduce routine gaps, while systems that need careful scheduling should have a documented process. Check whether the update actually installed and whether a restart is pending. A notification acknowledged is not the same as a vulnerability addressed.
Backups are recovery tools, not just extra copies
File synchronisation can make work accessible across devices, but it may also synchronise a mistaken deletion or an unwanted change. A useful backup arrangement considers which versions are retained, who can alter them and whether an attacker could destroy them using the same compromised account.
The ACSC small business guide identifies backups, software updates and multi-factor authentication as foundational measures. For the business itself, define recovery in practical terms: the records required, the acceptable interruption and the most recent information that could be lost without making recovery unworkable.
A restore test answers the important question
A successful backup message confirms that a process ran, but it does not demonstrate that the business can use the result. Restore selected files into a safe location and check that they open. Include a system or application recovery discussion where specialist software is essential, because data alone may not restore a working service.
- List essential records and the systems that use them.
- Confirm backup frequency and retained versions.
- Separate backup access from ordinary working accounts where possible.
- Record who can authorise a restore.
- Test recovery and document anything that failed.
People need a reliable way to verify unusual requests
Attackers can exploit ordinary work patterns, such as a supplier changing bank details or a manager requesting urgent payment. A familiar name or genuine-looking email thread does not remove the need for verification. Build an independent check into consequential changes.
For example, use an established contact number already held in business records rather than a new number supplied in the suspicious message. Make the procedure apply consistently, including requests that appear to come from senior staff. A clear rule is easier to follow than expecting someone under time pressure to judge whether a message feels convincing.
These habits should be explained during onboarding and revisited when a process changes. Give staff a realistic example and let them practise finding the approved contact details. A procedure that exists only in a document nobody can locate is unlikely to provide much help during a rushed request.
Know who acts when something looks wrong
Keep an incident contact list accessible if ordinary email or file storage becomes unavailable. Identify the internal decision-maker, IT support and relevant service providers. Staff should know how to report a suspected compromise promptly without experimenting with unfamiliar recovery steps.
Review these controls when staff, software or business processes change. The point is a working relationship between access, prevention and recovery. Understanding that relationship makes it easier to ask suppliers useful questions and to recognise a gap before an incident exposes it.