Cyber security for accountants: where client data moves in tax season, and how to test each step
An accounting or bookkeeping practice can hold tax file numbers, identity documents, workpapers, payroll files and logins to its clients' ledgers, and its busiest weeks can bring seasonal staff and a stream of shared documents.
This guide follows that workflow from first enquiry to former client, sets out the duties that may bear on a practice as their own text states them, and gives a tax-season matrix of access tests and change-freeze evidence to run on systems your practice runs or holds accounts in.
On this page
Tax-season workflow matrix with access tests and a change-freeze evidence lane
Rows W1 to W12 follow an accounting practice's year from first enquiry to former client, and rows F1 to F6 are the evidence lane for a tax-season change freeze. Use it only on systems your practice runs or holds accounts in, with invented test roles: clients A and B (client A also plays the former client in W10), seasonal staff member S and outside bookkeeper K, each given a mailbox and mobile number that belong to the practice.
How to use itHide the instructions
Write the expected result before you run a row, keep the evidence for passes as well as failures, and follow the limits in each row's last column. Rows W1 to W6 and W9 to W12 sign in, submit or send requests, and each states its own limits; rows W7 and W8 sign in with your own login only to read a user or app list. Rows F1 to F6 check a document, a list or a log, and where an F row reruns a W row, that run keeps the W row's limits. For any system a vendor runs, read the vendor's terms first and ask the vendor where they are unclear.
18 rows
Row and step
Data involved
W1. Onboarding: website enquiry and engagement forms
- Data involved
- Names, phone numbers and email addresses, business and entity details, the services asked for, and any documents the form accepts.
- Who should reach it, and who should not
- Should: the staff who handle new enquiries and engagements. Should not: other visitors, other clients, or anyone who opens a confirmation page by changing its address.
- Test case or check
- Submit each form once as an invented prospect, using an email address you control. List every inbox, tool and portal the submission reaches. Read the confirmation page and email. If the confirmation page address contains a number or id, change it once and reload.
- Expected result
- The submission reaches only the places on your list. The confirmation repeats nothing beyond the prospect's name and the next step. The changed address returns a refusal or a not-found page, not another submission.
- Evidence to keep
- The date, the form address, the list of places the submission reached and who can read each, the confirmation text, and the response to the changed address.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one submission per form and one changed address.
W2. Onboarding: portal invitation and first sign-in
- Data involved
- The client contact's email address, the invitation link, and everything the portal will hold for that client.
- Who should reach it, and who should not
- Should: the invited contact. Should not: anyone holding the invitation once it has been used, or an invitation past the expiry your portal states.
- Test case or check
- Invite test client A at an address you control. Accept the invitation and sign in, noting whether a second factor is asked for or offered. Open the used link once more in a private window. If the portal states an expiry, open one unaccepted test invitation once after it.
- Expected result
- The used link does not sign anyone in or let them set a password. The expired invitation is refused. The first sign-in follows the second-factor setting you chose.
- Evidence to keep
- A screenshot of each result with the date and time, cropped so the invitation link itself does not show, and the portal's invitation and second-factor settings as configured.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one invitation accepted, one reuse of it and one expired invitation.
W3. TFN collection
- Data involved
- An individual client's TFN, typed into a form or portal field or carried on an uploaded document.
- Who should reach it, and who should not
- Should: the client, and the staff who need to handle the TFN for the tax work. Should not: other clients, other staff roles, notification emails, and exports whose recipients have no use for it. Section 11(1) of the TFN Rule says TFN recipients must take reasonable steps to ensure that access to records containing TFN information is restricted to individuals who need to handle it for taxation law, personal assistance law or superannuation law purposes.
- Test case or check
- As test client A, enter a placeholder TFN agreed with whoever runs the form, never a real number. Sign in as each staff role and note whether each sees it in full, masked or not at all. Read the notification the portal sends. On the staging copy, or with the export filtered to test client A where there is no staging copy, run each export or report that includes client details and search it for the value; do not export real clients' records for this row. As test client B, request client A's record once by its link or id.
- Expected result
- Only the roles on your list see the full value. The notification names no TFN. Exports with no need for it leave it out or mask it. Client B gets a refusal or a not-found response.
- Evidence to keep
- A dated role-by-role list of what each role saw, the notification text, the column list of each export, and client B's response.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one entry, one sign-in per staff role, one run per export and one request as client B.
W4. Identity documents
- Data involved
- Scans or photos of identity documents and the details on them, such as date of birth and address.
- Who should reach it, and who should not
- Should: the client, and the staff who verify identity. Should not: other clients, staff who never verify identity, a visitor with no session, or anyone using the link after the client signs out.
- Test case or check
- As test client A, upload an invented image marked SAMPLE, not a copy of any real document. Request its download link once from client B's session, once with no session in a private window and once after client A signs out. Note where the file is kept once identity is checked, and which roles can list it there.
- Expected result
- All three requests are refused. The file sits where your process says it should, and only the roles on your list can see it.
- Evidence to keep
- Which file each request was for (a description, not the link itself), each response with the date and time, the storage location, and the roles that can list or open the file.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one upload and three requests for the link.
W5. BAS workpapers and review
- Data involved
- A client's transaction detail, GST and PAYG workings, reviewer notes and the draft statement.
- Who should reach it, and who should not
- Should: the preparer and reviewer on the job, and the client once your process releases it. Should not: other clients, staff outside the job if your rules exclude them, or the client while it is a draft, if your process holds drafts back.
- Test case or check
- Create a workpaper with invented figures for test clients A and B. As client A, request client B's workpaper and draft once each by link or id. As a staff account outside the job, open client A's job. As client A, look for reviewer notes on the client side.
- Expected result
- Client A is refused client B's files. The staff account sees what your rules allow and no more. Reviewer notes stay on the practice side.
- Evidence to keep
- Each request and response, the staff account's view, and a screenshot of the client side, all dated.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: two as client A and one view as the staff account.
W6. Payroll files
- Data involved
- Payroll reports and exports, which may carry employees' names, pay rates, bank details and TFNs. The employees are the client's, not the practice's clients.
- Who should reach it, and who should not
- Should: the client's payroll contact and the practice staff on the payroll work. Should not: other clients, staff outside the job, and anyone an export is sent to who does not need every field in it.
- Test case or check
- In a test organisation or test company file with invented employees, run each payroll report and export your practice uses and list the fields each one contains. Then, from the user lists recorded in row W7, note which users of each client file hold a role that reaches payroll. In MYOB Business, MYOB lists Payroll among the roles, covering the Payroll menu and payroll and employee reports among other things, and lists the Administrator role as all features and functions.
- Expected result
- Each export carries only the fields its recipient needs. Roles that reach payroll are held only by people on the payroll work.
- Evidence to keep
- The field list for each export, the list of people with payroll access, and the date.
- Limits of this row
- Signs in and runs reports in a test organisation or test company file with invented employees only, never a client's live payroll, using the ledger's own features as any user would; one run per report or export and no load; any export that is emailed goes to an inbox the practice controls. The role check reads the W7 lists and sends nothing new. If a system in this row is a vendor's product, read the vendor's terms first and ask the vendor where they are unclear. If a report shows a real person's data, stop at once, note what appeared and the time, leave everything else unopened and hand the note to the practice's privacy contact.
W7. Xero and MYOB connections: users in client files
- Data involved
- Everything in each client's ledger file that a user can open.
- Who should reach it, and who should not
- Should: the client's own people, and practice staff working on that client. Should not: former staff, seasonal staff after their end date, people sharing one login, or a former practice after the client has moved on.
- Test case or check
- In each client file the practice works in, or a sample chosen before you look, read the list of users and note each person, their role and their status. In MYOB Business, MYOB says everyone with access is listed on the Users page, under the settings menu and Users and permissions, and that an Advisor's staff can only access the file with an email address on the same domain as the invited Advisor. Read each Xero organisation's user list the same way; Xero's MFA FAQ says everyone logging in to Xero who has access to an organisation needs MFA enabled on their account.
- Expected result
- Every user is a current person with a current reason to be there. Practice staff each sign in with their own login. Nobody on the list has left the practice or finished their season.
- Evidence to keep
- A dated list per client file of each user, their role or user type and their status, and what was done about anyone who should not be there.
- Limits of this row
- Read-only row: it signs in with your own login, reads a user list and changes nothing during the read. It opens no screen that shows a password, key or secret. Removing a user is a separate change, made with the client where the file is theirs.
W8. Xero and MYOB connections: connected apps
- Data involved
- Whatever each connected app was given access to when it was connected.
- Who should reach it, and who should not
- Should: apps the client or the practice still uses, each with a named owner. Should not: apps left from a trial, a former provider, or a staff member who has left.
- Test case or check
- For the practice's own ledger and each client file in the W7 sample, list the connected apps, who connected each one and when, where the ledger shows it, and what each is used for. Agree with the client which to disconnect.
- Expected result
- Each connected app has an owner, a purpose and a client who knows it is there.
- Evidence to keep
- A dated list per file of each app, its owner and purpose, and the decision made about it.
- Limits of this row
- Read-only row: it signs in with your own login, reads the list of connected apps and changes nothing. It opens no key, token or secret and copies none. Disconnecting an app is a separate change made after the review.
W9. Portal sharing and document links
- Data involved
- Final returns, financial statements and signed documents, shared in the portal or as links in an email.
- Who should reach it, and who should not
- Should: the client contacts each document was shared with. Should not: other clients, a visitor with no session where your setting says links need sign-in, and anyone using a link after its stated expiry or after the document is withdrawn.
- Test case or check
- Share one invented document with test client A through the portal and, if your practice sends them, as an emailed link to an address you control. Open each link once from client B's session, once with no session in a private window, once after its stated expiry and once after you withdraw the document.
- Expected result
- Client B is refused. The request with no session asks for sign-in, or is recorded as an open link if that is your setting. Expired and withdrawn links are refused.
- Evidence to keep
- Each kind of link, each response with the date and time, and the portal's sharing and expiry settings.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: four for each kind of link.
W10. Former clients
- Data involved
- The former client's documents and returns in the portal, and the practice's own user in the former client's ledger file.
- Who should reach it, and who should not
- Should: the practice, for the records it keeps. Should not: the former client's portal login after the date your process sets, sessions already open on that date, links sent earlier, or the practice's login in a ledger the client has taken elsewhere.
- Test case or check
- With test client A signed in on a second browser, close their portal access the way your offboarding steps say. Reload the open session once, sign in again once, and open a document link sent before the change once. For each real departed client, read the user list in their ledger file to see whether the practice is still on it. MYOB says an Advisor cannot remove their own access, and that an Owner, Online Admin or Advisor with the Administrator role must remove it.
- Expected result
- The open session ends, the new sign-in is refused and the old link is refused. ASVS 5.0.0 requirement 7.4.2 (Level 1) is that an application terminates all active sessions when a user account is disabled or deleted. The practice is off each departed client's file, or a removal request has gone to the client.
- Evidence to keep
- The three responses with the date and time, the offboarding step used, and for each departed client's file the user list and any removal request sent.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: three, as test client A. Reading a departed client's user list only reads and changes nothing.
W11. Seasonal staff
- Data involved
- Client files, TFNs and workpapers for the clients a seasonal staff member is assigned to.
- Who should reach it, and who should not
- Should: the seasonal staff member, with their own login, for assigned clients only, between their start and end dates. Should not: clients they are not assigned to, anyone after the end date, or a login shared between people.
- Test case or check
- Create invented seasonal staff member S with their own logins in the portal, the practice software and a test ledger file, assigned to test client A only. As S, request client B's record once by link or id. Then, with S signed in on a second browser, end S's access the way your season-end steps say, reload once and sign in again once in each system. Note which option the ledger used: MYOB describes making a user inactive as temporarily turning off their access, and says a user whose access is removed cannot sign in unless sent a new invitation, and that a user with the Administrator role cannot be made inactive.
- Expected result
- S is refused client B's record. After the end step, the open session ends and the new sign-in is refused in each system. ASVS 5.0.0 requirement 7.4.2 (Level 1) is that an application terminates all active sessions when a user account is disabled or deleted.
- Evidence to keep
- The request and the responses with the date and time, the end step used in each system, and the option the ledger used.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one as S before the end step, then two in each system after it.
W12. Outside bookkeepers
- Data involved
- The client's ledger and the documents the bookkeeper works from, plus anything the practice shares with them.
- Who should reach it, and who should not
- Should: the bookkeeper, for the clients who engaged them and the work they do. Should not: other clients' records, fields such as TFNs that the bookkeeping work does not need, or the practice's internal notes.
- Test case or check
- Give invented bookkeeper K the portal role your practice uses for outside bookkeepers, linked to test client A. As K, request client B's documents once by link or id, open client A's TFN field and look for internal notes. In MYOB Business, read the role K would hold: MYOB lists the Accountant/Bookkeeper role as all features and functions, excluding user management and all sections of the Dashboard.
- Expected result
- K is refused client B's documents, sees the TFN masked or not at all unless your rules say otherwise, and sees no internal notes. ASVS 5.0.0 requirement 8.2.3 (Level 2) asks that field-level access is restricted to consumers with explicit permissions to specific fields.
- Evidence to keep
- Each request and response with the date and time, a screenshot of K's view of client A, and the role K holds in each system.
- Limits of this row
- Sends requests: only to systems the practice runs or holds accounts in, using a staging copy if there is one, with test accounts and invented records; no load; only the requests listed here; every email or text it causes lands in an inbox or phone the practice controls. Invitation, reset and shared document links can let in whoever has them, so handle each one like a password: use it only for the test record and leave the link out of the evidence. If a system in this row is a vendor's product, read the vendor's terms before running it and ask the vendor where they are unclear. If another person's real data appears, stop at once, note the address and the time, leave everything else unopened and hand the note to the practice's privacy contact. Requests in this row: one as K for client B's documents, plus K's views of client A.
F1. Change freeze: the freeze notice
- Data involved
- The dates of the freeze, what is frozen (website forms, portal settings, integrations and ledger connections) and what stays exempt, such as security fixes and access removals.
- Who should reach it, and who should not
- Should: every staff member, seasonal staff included, and the person who approves exceptions.
- Test case or check
- Before the freeze starts, check that the notice names its dates, what is frozen, what is exempt and who approves an exception.
- Expected result
- One dated notice every staff member can find, with access removals listed as exempt.
- Evidence to keep
- The notice and its approval. May relate to: section 40(2) of the Tax Agent Services (Code of Professional Conduct) Determination 2024, which says the agent must document and enforce the policies and procedures of their system of quality management. Establish whether and how it applies to your practice with your adviser or the Tax Practitioners Board.
- Limits of this row
- Read-only row: it checks a document and sends no requests.
F2. Change freeze: access review before it starts
- Data involved
- The user lists for the portal, the practice software and client ledger files, and the apps connected to each.
- Who should reach it, and who should not
- Should: the person who runs the review and the principal who signs it off.
- Test case or check
- In the week before the freeze, run rows W7 and W8 and read the user lists in the portal and the practice software. Remove what should go before the freeze begins.
- Expected result
- Every login and connected app on the lists has a current owner and reason, and anything that should go is removed before the freeze begins.
- Evidence to keep
- The dated lists and the removals made. May relate to: section 11(1) of the TFN Rule (reasonable steps to ensure access to records containing TFN information is restricted to individuals who need to handle it for the purposes the section names) and APP 11.1 of the Privacy Act 1988 (reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure), each where it applies. Establish applicability with your adviser.
- Limits of this row
- Read-only row: it reads lists and changes nothing during the read. Removals are separate changes.
F3. Change freeze: seasonal staff register
- Data involved
- For each seasonal staff member: start and end dates, each login issued (portal, practice software and ledger files), the clients assigned, the supervisor and the training given.
- Who should reach it, and who should not
- Should: the practice manager and the supervising accountant. Should not: anyone outside the practice.
- Test case or check
- Check that the register matches the user lists from F2, and that each seasonal login has an end date and a named supervisor.
- Expected result
- No seasonal login without a register entry, and no register entry without an end date and a supervisor.
- Evidence to keep
- The register and a dated record of the training. May relate to: section 12 of the TFN Rule (reasonable steps to ensure all staff are aware of the need to protect individuals' privacy when handling TFN information, and that all staff who collect or access it are aware of the matters the section lists) and section 35(2) of the Tax Agent Services (Code of Professional Conduct) Determination 2024 (the agent must ensure that each entity providing tax agent services on the agent's behalf is appropriately supervised, having regard to the matters the section lists). Establish applicability with your adviser.
- Limits of this row
- Read-only row: it compares a register with user lists and sends no requests.
F4. Change freeze: exceptions log
- Data involved
- Each change made during the freeze: what changed, why, who approved it, and which rows were rerun afterwards.
- Who should reach it, and who should not
- Should: the approver and whoever made the change.
- Test case or check
- Check that each change made during the freeze has an approval and a rerun of the rows it touched, such as W9 after a change to portal sharing settings.
- Expected result
- Every exception is approved, dated and followed by a rerun with its result.
- Evidence to keep
- The log and the rerun results. May relate to: control questions in a client's or insurer's questionnaire, such as whether access is removed when staff leave, which the security questionnaires guide separates from organisation and assurance questions. The log can also sit with the documented policies and procedures in F1.
- Limits of this row
- Read-only row: it checks a log. Each rerun carries the limits of its own row.
F5. Change freeze: after it ends
- Data involved
- Seasonal staff logins, former clients' portal access, and the TFN information and other records gathered during the season.
- Who should reach it, and who should not
- Should: the practice manager, with the principal deciding what is destroyed and what is kept.
- Test case or check
- For each person leaving, close their access the way the W10 and W11 offboarding steps say and confirm from the F2 user lists that it is gone; rerun W10 and W11 themselves only with test client A and staff member S. Decide which TFN information to destroy or de-identify and which records to keep, and record each decision.
- Expected result
- Every seasonal login is closed or has a new end date, every former client's access is closed, and each retention decision is written down.
- Evidence to keep
- Dated results of W10 and W11, and a record of what was destroyed, de-identified or kept, and why. May relate to: section 11(2) of the TFN Rule (reasonable steps to securely destroy or permanently de-identify TFN information no longer required by law to be retained, or necessary for a purpose under taxation law, personal assistance law or superannuation law, including the administration of such law), section 30 of the Tax Agent Services (Code of Professional Conduct) Determination 2024 (records of the tax agent services provided to each client, including former clients, retained for at least 5 years after the service has been provided, for services within section 100(4)) and APP 11.2 of the Privacy Act 1988. These can pull in different directions, so settle with your adviser which records each one reaches.
- Limits of this row
- Read-only row for the records. Reruns of W10 and W11 carry those rows' limits.
F6. Change freeze: incident contacts
- Data involved
- Who to call if a row shows another person's real data, or anything worse: the person who handles privacy, the IT provider, the portal and ledger vendors' support channels and the insurer.
- Who should reach it, and who should not
- Should: every staff member, seasonal staff included.
- Test case or check
- Before the freeze starts, check that the list exists, names a person for each role and has been read by the people on it.
- Expected result
- One current list, read and acknowledged by everyone on it.
- Evidence to keep
- The list and the acknowledgements. May relate to: the Notifiable Data Breaches scheme, under which, the OAIC's page on the scheme says, an organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved; paragraph 26WE(1)(d) of the Act, under which section 26WE, headed Eligible data breach, applies where a file number recipient holds tax file number information relating to one or more individuals and is required under section 18 not to do an act, or engage in a practice, that breaches a section 17 rule that relates to that information; and any notice terms in a cyber insurance policy, which the cyber insurance security checklist covers. Establish applicability with your adviser.
- Limits of this row
- Read-only row: it checks a list and sends no requests.
Cyber security for accountants starts with where client data goes
This guide models a practice's working year as a run of steps, because its exposure follows that year.
A prospect fills in an enquiry form on the website. An engagement letter goes out for signature. The new client is invited to a portal, uploads identity documents and, if they are an individual, gives a tax file number (TFN).
Through the year the practice receives bank statements and payroll reports, prepares business activity statement (BAS) workpapers, and works inside the client's own ledger file as an invited user. Where a practice takes on seasonal staff at the busiest point of the year, each of them needs logins of their own.
When a client leaves, their documents and their links to the practice can stay behind until someone removes them.
Each of those steps puts client data somewhere a browser can reach, and only some of those places belong to the practice. The website and its forms may be the practice's own. Where the portal, the practice software, the email service and the client's ledger are run by vendors, the practice controls only its own accounts and settings inside them.
So for Australian accountants, cyber security is as much a question of accounts and access across systems other businesses run as it is about the practice's own website: who holds a login, what each login can open, and whether access ends when the reason for it does.
The reader in mind is whoever runs the practice or its systems: a principal, a practice manager or the person who looks after its technology. Nothing here is legal advice or a rating of any vendor's product.
It sets out the duties that may bear on a practice and where each one is written, and leaves the question of whether each applies to you with your own adviser. The matrix on this page is the part to use: one row per workflow step, each with a test you can run or hand to your developer, and a lane of evidence to keep around a tax-season change freeze.
The tax-season workflow, step by step
The steps below follow the rows of the matrix.
At each one the questions are the same: what data is involved, where it travels, and who can reach it once it arrives.
Tax practice website security starts with the forms: where the website is the practice's own, they are the first point in this workflow that it can test itself. An enquiry form collects names, contact details and a description of the client's affairs, and an engagement form may add entity details and authorisations.
Follow each submission to where it lands. One form can copy its contents into an inbox, a customer relationship tool and a portal at once, and every one of those copies is readable by a different set of people.
Read the confirmation page and email as well: a confirmation email that repeats what the client typed sends it on to an inbox the practice does not control.
The portal invitation comes next. Where whoever holds the invitation link can set up the account, how long the link lasts, whether it works a second time and whether the first sign-in asks for a second factor decide what a forwarded or intercepted invitation is worth. Row W2 checks each of those.
TFNs and identity documents can arrive at onboarding by a portal field, an uploaded scan or an email attachment; the matrix follows the portal field and the upload to wherever each copy ends up, and email attachments sit outside it. The Privacy (Tax File Number) Rule 2015, which its section 5(1) describes as legally binding, regulates the collection, storage, use, disclosure, security and disposal of individuals' TFN information.
Section 5(2) limits it to the TFN information of individuals: it does not apply to TFN information about other legal persons, including corporations, partnerships, superannuation funds and trusts.
Among other things, section 8(2) says that when a TFN recipient requests an individual's TFN, it must take reasonable steps to ensure the individual is informed of the taxation law, personal assistance law or superannuation law that authorises the TFN recipient to request or collect it, the purposes for which it is requested or collected, that declining to quote a TFN is not an offence, and the consequences of declining.
If an onboarding form asks for a TFN, the wording beside the field is the place to check against that list.
For the matrix, the question is where the TFN goes after the form: which staff roles see the full number, whether a notification email repeats it, and whether exports and reports carry it to people who have no use for it. Identity documents raise the same questions as any stored file: who can download a scan, whether its link works for another client or after sign-out, and where it is kept once identity has been checked.
The file upload security guide in this library covers what an upload form should accept and how stored files should be served.
A set of BAS workpapers can combine a client's transaction detail with the practice's own working: GST and PAYG calculations, reviewer notes and draft statements. In a portal or practice system they belong to one client and one job, and the test is whether they stay there. Can a second client open them by changing an id? Do internal reviewer notes appear on the client's side of the portal?
Payroll files need a row of their own, because the people in them are the client's employees, not the practice's clients, and a payroll report or export may carry their pay rates, bank details or TFNs. The matrix lists the fields each export actually contains, run in a test organisation or test company file with invented employees, before anyone decides who should receive it.
In MYOB Business, MYOB lists Payroll among the roles a user can hold, covering the Payroll menu and payroll and employee reports among other things, and it lists the Administrator role as all features and functions.
Reading the roles each user holds in the file is therefore part of finding out who can reach payroll.
Where a practice works in a client's Xero organisation or MYOB file as an invited user, each vendor's own pages describe that access in terms a practice can check.
MYOB's help pages say an accountant or bookkeeper is invited to a MYOB Business file as an Advisor, with the Administrator role, and that an Advisor can access all the MYOB Business files under the business's serial number, if it has more than one.
MYOB says an Advisor's staff can only access the file if they have an email address with the same domain as the invited Advisor, and that an Advisor adds, edits or removes practice staff in their practice software. Everyone with access is listed on the file's Users page, reached from the settings menu under Users and permissions.
MYOB says only an Owner, Advisor or Online Admin user type can access that page and add or remove other users, and that a File User with the Administrator role can view the page but cannot add or remove other users.
On sign-in, MYOB's page for accountants and bookkeepers says two-factor authentication has been mandatory since 30 June 2018, and that it is associated with the login rather than with the files being accessed.
Xero's multi-factor authentication FAQ says everyone logging in to Xero who has access to an organisation needs MFA enabled on their account, and that there are no limits on the number of users who can be invited into an organisation or client file. It suggests inviting new users instead of sharing login credentials, and warns that sharing a login brings more frequent requests to log in and authenticate, and that access to some key functionality might be blocked because the activity may be classified as suspicious.
The same FAQ says Xero has offered authentication as an optional feature since 2015, and that in Australia it became mandatory in 2018 due to what it calls the "Australian Tax Office's (ATO) Operational Framework".
This page makes no statement about what that framework contains or whom it covers; those are questions for the ATO.
Connected apps sit beside the users. The matrix treats each connected app as one more holder of access to the ledger, so the list of connected apps goes into the same review as the list of users: it reads that list and asks for an owner and a purpose for each app, rather than testing the apps.
If client data moves between systems through an automation tool, the Zapier guide in this library covers reviewing those connections.
At lodgement time the traffic runs the other way: returns, financial statements and signed documents go back to clients through the portal or as links in an email. Accounting client portal security comes down, at this step, to whether each shared document reaches only the people it was shared with.
A shared link is an access decision made once and then left in an inbox, so the matrix opens each kind of link from a second test client's session, with no session at all, after any expiry the portal states and after the document is withdrawn.
Whether a link should need a sign-in is the practice's decision. The test records which kind each link is, so that the decision is made on purpose.
Where access goes wrong in an accounting practice
The access tests in the matrix centre on four kinds of access.
Each comes down to an access control check, and each has a guide in this library that explains that check in depth, so this page names the guide and leaves the explanation to it.
- Former clients. Access can outlive the relationship in the client's login to the practice's portal and in the practice's login to the client's ledger. Closing the portal login is the practice's job, and the matrix checks that open sessions end with it, not only new sign-ins. Requirement 7.4.2 of ASVS 5.0.0 (Level 1) asks that the application terminates all active sessions when a user account is disabled or deleted. In MYOB Business, where the practice's login is an Advisor, closing it takes another user of the file: MYOB says an Advisor cannot remove their own access, and that an Owner, Online Admin or Advisor with the Administrator role must remove it. How a session ought to end is the subject of the session management guide.
- Seasonal staff. A seasonal accountant or administrator needs logins in the portal, the practice software and any client files they work in, for the clients they are assigned, between a start date and an end date. The failures to look for are a login that outlasts the season and a login shared between people. MYOB distinguishes making a user inactive, which it describes as temporarily turning off their access, from removing access, after which the user cannot sign in to the file unless sent a new invitation, and it says a user with the Administrator role cannot be made inactive. The authentication failures and MFA security guides cover sign-in and second factors.
- Bookkeepers. An outside bookkeeper may work in a client's ledger, send documents to the practice and hold a portal role. The questions are horizontal and field-level: can the bookkeeper's login open another client's records, and can it see fields, such as TFNs, that the bookkeeping work does not need? Requirement 8.2.3 of ASVS 5.0.0 (Level 2) asks that the application ensures field-level access is restricted to consumers with explicit permissions to specific fields. In MYOB Business, MYOB lists an Accountant/Bookkeeper role with all features and functions, excluding user management and all sections of the Dashboard. The broken access control guide covers the two-account method the matrix uses.
- Document links. A link to a return or a scanned licence is a reference to a record, and the server has to check, each time the link is used, that the person holding it may have that record. The OWASP test for insecure direct object references in WSTG v4.2 (WSTG-ATHZ-04) says the best way to test for direct object references would be by having at least two (often more) users to cover different owned objects and functions, which is why the matrix uses two test clients. The sensitive data exposure guide covers what a response should contain once access is allowed.
Privacy, TFN and tax agent rules, and what clients and insurers ask
The laws and instruments below speak to how a practice handles client information.
Each is described below as its own text states it, with who it covers. Whether each one applies to your practice, and what it asks of you in particular, is for you to establish with your own adviser, the regulator concerned or your professional body. This page does not answer that question for any reader.
Australian Privacy Principle 11.1 says that if an APP entity holds personal information, it must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure, and APP 11.3 says those steps include technical and organisational measures.
APP 11.2 says that where an APP entity holds personal information it no longer needs for any purpose for which it may be used or disclosed under the Principles, the information is not in a Commonwealth record, and no Australian law or court or tribunal order requires it to be kept, the entity must take such steps as are reasonable in the circumstances to destroy the information or to ensure it is de-identified.
Where client information goes overseas, APP 8.1 says that before an APP entity discloses personal information about an individual to an overseas recipient, meaning a person who is not in Australia or an external Territory and who is not the entity or the individual, it must take such steps as are reasonable in the circumstances to ensure the overseas recipient does not breach the Australian Privacy Principles, other than APP 1, in relation to the information, and APP 8.2 sets out cases where APP 8.1 does not apply.
Who those principles reach is a question of definitions. Section 6(1) of the Privacy Act 1988 says APP entity means an agency or organisation, and section 6C(1) defines an organisation as an individual, body corporate, partnership, other unincorporated association or trust that is not a small business operator, a registered political party, an agency, a State or Territory authority or a prescribed instrumentality of a State or Territory.
Under section 6D(1), a business is a small business at a time in a financial year if its annual turnover for the previous financial year is $3,000,000 or less, and section 6D(2) sets a different test for a business that was not carried on at any time in the previous financial year.
Section 6D(3) says a small business operator is an individual, body corporate, partnership, unincorporated association or trust that carries on one or more small businesses and does not carry on a business that is not a small business.
Section 6D(4) then lists entities that are not small business operators even so, among them one that carries on a business that has had an annual turnover of more than $3,000,000 for a financial year that has ended after the later of when it started to carry on the business and the commencement of the section, and one that is a contracted service provider for a Commonwealth contract; section 6D(9) adds that a body corporate is not a small business operator if it is related to a body corporate that carries on a business that is not a small business.
Section 6E(1A) says that if a small business operator is a reporting entity, or an authorised agent of one, because of anything done in the course of a small business it carries on, the Act applies, with the prescribed modifications (if any), in relation to its activities carried on for the purposes of, or in connection with, activities relating to the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 or regulations or AML/CTF Rules under that Act, as if it were an organisation.
Whether a practice is a reporting entity under that Act is a question for AUSTRAC or your adviser, and this page does not answer it.
The OAIC's page on the Notifiable Data Breaches scheme says that, under the scheme, an organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved.
In the Act itself, section 26WA says Part IIIC sets up a scheme for notification of eligible data breaches, and Part IIIC names tax file numbers directly: under paragraph 26WE(1)(d), section 26WE applies where a file number recipient holds tax file number information relating to one or more individuals and is required under section 18 not to do an act, or engage in a practice, that breaches a section 17 rule that relates to that information.
Section 3 of the TFN Rule says it is issued by the Privacy Commissioner under section 17 of the Privacy Act, and section 18 of the Act says a file number recipient shall not do an act, or engage in a practice, that breaches a rule issued under section 17.
Section 11(1) of the Act says a person who is, whether lawfully or unlawfully, in possession or control of a record that contains tax file number information shall be regarded, for the purposes of the Act, as a file number recipient.
Under paragraphs 11(2)(a) and (d), and subject to subsection (3), where such a record is in the possession or under the control of a person in the course of the person's employment in the service of or by a person or body other than an agency, the file number recipient in relation to that record is taken to be the person's employer.
Section 6(2) of the Rule gives TFN recipient the same meaning as file number recipient in the Privacy Act.
Section 5(3) of the Rule says a breach of the Rule is an interference with privacy under the Privacy Act, and that unauthorised use or disclosure of TFNs can be an offence under the Taxation Administration Act 1953.
Section 11(1) of the Rule says TFN recipients must take reasonable steps to protect TFN information from misuse and loss, and from unauthorised access, use, modification or disclosure, and to ensure that access to records containing TFN information is restricted to individuals who need to handle it for taxation law, personal assistance law or superannuation law purposes.
Section 11(2) says a TFN recipient must take reasonable steps to securely destroy or permanently de-identify TFN information that is no longer required by law to be retained, or necessary for a purpose under those laws, including the administration of such law.
Section 12 says TFN recipients must take reasonable steps to ensure that all staff are aware of the need to protect individuals' privacy when handling TFN information, and that all staff who collect or access it are aware of the matters the section lists, among them the prohibitions on its use and disclosure. Rows W3, F2, F3 and F5 of the matrix are built around these sections.
Section 30-5 of the Tax Agent Services Act 2009 says the Code of Professional Conduct applies to a registered tax agent or BAS agent. Its confidentiality item, section 30-10(6), says that unless the agent has a legal duty to do so, the agent must not disclose any information relating to a client's affairs to a third party without the client's permission.
Whether putting client information into a particular system or vendor is a disclosure to a third party is a question for your adviser or the Tax Practitioners Board.
The Tax Agent Services (Code of Professional Conduct) Determination 2024 adds obligations under section 30-12 of the Act, and sections 30, 35 and 40 of it touch the matrix. Section 30(1) says the agent must keep records that correctly record the tax agent services provided by the agent, or on the agent's behalf, to each client, including former clients, and section 30(2)(b) says the records must be retained for at least 5 years after the service has been provided.
Section 100(1) says that, except as otherwise provided in the instrument, the obligations included in it on the day it commenced apply on or after 1 July 2025 for an agent with 100 employees or less as at 31 July 2024, counted as section 100(2) sets out, and on or after 1 January 2025 otherwise.
Section 100(3) says that for an agent who leaves one registered firm for another between the commencement day and 30 June 2025, which of those dates applies at a particular time depends on which firm they were with at that time, and section 100(4) says section 30 applies to tax agent services provided on or after the day the section begins to apply to the agent.
Section 35(2) says the agent must ensure that each entity providing tax agent services on the agent's behalf is appropriately supervised, having regard to its knowledge and skills, the services it provides and the agent's system of quality management.
Section 40(1) and (2) say the agent must establish and maintain a system of quality management, in relation to the tax agent services provided by the agent or on its behalf, designed to provide reasonable confidence that the agent is complying with the Code, and must document and enforce its policies and procedures; its Note 1 says such a system includes policies and procedures relating to, among other things, protecting confidentiality of information and the recruitment, training and management of employees.
Keeping a former client's records and keeping their login open are separate decisions. The matrix treats them separately, in rows W10 and F5.
Some requests arrive from the other direction: a business client's supplier questionnaire, or a cyber insurance proposal form at renewal. The security questionnaires guide sorts such questions into those about the organisation, those about whether a control exists and those about how you know, and shows which of them a test report can evidence.
The cyber insurance security checklist covers proposal forms. The evidence lane in the matrix produces dated records of access reviews and of access removed when staff leave; whether a record supports a particular answer is for you, and the person asking, to judge.
Before you run the matrix
The matrix is written for systems your practice runs or holds accounts in, tested by you or by a developer or tester you authorise in writing.
It is not for anyone else's system. Rows W1 to W12 follow the workflow, and rows F1 to F6 are the change-freeze evidence lane. Each row carries its own limits, and the limits are part of the test.
- Set up test roles, never real ones: two invented clients, A and B; an invented seasonal staff member, S, with an end date; and an invented outside bookkeeper, K. Client A doubles as the former client in row W10. Give each of them an inbox and a phone number the practice controls.
- Use a staging copy of the website and portal where one exists. For the payroll and ledger tests, use a test organisation or test company file with invented employees and transactions, never a client's live file. Rows W7 and W8, and the ledger check in W10, read user and app lists in real client files, and they only read.
- For any system a vendor runs, read the vendor's terms before you send it anything beyond ordinary use, and ask the vendor where the terms are unclear. Nothing on this page says what a given vendor allows.
- Keep every test small: the requests the row names and no more, no load and no automated guessing. Every email or text a row sets off should land in an inbox or phone the practice controls.
- Treat invitation, reset and shared document links as secrets, because they can work for whoever holds them. Open each one only for the invented record it was made for, and describe it in the evidence without copying the link itself.
- Use placeholder values, never a real person's TFN, licence or bank details. Agree a placeholder TFN value with whoever runs the form, chosen so that it is not a real person's number.
- Should a row bring up a real person's data, halt there. Note what appeared, the address and the time, go no further, and pass it to the person who looks after privacy in the practice. The duties above, read with your adviser, decide what happens next.
- Write the expected result before you run each row, from your own rules, and keep the evidence for passes as well as failures. A dated pass is what lets you say later that a check was made.
- Change nothing except what the row says, and reverse each change afterwards: restore test accounts, delete test documents and list anything you could not remove.
A tax-season change freeze, and the evidence to keep
A change freeze is a practice's own decision to stop changing its website, portal settings, integrations and ledger connections during its busiest weeks, so that nothing new breaks while lodgements are going out.
None of the laws or instruments on this page is quoted here as asking for one, and a freeze has a cost: one that also stops access removals keeps seasonal and departed staff logins alive for as long as it lasts. The matrix therefore lists access removals as exempt.
The evidence lane turns the freeze into records. Before it starts, write down what is frozen and what is exempt (row F1), and run the access review while there is still time to act on it (F2). Keep a register of seasonal staff, their logins and their end dates (F3).
Log every exception made during the freeze and rerun the rows it touched (F4). When it ends, close access for everyone leaving the way the offboarding steps say, confirm from the user lists that each login is gone, rerun W10 and W11 with the test roles, and decide what TFN information to destroy or de-identify and which records to keep (F5). Keep the incident contacts ready throughout (F6).
Each F row names the duty or request it may relate to. Two of those duties can pull in different directions, which is the reason to write both down. Section 11(2) of the TFN Rule concerns taking reasonable steps to securely destroy or permanently de-identify TFN information that is no longer required by law to be retained, or no longer necessary for a purpose under the laws it names, including the administration of such law, and section 30(2)(b) of the Determination says records of the tax agent services provided must be retained for at least 5 years after the service has been provided. Which records each one reaches is a question for your adviser.
What the matrix cannot tell you
The matrix tests the accounts, links and settings you can see, on the day you run it, for the test roles you created.
A clean row is a result for that row, that build and those accounts, and nothing wider.
- Vendor platforms. Whether a portal, practice system or ledger enforces its own rules everywhere is a question for its vendor and whatever evidence the vendor offers. Your rows show how your own instance behaved for your own test accounts.
- Anything not on the list. A form, inbox, shared drive or connected app that nobody listed has no row. The access review is only as complete as the inventory behind it.
- Email and devices. Documents sent as attachments, staff laptops and phones, and the email accounts themselves sit outside a review of the website and portal.
- People with valid access. A seasonal staff member who copies files to a personal drive while their login is valid passes every access test in the matrix.
- Legal questions. Whether a duty on this page applies to your practice, and whether what you do meets it, is for your adviser. The matrix records what you did and when.
Which Clever Ops service fits which part of a practice
The testing Clever Ops offers covers what customers use through a browser or an API; in a practice, those customers are its clients.
Three services match that ground. For a practice website where the only people who log in are its editors, the website security check reviews only what is visible to a visitor who has not signed in, from certificates, transport security and security headers to cookie settings, exposed files and admin paths, and the software versions visible from outside.
A practice website built on WordPress fits the WordPress security audit instead: it follows every role able to log in and examines the login and password-reset flows, then the version of each installed plugin and theme, with evidence.
A custom client portal that customers or staff sign in to fits the web application and API penetration test, whose scope calls for two test accounts in every role so that people holding the same role, such as two clients, can each be tested against the other. How a test runs, from scope through to retest, is set out in the methodology guide.
A portal, practice system or ledger that a vendor runs belongs to that vendor, and Clever Ops does not test a product or platform that belongs to a vendor. The read-only rows in the matrix are how a practice reviews its own accounts and settings inside those systems.
Where a business client's questionnaire, an insurer or a tender asks for a CREST-accredited tester, Clever Ops is not CREST accredited, so we refer that work to a provider that is. What Clever Ops hands over is a test report, which is evidence for someone else to weigh and not a certificate.
If we built or host the system, we call the work a security review rather than an independent test, and our report records which party built the system and which hosts it.
Frequently asked questions
It depends on facts this page cannot see. The definition of organisation in section 6C(1) of the Privacy Act 1988 excludes a small business operator. Under section 6D(1) a business is a small business at a time in a financial year if its annual turnover for the previous financial year is $3,000,000 or less, section 6D(2) sets a different test for a business not carried on in the previous financial year, section 6D(3) defines a small business operator, and sections 6D(4) and 6D(9) list entities that are not small business operators even so. Sections 6E and 6EA set out when a small business operator is treated as an organisation. The tax file number provisions use a different term: section 11(1) regards a person who is, whether lawfully or unlawfully, in possession or control of a record that contains tax file number information as a file number recipient, and section 18 says a file number recipient shall not do an act, or engage in a practice, that breaches a rule issued under section 17, the power the TFN Rule is made under. Ask your adviser how these provisions apply to your practice.
Xero's MFA FAQ suggests inviting new users instead of sharing login credentials, and says there are no limits on the number of users who can be invited into an organisation or client file. MYOB says two-factor authentication is associated with each login rather than with the files it opens, and that an Advisor adds, edits or removes practice staff in their practice software. A login per person also lets the end of the season close one person's access without touching anyone else's, which rows W11 and F3 of the matrix check.
That is the practice's decision, and it is worth making on purpose. Keeping a former client's records and keeping their login open are separate questions. Section 30 of the Tax Agent Services (Code of Professional Conduct) Determination 2024 says a registered tax agent's or BAS agent's records of the tax agent services provided to each client, including former clients, must be retained for at least 5 years after the service has been provided, for services to which section 100(4) applies it. Row W10 of the matrix checks that a closed login, its open sessions and its old document links all stop working, and whether the practice is still a user in the former client's ledger.
No. A product or platform that belongs to a vendor is not something Clever Ops tests. A practice can review its own instance of those systems, meaning its accounts, roles, links and settings, with the matrix on this page, after reading the vendor's terms. What Clever Ops can test is what the practice itself runs for clients: its website, a WordPress site, or a custom client portal that clients sign in to.
It is a practice's own decision to stop changing its website, portal settings, integrations and ledger connections during its busiest weeks. None of the laws or instruments described on this page is quoted here as asking for one. What they do speak to, such as restricting access to records containing TFN information and documenting the policies and procedures of a system of quality management, is why the matrix keeps an evidence lane around the freeze: a written notice, an access review before it, a log of exceptions during it and offboarding after it, with access removals exempt throughout.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.