Cyber Security for Accountants: The Essential Eight

Protect client details and ATO access in your accounting practice. Use a cyber security checklist for email encryption, staff training and policies.

Published
Updated

Cyber security for accountants starts with named access and multi-factor sign-in. Assign this checklist to protect ATO access and keep TFNs out of staff inboxes.

The Checklist at a Glance

Print this list and write a staff name beside each owner. The checking intervals below are a practical starting schedule for a small practice.

Client Data

  1. Turn on multi-factor authentication for every service holding client data, including email, document storage and your tax software. Owner: IT provider. Check monthly and whenever you add a service.
  2. Restrict client folders and TFNs to staff who need them. Owner: practice manager. Check monthly and when someone changes roles.
  3. Replace document attachments with an approved portal or secure file link. Owner: practice manager. Check each new-client request.
  4. Keep a retention register and arrange secure disposal when lawful retention and use end. Owner: principal. Check annually and before disposing of devices.

ATO Access

  1. Give each authorised staff member their own myID and business authorisation. Owner: principal. Check monthly and remove leavers on their last day.
  2. Confirm refund bank changes through a number already on file and record approval. Owner: practice manager. Check every change.
  3. Review unexpected lodgements and bank changes against the job record. Owner: practice manager. Check each working day.

Devices

  1. Keep supported software updated and check that device protection is running. Owner: IT provider. Monitor continuously and report exceptions weekly.
  2. Require encrypted devices, screen locks and separate administrator accounts. Owner: IT provider. Check monthly and before issuing a device.
  3. Back up client records and test restoring a usable file. Owner: IT provider. Check backup results daily and test recovery quarterly.

Email

  1. Require mailbox multi-factor sign-in and investigate unexpected forwarding rules. Owner: IT provider. Check monthly and after a suspicious sign-in.
  2. Set up SPF, DKIM and DMARC for the practice domain, plus external-sender warnings. Owner: IT provider. Check after configuration changes and review reports monthly.

Staff

  1. Train staff to collect client documents through approved services and give access only to the people doing the work. Owner: practice manager. Check at induction and before busy periods.
  2. Rehearse a document transfer and report a simulated disclosure. Owner: practice manager. Repeat before tax season and record what each person demonstrated.

Written Policies

  1. Approve acceptable use rules and have staff sign them. Owner: principal. Check at induction and review annually.
  2. Keep incident contacts and escalation instructions available outside the affected computer. Owner: practice manager. Check quarterly and whenever a contact changes.

For the first week, finish items 1, 5, 3, 6 and 10 in that order. Confirm sign-in protection works, obsolete access is removed and the secure document link reaches the intended client.

Ask the IT provider to demonstrate a restored file you can open. Record unfinished work with an owner and completion target.

What Your Duties Require You to Protect

Your confidentiality duties cover client information wherever the practice holds or shares it. Under Code item 6 in section 30-10 of the Tax Agent Services Act, disclosure needs client permission or a legal duty.

The TPB’s confidentiality guidance includes cloud storage and outsourced services in this responsibility.

Weak security can therefore become a professional conduct matter. The TPB’s guidance on TFNs in email explains that failing to take reasonable protective steps can have Code consequences.

A breach does not automatically prove a Code breach. The circumstances and precautions matter.

The OAIC’s TFN Rule guidance requires reasonable safeguards against misuse, loss and unauthorised access, modification or disclosure. Limit TFN access to people who need it for an authorised purpose.

Securely destroy or permanently de-identify TFN information when lawful retention and permitted need end. Check retention duties before deleting records.

Criminals value TFNs, identity documents, bank details, ATO access and business records. Together, these can support identity theft and refund fraud.

Stolen agent access can let a criminal lodge returns or redirect refunds through the practice’s access. Protect the authority to act as carefully as the documents supporting it.

Protecting ATO Online Services Access and Client Refunds

Each staff member who needs ATO access must use their own myID and their own authorisation to act for the practice. Never share the principal’s identity or approve a sign-in request somebody else initiated.

