Cyber attack in the family office: reporting is the safer course
Twenty-four hours. That is how long a portfolio manager licensed by FINMA has to report a material cyber attack to FINMA. The deadline starts on discovery. For outsourced functions, it may already be running before the executive board learns of the attack.
In October, in my article on cybersecurity in the boardroom, I asked who decides on a ransom demand and at what point a reporting duty applies. For portfolio managers and family offices licensed by FINMA, the second question can be answered precisely. Besides FINMA, there are up to two further recipients, and each follows its own threshold. Where there are links to Liechtenstein, a report under EEA law may be added, depending on the set-up. This article is limited to Switzerland.
A single family office that manages exclusively the assets of persons with whom it has economic or family ties is, in principle, not subject to the Financial Institutions Act (Art. 2 para. 2 let. a FinIA). A FINMA licence can nevertheless make sense. In my experience, the administrative effort of dealing with banks and other financial service providers without a licence can be greater than the effort of the licence itself and the regulation that follows from it. For a single family office without a licence, FINMA and the supervisory organisation drop out. The duty to report to the Federal Data Protection and Information Commissioner (FDPIC) remains.
Three reporting channels, one initial assessment
FINMA: Supervised institutions must report to FINMA without delay any incidents of material significance for supervision (Art. 29 para. 2 FINMASA). FINMA Guidance 05/2020 specifies ‘without delay’ for cyber attacks as an initial report within 24 hours. The full report follows within 72 hours via the survey and application platform (EHP), which is accessed through the FINMA portal. Once the case is closed, FINMA requires a root cause report whose scope depends on the severity.
The supervisory organisation: Ongoing supervision of portfolio managers lies with a supervisory organisation (Art. 61 FinIA). A separate reporting duty applies towards it, worded identically to the duty towards FINMA (Art. 43l para. 2 FINMASA). The law sets no deadline in hours. I recommend informing the supervisory organisation at the same time as the initial report to FINMA.
The FDPIC: The FDPIC must be informed as soon as possible if a data security breach is likely to result in a high risk for the data subjects (Art. 24 FADP). Mandatory reports go through the DataBreach reporting portal; their content is governed by Art. 15 DPO. Breaches must be documented, and the documentation kept for at least two years (Art. 15 para. 4 DPO). Personal data means information relating to natural persons. As soon as KYC files listing beneficial owners or family members are affected, data protection comes into play.
The Federal Office for Cyber Security (NCSC) is not a recipient in this case: In the financial sector, the reporting duty under the Information Security Act covers only undertakings subject to the Banking Act, the Insurance Supervision Act or the Financial Market Infrastructure Act (Art. 74b para. 1 let. e ISA). Portfolio managers are not among them.
The three channels differ in threshold and deadline. In an emergency, a single initial assessment that answers all three questions in one pass is therefore helpful.
When an attack is material
A successful or partially successful attack on critical assets that endangers the availability, integrity or confidentiality of a critical function must be reported to FINMA. Each institution determines for itself which functions and assets are critical. Without this inventory, the initial assessment lacks a basis. In its Guidance 03/2024, FINMA found that institutions often had no complete inventory of their service providers and had not clearly defined what their critical data is.
For classification, Annex 1 of Guidance 05/2020 sets out three severity levels. For the availability criterion, it measures the outage against the recovery time objective (RTO), the defined target time for restoring operations. An outage of more than 50 per cent of the RTO counts as medium, from the RTO onwards as high, and above 200 per cent as severe. What is required once the case is closed depends on this, from a forensic report to a root cause analysis with evidence on the crisis organisation. Without a defined RTO, this criterion cannot be applied.
The initial report may be provisional
Guidance 03/2024 takes much of the weight off the initial report. It is made informally by e-mail or telephone and states what is known so far. If the severity is still unclear after 24 hours, the report is made on time anyway. If it later turns out that the threshold was not reached, the report can be withdrawn at any time.
The deadlines count on bank business days. Attacks of severity ‘severe’, however, must be reported within 24 hours at weekends too. The FDPIC takes a similarly pragmatic view: according to its guidelines on Art. 24 FADP, a report should be made without waiting for lengthy clarification.
Anyone who waits for certainty risks missing the deadline. I consider this the critical point in an emergency. Releasing an incomplete report is harder than writing it.
Your service provider sets your deadline
According to FINMA, for several years more than half of successful attacks on supervised institutions have affected their supply chain (Guidance 03/2024). For outsourced functions, the deadline starts according to FINMA as soon as the third-party provider discovers the incident. FINMA bases this rule on its Circular 2018/3 on outsourcing, which does not apply to portfolio managers. I recommend applying the rule nevertheless, because Art. 14 FinIA requires delegated third parties to be carefully instructed and monitored, and FINMA states in Guidance 03/2024 that an institution remains responsible for regulatory requirements at all times, including when outsourcing. With client data, every hour counts in any case, because in the end it is the clients who suffer the damage.
For the contract with the IT service provider, this results in a clear requirement: the provider reports cyber incidents immediately, through a defined channel and within a deadline measured in hours. To do so, it needs monitoring and reporting processes that work around the clock, because attackers keep no office hours. If it processes personal data on behalf of the family office, it must in any case report every data security breach to the family office as soon as possible (Art. 24 para. 3 FADP). According to the FDPIC, the level of risk is irrelevant here.
Why reporting is the safer course
Failing to report is not directly punishable under FINMASA. Concluding from this that silence carries less risk would be a fallacy.
The duty to provide information remains: The audit firm and the supervisory organisation are entitled to all necessary information (Art. 25 and 43l para. 1 FINMASA). In years without an audit, the portfolio manager also submits a report to the supervisory organisation on whether its business activities comply with the law (Art. 62 para. 3 FinIA). Anyone who has concealed a reportable incident must either disclose it there or gloss over it. Giving false information to FINMA, the supervisory organisation or the audit firm is a criminal offence (Art. 45 FINMASA), as is the breach of duties towards the audit firm (Art. 47 FINMASA). The penalty ranges up to three years’ imprisonment for intent and up to a fine of CHF 250,000 for negligence.
Supervision acts regardless: If FINMA learns of an incident by other means, it ensures that compliance with the law is restored (Art. 31 FINMASA). In serious cases, it can ban those responsible from acting in a senior function at a supervised institution for up to five years (Art. 33 FINMASA). The FDPIC can order the report to be made (Art. 51 para. 3 let. f FADP).
For me, the balance is clear. A provisional, correctly labelled initial report protects the institution and its governing bodies. Silence shifts the risk to a later point, when it is greater.
Four checkpoints for the board of directors
- Inventory: Critical functions, assets and material service providers, including subcontractors, are recorded and up to date.
- Reporting chain around the clock: Initial assessment and reporting also work at night and at weekends, 365 days a year. The contact routes to FINMA, the supervisory organisation and the FDPIC are recorded in the incident response plan. The route to FINMA is best clarified in advance, for example via assetmanagement@finma.ch, the address FINMA gives portfolio managers for licensing questions.
- Contracts with service providers: IT service providers report cyber incidents immediately and through a defined channel.
- Exercise: At least once a year, a tabletop exercise that includes the reporting process and the crisis organisation. FINMA expects this from institutions subject to Circular 2023/1. For portfolio managers, Guidance 03/2024 can serve as a reference.
Working document for download
I have summarised the processes, thresholds and deadlines in a presentation suitable for the next meeting of the board of directors or the executive board: Cyber Attack: FINMA Reporting Process for Portfolio Managers and Family Offices (PDF, 12 slides). You can request the document using the form at the end of this article.
An incident response plan that names only FINMA covers just one of up to three reporting channels for a portfolio manager. This gap can be closed before it is needed.
As at 20.11.2026. This article provides a general overview and does not replace legal advice in individual cases.
Transparency note
Generative AI was used in support of research and editorial preparation for this article. The conceptual design, the selection and weighting of content, the professional assessment, the final version of the text and responsibility for all statements and conclusions lie with me.
Sources
- FINMA (2020): FINMA Guidance 05/2020. Duty to report cyber attacks pursuant to Article 29 para. 2 FINMASA. German original
- FINMA (2024): FINMA Guidance 03/2024. Findings from FINMA’s cyber risk supervision, clarification of FINMA Guidance 05/2020 and scenario-based cyber risk exercises. German original
- FINMA: Circular 2018/3 ‘Outsourcing’, current version. FINMA circulars
- FINMA: Circular 2023/1 ‘Operational risks and resilience – banks’. FINMA, German original
- FDPIC (2025): Guidelines on reporting data security breaches and informing data subjects in accordance with Article 24 FADP, version 1.2 of 23.04.2025.
- Financial Market Supervision Act (FINMASA), Art. 25, 29, 31, 33, 43l, 45 and 47. Fedlex
- Financial Institutions Act (FinIA), Art. 2, 14, 61 and 62. Fedlex
- Federal Act on Data Protection (FADP), Art. 24 and 51. Fedlex
- Data Protection Ordinance (DPO), Art. 15. Fedlex
- Information Security Act (ISA), Art. 74b; available in German, French and Italian only. Fedlex
Request the working document
Cyber Attack: FINMA Reporting Process for Portfolio Managers and Family Offices (PDF, 12 slides)
Please enter your details. You will receive the download link by e-mail.