すべてのテンプレート
Privacy & Compliance

Security Incident and Data Breach Report Intake

Captures a structured first-hand account of a suspected or confirmed security incident — what happened, what systems or data may be affected, and how contained it is — for IT, security, and compliance teams. An AI follow-up interview reconstructs the actual timeline of discovery and response instead of relying on a rushed written summary.

設問の例

テンプレートの内容をプレビューできます。すべての設問は公開前に自由に編集できます。

全14問・約7分
Q01
メッセージ

Thanks for reporting this. The details you share here go directly to the security and compliance team and help us respond quickly. Your responses are completely confidential and anonymized. This takes about 8 minutes — if the incident is still active, please also contact IT/Security through your emergency channel right away.

Q02
選択式必須

What is your role in relation to this incident?

  • Employee who discovered or experienced it
  • IT / Security staff member
  • Manager of an affected team
  • Third-party vendor or contractor
  • Other
Q03
日付必須

When did you first notice or suspect something was wrong? (Best estimate is fine.)

Q04
選択式必須

Which best describes the type of incident?

  • Phishing or social engineering attempt
  • Unauthorized system or account access
  • Malware or ransomware
  • Lost or stolen device
  • Data sent or exposed to the wrong recipient
  • Physical break-in or unauthorized access to premises
  • Other
Q05
選択式必須

As far as you know, what type of data may have been affected? Select all that apply.

  • Customer personal information
  • Employee personal information
  • Financial or payment data
  • Health records
  • Intellectual property or trade secrets
  • Login credentials or passwords
  • Other
Q06
自由回答(長文)必須

In your own words, what happened? Include what you saw or were told, and any systems, accounts, or locations involved.

Q07
オピニオンスケール必須

How confident are you that the incident is currently contained (i.e., not actively ongoing)?

スケール: 1 – 7
最小:Not confident at all最大:Completely confident
Q08
選択式必須

Has this incident already been reported to your IT or Security team through another channel?

  • Yes, already reported
  • No, this is the first report
  • In progress / not sure
Q09
自由回答(長文)

What actions, if any, have already been taken to contain or address this incident (e.g., password reset, device disconnected, account disabled)?

Q10
AIインタビュー

Reconstruct the actual timeline of this incident: how it was first noticed, exactly what the respondent did in the minutes and hours after, and who else was told or involved. Anchor on the specific incident type and data categories they selected, and probe any gap between discovery and reporting — ask what caused the delay, if any, and whether the respondent believes the incident could still be active. If they seem unsure about scope, ask what evidence would help them confirm it.

Q11
評価スケール

How clear was it to you what steps to take when you noticed this incident?

範囲: 1 – 5
最小:Very unclear最大:Very clear
Q12
数値

Roughly how many individuals or records do you think may be affected? (Enter 0 if unknown or not applicable.)

Q13
選択式

Which department or team are you part of?

  • IT / Security
  • Operations
  • Sales / Customer Success
  • Finance
  • HR
  • Other
  • Prefer not to say
Q14
メッセージ

Thank you for reporting this promptly. Your report has been logged and routed to the security team for immediate review; you may be contacted for follow-up as part of the incident response process.

含まれる機能

  • AIによる深掘り

    自由回答に合わせてAIが追加で質問し、固定のフォームでは拾えない具体的な内容を引き出します。

  • 注意確認設問

    急いだ回答や質の低い回答者を除外する仕組みを標準で備えています。

  • AIが作成する設問文

    文言、設問の順序、条件分岐をAIが調査の目的に合わせて作成します。

  • 自動レポート

    回答が集まると、テーマ、引用、わかりやすい要約が自動で作成されます。

他ツールとの比較

ほかのアンケートツールで最も近いテンプレートを調べました。それぞれの優れている点と、このテンプレートがさらに踏み込んでいる点をまとめています。

このテンプレートを選ぶ理由

  • Includes an AI follow-up interview that reconstructs the actual incident timeline (discovery, response, containment) instead of relying on a single rushed written summary
  • Combines structured fields (role, incident type, data types affected, confidence in containment, estimated records affected, department) with open-ended narrative questions for full context
  • Captures process signals other tools don't, like whether the incident was already reported through another channel and how clear the reporting steps were, which helps compliance teams spot process gaps
  • Closes with automated logging/routing confirmation messages so the reporter knows their report was received and sent to the right team

Jotform

Security Incident Report Form Template

A standard fielding-ready form template for logging security incidents with typical fixed fields. It's built on Jotform's general form builder and widget ecosystem rather than anything specialized for security/compliance workflows. Good for basic intake but not for reconstructing what actually happened during the incident.

優れている点

  • Fielding-ready template usable immediately
  • Backed by Jotform's broad form-building and integration ecosystem
  • Likely customizable with drag-and-drop fields

物足りない点

  • Static question set with no adaptive follow-up to probe inconsistent or vague answers
  • No mechanism to reconstruct an incident timeline beyond what the reporter chooses to write
  • No published methodology on how questions were validated for security/compliance use

SurveyMonkey

Security Breach Report Template

A fielding-ready template aimed at capturing breach details in a standard survey format. It leans on SurveyMonkey's general survey infrastructure (skip logic, reporting) rather than anything purpose-built for reconstructing incident timelines. Useful as a quick intake form but limited for deeper investigative follow-up.

優れている点

  • Fielding-ready and quick to deploy
  • Supports basic skip logic for branching questions
  • Benefits from SurveyMonkey's established reporting/dashboard tools

物足りない点

  • No adaptive AI interview to dig deeper into vague or incomplete incident descriptions
  • Relies on the reporter's own written summary rather than a reconstructed timeline
  • No transparent, published prompt methodology for how follow-up questions (if any) are generated

Typeform

Security Incident Report Form

A conversational-style, fielding-ready form template for reporting security incidents, benefiting from Typeform's polished one-question-at-a-time UX. It's a static question flow, however, with no capability to adaptively probe for missing details like exact timing of discovery or containment steps. Good for a friendly intake experience but not for deep incident reconstruction.

優れている点

  • Polished, conversational one-question-at-a-time UX
  • Fielding-ready template with Typeform's known design quality
  • Likely supports basic logic jumps between questions

物足りない点

  • No adaptive AI follow-up interview to reconstruct the actual incident timeline
  • No automated per-response quality scoring to flag vague or incomplete reports
  • No published prompt-level transparency into how any branching questions are determined

よくあるご質問

「Security Incident and Data Breach Report Intake」テンプレートにはどのような設問が含まれていますか?

すぐに使える設問が14問含まれており、最初の設問は次のとおりです:「Thanks for reporting this. The details you share here go directly to the security and compliance team and help us respon…」・「What is your role in relation to this incident?」・「When did you first notice or suspect something was wrong? (Best estimate is fine.)」。すべての設問は上でプレビューでき、自由に編集できます。

このアンケートの回答にはどのくらい時間がかかりますか?

回答者は通常、14問を約7分で回答し終えます。

テンプレートは編集できますか?

はい。公開前であれば、すべての設問、選択肢、順序を編集できます。設問の追加や削除のほか、調査の目的に合わせた作り直しをAIエディターに依頼することもできます。

このテンプレートは無料で使えますか?

はい。エディターで開けば、すぐに編集を始められます。お試しにアカウントは不要で、無料プランでアンケートを公開できます。

公開の準備はできましたか?

このテンプレートをエディターで開いてみてください。最初の回答者が目にする前に、すべてを自由に変更できます。

関連テンプレート

似たテーマのほかの調査もご覧ください。

すべて見る