Relationship Authorisation Manager (RAM) manages business authorisations. ATO Access Manager sets the permissions needed for individual duties.

Use Standard or Strong myID for ordinary staff access. Strong identity strength is needed for a principal authority linking a business online in RAM. An assisted route exists where Strong is unavailable.

A Basic identity has a separate restricted access process. These are different requirements from a taxpayer’s access through myGov.

Keep the RAM authorisation guide beside your access register. Review authorisations and ATO permissions monthly. Remove a leaver’s access on their last day, including document storage and mailboxes. A role change also needs a review of permissions.

Never change a client’s refund bank details on an email request alone. Call a number already in the client record, establish who you are speaking with and confirm the request.

Keep one bank-change record from the client’s instruction through to the saved refund destination.

  1. Retain the client’s instruction and identify the client and tax account affected. Check that the practice has signed authority to act for that account.
  2. Record the independent callback, including the number’s existing source, who answered and how you confirmed their identity and authority. Record the account details they confirmed.
  3. Name the staff member who approves the change and record their decision. Use a second staff check before updating the record.
  4. Name the person who actually updates the bank details and identify the destination: your tax software, the relevant ATO account or both. Record the time of each change.
  5. Reopen the saved destination record and compare the BSB, account number and account name with the approved instruction. Record who confirms the match and when.

The ATO’s agent user guide distinguishes signed authority from the financial institution details held against each client account. Updating a bank field in a client form does not confirm the ATO refund destination. Check the saved ATO record separately.

If a refund change is unauthorised, compare this record with available sign-in and change logs for the affected services. Ask the ATO or software provider to examine records your practice cannot access.

Tax Genie’s form-change history records changes within Tax Genie. Evidence of an ATO bank-account change must come from the destination record and available ATO evidence.

Watch for lodgements nobody prepared, refund account changes nobody approved and clients unexpectedly leaving the agent list. Treat an unexplained event as a suspected incident.

The principal must call the ATO’s Client Identity Support Centre on 1800 467 033 if they suspect taxpayer information was compromised. Follow the ATO’s data breach guidance for tax professionals.

Notify the practice’s incident lead immediately. Use the incident response plan for technical escalation and recovery.

Place the Mitigation Plan Within Your Duties

The Australian Signals Directorate’s Essential Eight is one model for reducing cyber risks within your wider client-information responsibilities. Its maturity model says additional measures can be needed for the organisation’s environment.

Applying it does not remove confidentiality, safe document handling or staff responsibilities.

Private tax practices do not become subject to government security policy simply by being registered agents. A contract or another applicable requirement can set a specific security standard. Record that requirement separately from the practice’s chosen mitigation target.

Give your principal and IT provider the dedicated Essential Eight checklist for maturity targets, assigned settings and assessment evidence. Keep this practice checklist for responsibilities across client records, ATO access and staff behaviour.

ASD has launched the Essentials series as an evolution of the Essential Eight. Its launch announcement says both frameworks remain maintained during the transition. Existing regulatory obligations continue until regulators communicate changes.

The series covers enterprise IT, cloud and operational technology through separate chapters. This expands the environments covered. A practice’s existing Essential Eight work remains relevant during the transition.

Ask your IT provider to use ASD’s transition guidance to compare the revised requirements with your settings. Have the provider identify systems that need changes and evidence the practice can reuse.

Keep protective measures running while the provider assesses any transition. Review the resulting actions and evidence before closing the work.

Email Security and Sending Client Information

Keep TFNs, identity documents and bank details out of plain email. A taken-over mailbox exposes stored attachments, conversation history and future messages. Criminals can also impersonate staff from the compromised account.

Email encryption can mean different things. Transport encryption protects a connection between mail systems while a message travels. Message encryption protects the message content, with access depending on the chosen method.

The Advanced Encryption Standard, or AES, is a method for encrypting data. When a provider lists AES, check which files it encrypts and who can decrypt them.

