Skip to main content

Broker guide

Data Breach Response Plan for a Brokerage

Use an editable breach response plan for your brokerage. Assign roles, contain disclosure, assess harm and record notification and recovery decisions.

Published
Updated

A data breach response plan tells your brokerage who can stop a disclosure, who assesses the risk to clients and who decides what to report. Copy the fields below into a controlled document and fill in the names, backups and contact channels before a client file goes astray.

Set Up the Editable Response Plan

Activate the plan when anyone reports a suspected or confirmed loss, unauthorised access or disclosure of personal information. That includes a processor spotting a misdirected file link and a supplier reporting possible exposure in its systems.

  • Plan details. Brokerage [legal entity], owner [name], version [number], approved by [name and date], next review [date].
  • Activation. Report to [incident lead and secure channel]. If unavailable, contact [deputy and backup channel]. Record who activated the plan and when [timestamp and time zone].
  • Record location. Keep the blank plan at [staff-accessible location]. Open a case at [restricted incident register] and record the case ID [ID], access owner [name] and evidence location [restricted folder].

Fill in a primary contact and a deputy for each role. Give deputies the access and authority they need before an incident.

RoleAssignmentResponsibility
Incident lead[Primary, deputy, channel]Open the case, set priorities and approve recovery.
Technical lead[Primary, deputy, channel]Restrict access, preserve logs and verify the fix.
Privacy assessor[Primary, deputy, channel]Establish the facts, assess likely harm and make the statutory notification recommendation.
Communications owner[Primary, deputy, channel]Prepare approved notices, record delivery and handle client follow-up.

In a two-person brokerage, the owner might serve as incident lead and communications owner, with the other broker as deputy. The other broker might lead the privacy assessment and the managed IT provider might handle containment, each with a named backup. Put the first contact and escalation channel in your employee privacy policy so staff can find it without opening an incident file.

Contain the Incident and Preserve Evidence

Start with the fastest safe way to stop further exposure. The Office of the Australian Information Commissioner’s response guidance describes containment, assessment, notification and review. The incident lead can assign containment and assessment in parallel.

  1. Limit access. Revoke the exposed share link or remove the unauthorised recipient’s access. Check for other active links or inherited access that could leave the same file exposed.
  2. Stop further disclosure. Pause the message, workflow or file transfer that exposed the information. If the wrong recipient may have saved it, ask them through a verified channel to stop using or forwarding it and confirm any deletion. Record their response and any uncertainty about copies.
  3. Preserve evidence. Save the original message, relevant sharing settings, access logs and supplier ticket in the restricted case folder. Record the time range and time zone of the logs. Keep the original file and audit history while you restrict access.
  4. Escalate and record. The person who discovers the incident alerts the incident lead immediately. Log each action with [time], [person], [what they did], [result] and [evidence reference]. Label each material point as confirmed, reported or unknown.

For example, a processor sends a link to a fictional client’s payslip and identity document to the wrong recipient. The processor alerts the incident lead while the technical lead disables the link and checks that it no longer opens from an unauthorised account in a controlled test. The technical lead checks for views or downloads between sending and revocation and records any limits in the available logs.

Assess the Information and Likely Harm

Give the privacy assessor one record to work from. If a sharing log lacks download events or the recipient cannot confirm what they did, record access or copying as unknown.

  • People and scope. [Affected client references and count], [files and document types], [data fields exposed], [recipient and relationship to clients], [period of exposure].
  • Access evidence. [Sharing permissions], [views or downloads if recorded], [recipient response], [evidence references and gaps].
  • Remedial action. [What changed], [when], [what the evidence shows it prevented], [any copies or access still unaccounted for].
  • Likely consequences. [What a recipient could do with the information], [which clients face which consequences], [likelihood and seriousness], [reasoning and outstanding checks].
  • Assessment handoff. [assessor], [start time], [next decision time], [who will obtain missing evidence and by when].

A payslip can disclose income and employer details. If the same link also exposes identity information, consider the combined risk of impersonation or a convincing scam. Send unresolved questions to the incident lead with a deadline and use the notifiable data breach guide to assess whether the statutory notification threshold is met.

Record Remediation and Notification Decisions

Use a separate record for the statutory decision about notifying individuals and the Office of the Australian Information Commissioner (OAIC). The privacy assessor records the conclusion and gives the incident lead the reasons. Record the decision even if notification is unnecessary.

  • Decision record. [Case ID], [assessor], [decision and time], [facts and evidence], [effect of remedial action], [reason for notifying or not notifying], [approver], [remaining checks and review time].
  • Notice and delivery record. [Recipient or group], [subject and approved wording], [sender and approver], [channel and time sent], [acknowledgement or delivery failure], [follow-up owner and due time].
  • Client notice draft. “This is [brokerage name and contact details]. [Describe the incident in one sentence.] The kinds of information involved were [details]. To protect yourself, take [specific steps]. You can reach us at [verified contact channel] if you need help.”

If notification is required, use the OAIC reporting instructions to prepare the statement and check the information to include. Log regulatory notifications and client notices as separate deliveries so each can be followed up.

For each lender, aggregator, insurer or supplier involved, find the signed agreement or policy and check whether the facts trigger a report. Record [party], [agreement and clause], [trigger], [verified deadline and channel], [owner], [approval] and [delivery evidence]. A contract may require notice even when the assessor concludes that statutory notification is unnecessary.

Restore Operations and Check Recovery

Before making the file available again, confirm that an unauthorised test account cannot open the old link and that a fresh share gives access only to the intended accounts. Check whether a link can still be forwarded to someone without permission. Record who ran the checks, the results and where the evidence is saved.

Assign a contact for affected clients. Track each [client reference], [support offered], [response or action still needed], [owner] and [follow-up date] in the restricted case record.

The incident lead signs off recovery with [approval and time], [access test evidence] and [outstanding client or operational risks]. Move unfinished work into a remediation list with [action], [named owner], [due date] and [evidence needed to close]. For example, the original link might be disabled while the brokerage still needs to change the default sharing permissions for its processing team.

Rehearse a Brokerage Client-File Incident

Run a tabletop exercise using a dummy identity document and payslip marked as fictional. Use test accounts and an isolated folder. The facilitator tells the processor that the file went to the wrong recipient, then adds that the recipient opened the message and the log does not capture downloads.

Have the processor hand off to the incident lead and the technical lead demonstrate link restriction. Ask the privacy assessor to record how the missing download evidence affects the decision and the communications owner to prepare an unsent notice. Have a deputy take over one role and find the current decision, supporting evidence and next action from the incident record.

To pass the exercise, the old link must fail for the test recipient and the intended account must still have access. The decision log must name the approvers for the statutory and contractual decisions, and the client notice must be ready for approval.

After an exercise or incident, check who could be reached, what evidence was missing and where the handoffs stalled. Assign fixes, update the plan version and brief staff on what changed.

Bring policy research and scenario planning together

Ask lender policy questions, plan client scenarios and compare lenders in one conversation, with the policy wording behind each answer.
See how it works14 days free · No credit card