FMA Cyber Incident Notification for FAPs: Current Rules and the 72-Hour Proposal

FMA cyber incident notification is the duty, under the full financial advice provider (FAP) licence conditions, to tell the Financial Markets Authority about an event that materially impacts the information security of critical technology systems. The current deadline is 10 working days after discovery. A 72-hour limit is under consultation and is not yet in force.

 

Late on a Friday, an adviser’s Microsoft 365 account starts sending emails nobody wrote. The advice platform is run by another company, the IT provider works under a separate agreement, and the principal is on leave.

Someone at the firm now has to work out what happened, whether it matters to the regulator and who tells the FMA. Every one of those answers depends on facts held by people outside the firm.

This guide covers FMA cyber incident notification as it stands today, what the October 2026 proposal would change, and the information a small advice firm needs from its suppliers to make the call in time. It was checked against the FMA’s published documents on 5 November 2026.

If your firm operates as an authorised body under another FAP’s licence, the same questions apply. Who assesses the event and who submits the notice needs to be agreed with the licence holder in advance.

The wider technology obligations of firms holding confidential client information are covered in our guide to IT for professional services firms. This page stays with the reporting question.

What must financial advice providers report to the FMA today?

Financial advice providers must report any event that materially impacts the information security of their critical technology systems within 10 working days of discovering it. The duty is standard condition 5 in the FMA standard conditions for full financial advice provider licences, in effect since 15 March 2021. It is the FMA cyber incident notification rule that every full licence holder works to now.

The condition defines information security as preserving the confidentiality, integrity and availability of information and information systems. Critical technology is anything whose disruption would materially affect the advice service or the firm’s other licence obligations.

The notice must describe the event, its impact on the advice service and on clients, and the remediation under way. The explanatory note adds that minor events, such as receiving a phishing email, do not need to be reported.

Condition 5 also requires a business continuity plan suited to the size of the firm, including outsourced arrangements such as the client data provider. FMA cyber incident notification belongs inside that plan, with names and contact details, so nobody has to invent the process during an incident.

Our guide to writing a business continuity plan covers the plan itself. The notification step is where an advice firm relies on facts from outside suppliers, and it is the step this guide works through.

What would the proposed 72-hour condition change?

The proposal would require notice as soon as possible, and no later than 72 hours, after discovering an event that materially impacts the operational resilience of critical technology systems. It is part of the FMA’s consultation on standard conditions for market services licences, which opened on 8 October 2026.

The FMA wants a single business continuity and technology systems condition across the licence types subject to it, and would extend it to consumer credit providers. Its consultation paper says the move to 72 hours affects only financial advice providers, because the other market services under this condition already work to that timeframe.

The draft standard conditions set out the proposed wording. The main differences from today’s FMA cyber incident notification rule are these.

Topic Current FAP condition Proposed condition
Deadline Within 10 working days of discovery As soon as possible, no later than 72 hours
Trigger Material impact on information security Material impact on operational resilience
Details to give Event, impact on service and clients, remediation Event, affected systems, impact, recovery timeline, remediation
Details not yet known Updates accepted through the FMA’s online form Draft guidance: provide as soon as possible
Materiality Guidance excludes minor events, such as a phishing email Draft guidance recommends documented, approved criteria
Business continuity plan Required; documentation described in guidance Documented and approved, in the condition itself
Status on 5 November 2026 In force Proposal only, not in force

The consultation paper says the switch from information security to operational resilience does not change the underlying obligation. The shorter reporting window is the main change for FAPs, alongside the requirement to have the plan approved.

The draft is written in hours rather than working days, so on its plain wording a weekend or public holiday counts toward the 72. That leaves three days for a firm used to roughly two calendar weeks, depending on weekends and holidays.

The FMA proposes that the new conditions apply six months after it gives licensees formal notice under section 405 of the Financial Markets Conduct Act. No start date has been set, and the timetable and wording remain subject to consultation.

Neither timeframe is permission to delay containment. The clock governs when the regulator hears about an event, and the response starts the moment the firm knows.

FMA cyber incident notification timeline: 10 working days today against a proposed 72-hour outer limit

When is a cyber event material enough to notify the FMA?

