Incident response questions: what buyers ask and how to answer
Short answer: Incident response questions check that you have a written plan, that someone owns it, that it has been tested, and how quickly you'll tell the customer if their data is affected. Answer with the plan's name and review date, the roles involved, the date of the last exercise, and a notification commitment that matches your contracts word for word. If your documents don't state a timeline, don't invent one in the questionnaire.
In Iris: when your incident response plan doesn't state a notification timeline, Iris says there isn't enough information instead of filling in a number.
Who this is for: security leads, GRC teams and sales engineers answering vendor assessments and DPAs.
On this page
- How is the question usually phrased?
- What is the reviewer really checking?
- Notification: what law requires vs what you promise
- Sample answers (fictional company)
- What evidence should you attach?
- How Iris drafts incident response answers
- FAQ
How is the question usually phrased?
| Common phrasing (paraphrased) | What it's really asking |
|---|---|
| "Do you maintain a documented incident response plan?" | A written plan exists, with an owner and a review date |
| "How often is the plan reviewed and tested?" | Annual review and a tabletop or live exercise, with a date |
| "Describe your incident classification and escalation process." | Severity levels and who gets paged at each |
| "How and when will you notify us of a security incident affecting our data?" | A specific commitment and the channel used |
| "Do you have a dedicated incident response team or retainer?" | Named roles; any external forensic support |
| "Have you had a reportable security incident in the past X years?" | Disclosure history (answer carefully, with legal) |
| "Do you perform root-cause analysis after incidents?" | Post-incident review and corrective actions |
| "How do you preserve evidence during an incident?" | Logging retention and forensic readiness |
What is the reviewer really checking?
- That the plan is real. A named document with a version and a review date is the baseline.
- That it has been exercised. "Tested annually" plus the month of the last tabletop beats "tested regularly."
- That your notification promise matches your contracts. Security reviewers often read your DPA alongside the questionnaire. A shorter timeline in the questionnaire than in the DPA becomes a contract question.
- That you'll tell them what they need. What you'll share (nature of the incident, data affected, steps taken), not just when.
Notification: what law requires vs what you promise
| Source of the obligation | What it says | What to write in a questionnaire |
|---|---|---|
| GDPR Art. 33(1), controller to authority | Notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware | Relevant if you are the controller. As a vendor you're usually the processor. |
| GDPR Art. 33(2), processor to controller | Notify the controller without undue delay after becoming aware | Quote your DPA's commitment, which may be more specific |
| Your DPA or MSA | Whatever timeline you agreed | Copy the contractual wording exactly; don't paraphrase it shorter |
| Other laws and sector rules | Vary by jurisdiction and sector | Have legal confirm before naming any |
Rule of thumb: the questionnaire answer should point to the contract, not create a new promise.
Sample answers (fictional company)
Written for Fernhill Software, a fictional SaaS vendor. Labelled examples.
Strong answer: documented plan
Answer: Yes.
Comment: Fernhill maintains a documented Incident Response Plan owned by the Head of Security, reviewed annually (last review: [month year]). The plan defines four severity levels, on-call escalation, and roles for security, engineering, legal and customer communications. We run a tabletop exercise at least annually; the last one was in [month year]. Summary available on request.
Strong answer: customer notification
Answer: Fernhill will notify affected customers of a confirmed security incident involving their data without undue delay, within the timeframe set out in our Data Processing Addendum §[x]. Notices go to the security contact on file and include the nature of the incident, data categories affected, and the steps we're taking.
Why it works: it ties the promise to the contract instead of inventing a separate number.
Weak answer, rewritten
Weak: "We have a world-class incident response capability and respond to all incidents immediately."
No document, no roles, no test, and "immediately" is a promise no one can keep.
Rewritten: Yes. Our Incident Response Plan (v3, reviewed [month year]) defines detection, triage, containment, eradication, recovery and post-incident review. Security on-call is reachable around the clock through our paging tool. [Only include round-the-clock coverage if your rota proves it.]
Abstention: when the timeline isn't documented
Draft: There is not enough information to answer the question.
Reviewer action: assigned to Legal to confirm the DPA notification wording before anything is submitted.
That's the right outcome. A guessed "24 hours" in a questionnaire can become a contractual expectation.
What evidence should you attach?
| Question | Evidence |
|---|---|
| Plan exists, reviewed | Incident response plan (summary or table of contents) with version and review date |
| Tested | Tabletop exercise summary with date |
| Notification | DPA clause reference |
| Post-incident review | Root-cause analysis template or procedure |
| Overall | SOC 2 Type II report (incident management section), if available |
How Iris drafts incident response answers
- Drafts only from your content: your incident response plan, DPA, SOC 2 report and past approved answers.
- Abstains when the documents don't say: "There is not enough information to answer the question." Those rows can't be approved as-is and are left blank in the export, so a guessed timeline can't slip through.
- Flags conflicts: if the plan and an older approved answer state different timelines, the draft is labelled Contradictory.
- Routes to the right owner: assign notification questions to Legal and plan questions to Security from the same project; @-mention a teammate in a comment to get a fast answer.
- Tracks what you promised: commitments written into answers are extracted when a project is finalized, so you can see every timeline you've committed to in writing.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered, or a security questionnaire you've already completed.
FAQ
Do we have to give a notification timeline in hours?
Only if your contract does. Point to the DPA clause; that keeps one source of truth.
What if we've never had an incident?
Say so plainly if it's true and legal agrees, and still describe the plan and the last exercise.
What's a tabletop exercise?
A walkthrough of a simulated incident with the people who'd respond. It shows the plan works on paper and that people know their roles.
Should we share the full incident response plan?
Usually a summary or table of contents is enough; share the full plan under NDA if a buyer insists.
Which framework covers incident response?
NIST SP 800-61 Rev. 3 is a common public reference. In CAIQ the theme is the Security Incident Management, E-Discovery & Forensics domain; see our CAIQ guide.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
