data breach

Data breach log template for Swiss SMEs

AA
Aurum Avis Labs Author
6 min read

Data breach log template

A data breach log template helps Swiss SMEs record what happened, what you did, and whether the FDPIC was informed, even when no external report is required. Art. 15 DSV expects documentation of data security violations with facts, effects and measures, kept at least two years from notification where applicable. Auditors and insurers ask for this file more often than for a perfect privacy policy PDF.

This checklist is for the privacy contact and management in firms with 20 to 250 staff. Pair it with reporting a breach to the FDPIC when high risk is likely. The guidance below is orientation, not legal advice.

  • Incident ID and date discovered
  • Who reported and who owns the case
  • Description of the breach type
  • Categories of data and approximate number of people
  • Whether sensitive data were involved
  • Immediate containment steps
  • Risk assessment: high risk likely or not
  • FDPIC notified yes or no, date and portal reference
  • Affected individuals informed yes or no
  • Follow-up measures and lessons

Write it down the same day, not “tomorrow in the log”

The usual gap is not a missing column but a missing day. Once you treat personal data as affected, open a row on the day of discovery. You may add detail later; do not delete earlier notes.

  1. Timestamp and reporting path

    Record time of discovery, who reported internally (role, not only a first name), and the channel used (phone, ticket, e-mail to privacy). That shows whether staff knew the internal path.

  2. Plain-language summary

    One sentence: “payroll PDF to wrong domain”, “USB with client files in a taxi”, “ransomware, backup status unclear”. No legalese required, but concrete enough for a stranger in two years.

  3. Data and people, roughly counted

    Categories (payroll, health, customer contacts) and an approximate number. “Twelve employees” is enough; do not paste a full name list into the log unless you must.

  4. Containment with times

    What happened in the first hours: password reset, recall of the e-mail, device locked, recipient confirmed deletion. Note a rough time for each step.

  5. First risk view

    State why high risk is or is not likely, using Swiss logic (FDPIC only when high risk is likely, “as soon as possible”), not only GDPR 72-hour habits from German articles.

  6. Decision on FDPIC and individuals

    Yes or no, who decided, date. If you notify, paste the portal reference the same day. If not, one sentence of reasoning, not only a tick box.

  7. Link evidence

    Deletion confirmations, portal screenshots, internal “do not forward” notes. Store them on the log row, not loose in a mailbox.

Log every serious incident, not only FDPIC cases

Wrong e-mails, lost USB sticks, ransomware with possible exfiltration, and rogue employee access belong in the log when personal data are involved. Trivial typos with no disclosure may need only a short note in a monthly review. When in doubt, log.

Full row makes sense

  • Data reached or could reach someone unauthorised
  • Health, payroll or customer data involved
  • Insurer, customer or audit may ask

Short note is often enough

  • Internal test with no real personal data
  • Typo in the address, message never sent
  • Near miss with no disclosure, tracked as a pattern in review

Fields explained briefly

Discovery date starts your internal clock, not the day the mistake happened if nobody knew. Data categories use plain language: payroll, customer contacts, health. Risk assessment should state why high risk is or is not likely. Measures list wipe, password reset, recall of e-mail where possible, and policy changes. Owner uses surname and role, not only “IT”.

  • RetentionAt least 2 years

    From FDPIC notification when you notified. Use the same habit for non-notified cases when staff change.

  • AccessKeep it tight

    Privacy contact, HR lead, management write. No public share folder.

  • HR fileSeparate

    Link disciplinary files and breach logs by incident ID only.

When risk changes after the first entry

If the assessment rises, update the row or add a follow-up row with a date. Add FDPIC portal timestamp and reference if you notify. Keep earlier notes visible. Store the FDPIC guide on reporting beside the template so fields match portal questions.

A made-up example: spreadsheet that survived staff change

A made-up example: a 30-person marketing agency keeps one password-protected spreadsheet as its breach log. A designer sends a newsletter test list to the wrong domain on Tuesday 09:40. The office manager opens a row before lunch: discovery time, 412 e-mail addresses, no health data, recipient deleted mail on request at 10:15, risk moderate, no FDPIC report with reasoning “known recipient, confidentiality in contract”, deletion confirmation attached. Two years later a new HR lead still sees the pattern and plans autocomplete training, noted in a “training” column without naming anyone in the session.

Sample row in prose

Incident 2026-047, discovered 14 March 09:15, reported by finance clerk, owner HR. Type: misdirected e-mail with twelve payroll PDF attachments. Data: employee salary, twelve people, not health. Containment: recall request to wrong recipient within one hour, confirmation received. Risk: internal recipient known, binding confidentiality in contract, assessed as no high risk. FDPIC: no. Individuals: informed internally only. Follow-up: Bcc rule for payroll, repeat training slot June.

  • Misdirected e-mail

    Same day: recipient, attachment type, recall or deletion request, recipient’s reply. Without that row you cannot later show that you acted.

  • Lost device

    Serial number, last sync, whether remote wipe ran, whether the backup was current. Name IT and the privacy contact as owners in the log.

  • Suspected third-party access

    Time window, affected systems, password resets, whether logs were exported. Risk is often unclear at first: open the row anyway with “assessment open” and a follow-up date.

Tool choice and review rhythm

Excel on a secured share, Notion with access log, or a ticket in your IT system all work. Consistency beats software brand. Number incidents sequentially per year. Quarterly management glance: how many rows, repeat causes, open follow-ups. Monthly export with date if you use a spreadsheet; version history if you use SharePoint.

When the privacy contact leaves, hand over the log, password rules and one anonymised example in writing. Gaps appear more often at staff change than after large hacks.

Staff who know the internal path create better entries early. Cross-reference retrospectives with e-mail sent to the wrong recipient. If the log leads to a report, follow report a data breach to the FDPIC and paste portal data back. After audit questions on awareness, see proof of security awareness training and data protection training for employees.

For data protection training that includes documentation habits, see data protection awareness training.

Keep the note even when you decide not to tell the FDPIC. The log is what you show later if someone asks what you knew and when. Two years is the floor you plan for internally, not a folder to empty once the shock passes.

data breach documentation template fadp switzerland
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.