Under the current condition, an event needs FMA cyber incident notification when it materially impacts the information security of critical technology systems, meaning the confidentiality, integrity or availability of information or systems has been compromised. The draft frames the same test around operational resilience, with examples of events that materially disrupt the service or harm the people who receive it.

Neither version gives a checklist. The draft recommends that each licensee set its own materiality criteria to suit its size and risk, write them down and have them approved by whoever governs the firm.

Use the questions below to assess impact against the condition and your firm’s own criteria. A suspected event needs a prompt assessment, but appearing on this list does not by itself make it reportable.

  • Client data exposed. Personal or financial information has been, or may have been, viewed or sent without authority.
  • Advice service disrupted. Advisers cannot reach client files, the CRM or the advice platform for longer than the firm can tolerate.
  • Account taken over. A staff or administrator account was controlled by someone else, even briefly.
  • Supplier incident. A platform or provider reports an incident touching systems or data the firm relies on.
  • Records in doubt. Client records, documents or payment details may have been altered.

A blocked phishing email is not on that list. A mailbox that was accessed and used to email clients may well qualify.

The materiality decision belongs to the licence holder, made on the facts available at the time and recorded with its reasons.

Which systems and suppliers belong in your reporting arrangements?

Every system and supplier whose failure would materially affect the advice service belongs in the arrangements, whether it runs in the office or under an outsourcing contract. The draft condition says critical technology can be part of internal infrastructure or an outsource arrangement.

For a typical small advice firm, the list looks something like this.

  • Microsoft 365 or Google Workspace. Email, files and the accounts that open everything else.
  • The advice or CRM platform. Client records, fact finds, statements of advice and file notes.
  • Provider and insurer portals. Logins that reach client policies, applications and commission statements.
  • Devices. Laptops and phones used by advisers, including personal phones with work email.
  • Document storage and e-signature tools. Signed advice, identity documents and authorities.
  • The IT provider’s own tools. Remote access and management software with administrative reach into the firm.

For each one, record who runs it, how they would tell you about an incident and how quickly. Then read what each supplier’s terms promise.

A supplier that only undertakes to notify customers within seven days could delay when the firm learns of an incident, or leave it short of facts once it does. The reporting clock runs from the firm’s discovery, so raise that gap with the supplier before an incident rather than during one.

The draft explanatory note links this condition to the outsourcing condition for the same reason. Outsourcing a system does not outsource the duty to report on it.

What facts should your IT provider hand over for an FMA notice?

Your IT provider should hand over the facts the firm needs to judge materiality and write the notice: what was affected, when and how it was found, what is known about access or disclosure, what has been done, and what is still unknown. The decision stays with the firm, but it cannot be made without those facts.

A short working record, started on the first call, stops the facts drifting as people relay them. The format below is a suggestion. It is not an FMA form, and keeping it does not prove compliance on its own.

Field What to record
Affected service System, accounts and supplier involved
Discovery Date, time and source: alert, staff report or supplier
Known impact Clients, advice work or records affected so far
Confirmed facts What logs or the supplier have confirmed
Unknowns Open questions and when answers are expected
Action owner Who is containing and investigating, with contact details
Next update Time of the next report to the firm

Discovery time comes first, because both the current and the proposed clock run from discovery. Ask the provider to note when an alert fired, when a person first saw it and when the firm was told, because those times can be hours apart.

Separate what is confirmed from what is suspected. A notice built on a guess that later proves wrong creates more work than one that says clearly what is still being checked.

Keep the record in the incident file. The draft says the FMA may request more information about an event, and the record shows what was known at each point.

A record kept this way also shortens the notice itself. Much of the notice is the record rewritten as sentences, with the firm’s assessment of impact on its advice service and clients added.

Who decides, notifies and supplies updates?

The firm responsible under its licence arrangements assesses whether a notice is needed and submits it, while suppliers provide the facts and updates behind it. An authorised body should agree with the licence holder who assesses and submits, without assuming that removes its own obligations, and an engaged adviser follows the firm’s process. Write those roles down before an incident, with a deputy for each.

  • Decision-maker. The principal or a director, with a named deputy who can act when they are away.
  • Coordinator. The practice or operations manager who gathers facts, keeps the working record and drafts the notice.
  • Technical lead. The IT provider’s named contact for containment and evidence.
  • Platform contacts. The incident or security contact at each platform supplier, not the general helpdesk.
  • Compliance adviser. A compliance consultant or lawyer, if the firm uses one, for the materiality call.
  • Privacy officer. The person who assesses whether a privacy breach notification is also required.