Transport encryption alone leaves a readable attachment in the recipient’s mailbox. It does not protect that document from someone who takes over the account.

Prefer a portal or secure file-sharing service with named access and an expiry setting. Use email for the notification and messages without identity or tax numbers.

The TPB’s TFN guidance also describes encrypted or password-protected attachments where email is necessary. Confirm the recipient and send any password through a separate channel.

Compare secure email providers by multi-factor sign-in, message encryption, administrator permissions, audit logs and recovery arrangements. Ask where messages, backups and support access are located.

An Australian-hosted provider is an option for a practice that requires Australian storage. Confirm the actual service locations in its written terms. Hosting location alone does not establish the most secure email service.

Ask your IT provider to apply ASD’s advice on preventing fake emails. SPF identifies authorised sending systems, DKIM signs outgoing mail and DMARC tells receiving systems how to handle failed checks.

Start with an inventory of legitimate senders before enforcing rejection. Add external-sender warnings and monitor mailbox forwarding rules. These settings do not stop a criminal sending from a genuinely compromised account.

Train Staff to Handle Client Records

At induction and before busy periods, have staff practise using the approved form to collect documents. Show where to file them, who needs access and which services the practice uses for sharing.

Give each person a fictional client file and name the colleague who needs it. Ask them to demonstrate the transfer.

  1. Confirm the recipient against the practice record and check they have permission to receive the file.
  2. Share through the approved service. Give access to the named recipient and choose the shortest expiry that allows them to finish the work.
  3. Log what was shared, with whom and when. Check that the intended recipient can open the file.
  4. For the exercise, tell the staff member that someone without permission received the link. Have them report it immediately to the practice’s incident lead using the policy’s reporting route.

Record who attended, which tasks each person demonstrated and what they need to repeat. Give the principal the register before tax season so they can assign follow-up training.

The OAIC’s guide to securing personal information covers training new starters, refresher training and limiting staff access to what their work requires.

Acceptable Use and a Cyber Security Policy Template

An acceptable use policy tells staff which devices and services they can use for practice work. Require approved devices and prohibit personal email or personal cloud storage for client files.

Set rules for USB storage, working from home and public wifi. Staff need a clear approval route when the usual method cannot be used.

Include AI use in those rules. Name the approved services and the information staff can enter. Require approval before client information goes to a new service, including any client permission needed for disclosure.

For exercises in ChatGPT, Claude or any other general AI tool, use fictional records. Give staff a clear route to seek approval before sharing client information with an AI provider.

Use this outline for a policy of a few pages. Under each heading, write the practice’s actual instruction and responsible role.

  1. Scope: identify the staff, contractors, devices and services covered.
  2. Roles: name the principal, practice manager, IT contact and incident lead.
  3. Access control: require named accounts, multi-factor sign-in and prompt removal of access.
  4. Data handling and TFN rules: specify approved storage, authorised sharing and retention review.
  5. Email: state the document-sharing method, recipient checks and suspicious-message reporting route.
  6. Devices: set approval, updating, encryption, USB and remote-working rules.
  7. Backups: name what is protected, who checks failures and who confirms recovery.
  8. Incident reporting: identify the trigger and link to the practice’s response instructions.
  9. Review date: record the next review and what changes require an earlier review.

Have each staff member sign the policy at induction. Review it annually and when the practice changes a service or discovers a failed safeguard.

Link the incident section to your data breach response plan. Keep breach assessment and notification instructions there.

Collecting New-Client Details Without Exposing Them

New-client collection brings TFNs, identity documents and bank details together. Asking for attachments puts those details in staff inboxes and makes later copies harder to track. Give the client one approved form or portal request and collect documents there.

Tax Genie collects client answers in a guided form and checks the details. TFNs are encrypted before storage and stay hidden until a staff member reveals them. Each reveal is logged.

TFNs stay out of emails, exports and generated documents.

Tax Genie removes every TFN before AI reviews the answers. When staff correct an answer, the history records who changed what and when. Read how Tax Genie handles TFNs when setting the practice’s collection rules.

