Does a processor have to notify the FDPIC of a data breach?
Direct answer
No. Under Article 24(3) of the Swiss Federal Act on Data Protection (FADP), a processor must inform the controller as quickly as possible of any breach of data security. The duty to notify the FDPIC sits with the controller, which decides whether the breach is likely to result in a high risk for the people concerned and must be notified.
What the processor owes
A processor must inform the controller of any breach of data security, as quickly as possible (Article 24(3) FADP). The duty is not limited to high-risk breaches: the processor reports, and the controller assesses.
What the controller then does
The controller decides whether the breach is likely to result in a high risk for the people concerned. If it is, the controller notifies the FDPIC as quickly as possible through databreach.edoeb.admin.ch. See how fast a data breach must be reported under the FADP.
What to do
- Controllers: keep processor contracts documented and current, and make sure each one says whom the processor must tell and how.
- Processors: know which controller each data set belongs to, and who its contact is outside office hours.
- Both: keep a record of the breach and of the time the controller was informed.
This is general information, not legal advice: scope depends on your facts, so confirm it with a qualified lawyer. Processor duties are one part of the FADP: see what a Swiss company must comply with, the Swiss FADP guide and what a data processing agreement is.
Processors and breaches in Acuna GRC
In Data Privacy in Acuna GRC, a DPA is generated for each processor, and the breach wizard records the affected activities, assets and third parties. Suppliers sit in one register in TPRM (Supplier Shield). See Data privacy management.
How Acuna GRC handles it
In Acuna GRC, Data Privacy generates a DPA for each processor and records the third parties affected by a breach.
- Module
Data Privacy
Processing activities, data inventory and flows, DPIAs, DPAs, TIAs, data subject requests and breaches, with a public privacy portal.
- Module
TPRM (Supplier Shield)
Suppliers, questionnaires, assessments and campaigns, with a supplier portal and supplier risk intelligence: daily scans condensed into an A to F grade, with breach and sanctions checks.
- Solution
Swiss FADP
Meet your revFADP duties: a record of processing, impact assessments for high-risk processing, access requests and breach reports to the FDPIC, with the GDPR.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
Does the processor’s duty depend on the level of risk?
No. A processor informs the controller of any breach of data security. Whether the risk is high is the controller’s assessment.
We process data for an EU controller. Which rule applies?
EU controllers impose GDPR terms on the processors they use, so expect the contract to set how and when you report a breach. See does the GDPR apply to Swiss companies?
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