In a small firm one person may hold three of these roles. That works, provided the deputy is written down and has the logins and contact list needed to act.

Our guide to building an incident response plan covers containment, response roles and testing. This guide adds only the regulatory reporting step for advice firms.

Notices go through the FMA’s online incident notification form in its Online Services portal. The FMA’s guidance on notifying operational incidents says the same form takes the first report, updates while the incident is open and a concluding report once it is resolved. If the portal cannot be reached, the guidance gives 0800 434 566 and compliance@fma.govt.nz.

Check before an incident who in the firm holds an Online Services login, and make sure the deputy can reach it too. A first notice can say what is still unknown and be updated as facts are confirmed.

Who else may need to hear about the same incident?

A cyber incident that triggers FMA cyber incident notification may also need to be reported elsewhere, each under its own test and timeframe, and the FMA notice does not stand in for any of them.

  • The Privacy Commissioner. A privacy breach that has caused or is likely to cause serious harm must be notified as soon as practicable, and affected people told unless an exception applies.
  • Your cyber insurer. Policies set their own notice requirements, and late notice can complicate a claim.
  • The licence holder. An authorised body or an adviser working under another FAP’s licence needs to tell that FAP quickly.
  • Product providers. Insurers and platforms whose portals were reached with compromised logins need to know.
  • Clients. People whose information or money is at risk need enough detail to protect themselves.

The facts in the working record serve every one of these reports. Collecting them once, from the IT provider and each platform, saves the coordinator asking the same suppliers the same questions three times.

The order of reports and the person responsible for each belong in the incident plan. The FMA notice is one line on that list, with its own deadline.

Check your cyber insurance policy for its notice clause and incident line. Some insurers arrange forensic and legal help through that line, which can feed facts straight into the working record.

What does a Friday afternoon mailbox incident look like?

A Friday afternoon mailbox incident shows how the roles and the working record fit together. The scenario below is illustrative and is not an Exodesk client case.

At 4.30pm on a Friday, an adviser reports that clients are replying to an email they did not send. The principal is overseas, and the firm’s advice platform is supplied by a separate company.

1

Contain the account

The deputy reaches the IT provider through the agreed contact route. Under agreed authority, IT blocks the account, revokes its sessions and checks for persistence such as mail rules, while preserving the logs.

2

Start the record

The coordinator notes the time of the adviser’s report, any alert time and the affected account.

3

Ask the platform

The platform supplier’s incident contact is asked whether the same credentials reach client records there, and whether its logs show unusual activity.

4

Establish the impact

The IT provider reports what the available logs show about messages sent, mail or files accessed and possible disclosure, names any logging gaps or open questions, and sets the next update time.

5

Make the call

The deputy and the compliance adviser assess materiality against the firm’s criteria, and the privacy officer assesses serious harm.

6

Notify and update

If the event is material, the notice goes in with what is known, and the record shows when the next update is due.

Not every mailbox compromise will meet the materiality threshold. One that sent messages to clients, or exposed client documents, needs a careful assessment.

If the proposed condition were adopted unchanged and this were a qualifying material event discovered at 4.30pm on Friday, the 72-hour outer limit would fall at 4.30pm on Monday. Notice would still be required sooner where possible.

Under the current condition the outer limit is 10 working days, and the facts the deputy needs are the same either way.

Supplier hand-off for FMA cyber incident notification: IT provider and platform facts flow to the firm decision-maker

What should your firm check before the conditions are finalised?

Check that your firm could gather the facts and make a decision inside 72 hours, including over a weekend, before the FMA settles the final wording. The consultation is open until 5pm on Friday 11 December 2026.

  • Supplier terms. How and when each platform and provider will tell you about an incident affecting your data.
  • Out-of-hours contact. Whether your IT agreement covers urgent calls at night and at weekends, and how to reach someone.
  • Named deputies. A second decision-maker and coordinator with the authority and access to act.
  • Materiality criteria. Written criteria, approved by whoever governs the firm.
  • The working record. A template ready to use, stored where the deputy can reach it without the principal’s laptop.
  • Business continuity plan. Documented and approved, as the draft would require.
  • A practice run. A tabletop walk-through of the Friday scenario above, timed against 72 hours.