For example, a fictional company client can upload its requested documents through the form. Staff receive an alert and review the record instead of downloading identity attachments from an email.

The manager assigns access to the staff doing that client’s work and records any approved disclosure to another provider.

Requirements to Give an Accounting Practice’s IT Provider

Give your IT provider a written brief covering named access, multi-factor sign-in, protected devices, backups, recovery tests and incident contacts. List the services that hold client information, including your tax software and cloud document storage.

Assign the practice manager responsibility for confirming the provider’s work.

Record who holds administrator credentials, who can access client files and how that access is approved and logged. Set an urgent incident contact and escalation route.

Require the provider to remove its access and hand over administration when the arrangement ends. The principal must also address client permission for provider access.

Support ArrangementStaff Access and Service ScopeRecovery and Escalation Duties
Managed IT supportAgreed ongoing device, account and security administrationName who monitors failures, runs recovery tests and handles urgent incidents
Incident-only assistanceAccess granted for a defined problem, then removedAgree the call-out route and separately assign routine backup and updating duties
Hosted desktop serviceStaff use a remotely hosted working environment with defined accessIdentify who restores files, the desktop and connected services, plus the provider’s escalation route

A hosted desktop does not automatically include every backup or secure every mailbox. A managed service also needs a written scope. Compare proposals by the responsibilities covered and the evidence supplied, including access reports and recovery results.

If you are reviewing Practice Protect for staff login security, its billing terms distinguish user and device licences. Ask which count applies to the services in your quote and how to remove a departing user from billing.

ConnectWise’s Cloud Backup advisory describes unauthorised access to application credentials and an interruption to backup services. Ask your provider who checks which practice services are affected when a supplier reports an incident.

Ask who confirms the next backup ran and which file the provider will restore to prove recovery works. Discuss cyber insurance for accountants separately from the IT support agreement.

Before accepting a closed ticket, the practice manager must open the restored client file and confirm staff access works as intended. Record any missing data or permissions and return the ticket for correction.

The principal signs off unresolved risks and the next review, so a completed support job has a confirmed client-record result.

Devices, Remote Access and Accounting Logins

Allow remote access only from approved devices through the practice’s approved service, with named accounts and multi-factor sign-in. Ask IT to disable unused remote access and keep administrator access separate from everyday work.

A bring your own device (BYOD) policy must state whether personal devices can hold client files. Require IT approval before use and explain how practice access and stored client files are removed when employment ends.

For a Windows login, Windows Hello for Business combines a credential tied to the device with a PIN or biometric check. Ask IT to verify both the Windows sign-in and the separate remote-access sign-in.

If your practice uses FortiGate, ask IT which VPN mode your FortiOS release supports. For Entra-managed sign-in, have IT verify that the VPN requires multi-factor authentication. FortiOS 7.6.3 replaced SSL VPN tunnel mode with IPsec.

If your practice uses Synology storage, ask IT to enforce two-factor authentication for DSM accounts and verify it on an administrator and an ordinary user account.

The device security policy must cover encryption, supported software, automatic updates, screen locking and lost-device reporting for practice laptops. Staff must report a missing laptop immediately to the practice manager and IT provider.

A clean desk policy covers paper as well as screens. Lock client documents away when unattended, collect printouts promptly and position screens so household members or visitors cannot read them.

For MYOB, set up two-factor authentication on each person’s account. MYOB recommends an authenticator app and supports passkeys. Keep recovery arrangements with the account owner instead of sharing sign-in codes across the team.

Reckon Accounts Hosted requires multi-factor authentication. For other Reckon products, identify the exact service and its sign-in requirements in the access register. Remove departing staff from each company file and service they could access.

The practice manager must confirm access removal on the person’s last day. Ask IT for the account report, then check the remaining staff permissions against their work. Keep Microsoft 365 configuration in the Microsoft 365 security guide.

One client form. One finished return.

Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.

See how Tax Genie works

Made for Australian accounting firms

Tax GenieSee how Tax Genie works