A practice run finds the gaps that a document review misses: the platform contact who has left, the deputy without the admin login, the supplier whose incident line only answers on weekdays. A short first exercise is enough to expose gaps, and its length depends on the scope.

Firms that want to comment can respond through the submission form on the consultation page. The FMA has asked whether the proposals are clear and workable, what they would cost, and whether six months is enough time to prepare.

Recheck the FMA’s final conditions once they are published. This guide will be updated when they are.

Get Help With Supplier Escalation for Your Advice Firm

Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.

We work with advice firms and insurance brokers to map their suppliers, agree escalation contacts and keep the technical facts a notification decision depends on.

NEXT STEP

If your advice platform had an incident tonight, who would tell you, and how quickly?

Talk to Exodesk about your firm’s IT support and supplier escalation arrangements. Support hours, escalation and specialist work are agreed as part of the service, and regulatory decisions stay with your firm and its advisers.

Or read about our IT assessment for a wider review of your systems.

Frequently Asked Questions

Is the FMA’s 72-hour notification proposal in force?

No. On 5 November 2026 it is a consultation proposal, and until final conditions are issued and take effect, full licence holders work to the current 10 working day condition.

How long does a financial advice provider have to notify the FMA today?

Ten working days from discovering an event that materially impacts the information security of its critical technology systems. That is an outer limit, and containment should start straight away.

What if our firm operates under another FAP’s licence?

The FMA says the licensed FAP is responsible and accountable for an authorised body’s conduct, and that authorised bodies are subject to the same regulatory obligations. Agree with the licence holder how quickly you will tell them about an event, who assesses materiality and who sends the notice. Advisers engaged by a FAP should follow that FAP’s incident process.

Can an initial notification to the FMA be updated later?

Yes. The FMA’s online notification form already takes updates on an existing notification and a concluding report once the incident is resolved. The draft condition adds that details not available at discovery are to be provided as soon as possible.

Does notifying the FMA also cover privacy breach notification?

No. Under the Privacy Act, a breach that has caused or is likely to cause serious harm must be notified to the Privacy Commissioner as soon as practicable, and the affected people told unless an exception or permitted delay applies. The Office of the Privacy Commissioner’s guidance on privacy breaches explains the test. Our guide to NZ Privacy Act compliance covers the wider obligations.

Is a phishing email a reportable event?

Receiving one is not. The FMA’s explanatory note gives a phishing email as an example of a minor event that does not need to be reported. A phishing email that led to a compromised account, a changed payment detail or exposed client data needs a materiality assessment. Record the outcome either way, so the reasoning is on file if the FMA asks.

Does the proposed 72 hours include weekends?

The draft says 72 hours, not working days, so on its plain wording weekends and public holidays count. Plan contacts and deputies on that basis, and recheck once the final wording is published.

Does outsourcing our IT pass the notification duty to our provider?

No. Reporting stays with the firm responsible under its licence arrangements, and the draft condition treats outsourced systems as part of the firm’s critical technology. Your IT provider’s job is to tell you quickly and supply the technical facts.

How do we send a cyber incident notification to the FMA?

Through the FMA’s online incident notification form in its Online Services portal, which takes the first report, updates and a concluding report. If the portal is unavailable, the FMA’s guidance gives 0800 434 566 and compliance@fma.govt.nz. Make sure more than one person in the firm can log in.

Can Exodesk help advice firms in Christchurch and Dunedin prepare?

Yes. Our Christchurch and Dunedin teams support businesses nationwide, including advice firms and insurance brokers. We can map your suppliers, agree escalation contacts and set up the technical side of your reporting arrangements, while compliance decisions stay with your firm.

Contact us or call 0800 396 337 to talk about your firm’s incident reporting arrangements.

Start typing and press Enter to search

Health NZ security checklist: a medical practice connecting to a national health data hub through a secured gateMicrosoft 365 baseline security mode: admin settings switches protecting apps, files, meetings and devices Call Us Now