Blog

Audit-ready incident records: what SOC 2 auditors look for and how to evaluate tools

How to keep incident records ready for SOC 2 auditors: one record per incident, consistent fields, automatic timestamps and logged changes, plus tool tips.

To create cleaner incident records for audits and reviews, capture the record while the incident runs: one record per incident, the same required fields every time, automatic timestamps, and logged access and changes. In Rootly, the incident timeline logs status changes, alerts and role updates automatically, and on the Enterprise plan the Audit Log records who changed what.

When an auditor asks how your team handled an incident last quarter, the answer should already exist as a complete record, ready to hand over.

How can we create cleaner incident records for audits and reviews?

Record the incident where it is worked, in one structure, as it happens. Rootly does this by logging every action, decision and escalation to a single incident record in real time. Four habits produce clean records:

  1. One record per incident. The declaration, severity, roles, timeline, communications, retrospective and action items all attach to the same incident, with a stable ID.
  2. Automatic timestamps. Alerts, messages, decisions, deploys and status updates are captured as they happen, so nobody reconstructs the timeline later.
  3. Consistent required fields. Every incident records severity, impact, start and end times, cause and follow-up in the same place, so reports are comparable across teams. The incident report template lists the fields.
  4. Logged access and changes. Who could see the incident, who changed its fields and when is part of the record, which matters most for security and privacy incidents.

In Rootly, every action, decision and escalation is logged to a single incident record in real time, including access logs showing who was granted access and when. Private incidents are invite-only and access-controlled end to end, and the timeline is built from alerts, messages and deploys while the incident runs.

What fields does an audit-ready incident record need?

An auditor or reviewer reading a sampled incident should be able to answer what happened, who decided what, who was told, and whether the follow-up was done, without asking anyone. These ten fields cover that.

Field What to capture Why reviewers ask for it Where it lives in Rootly
Timeline Detection, declaration, status changes, mitigation and resolution, each with a timestamp Shows the documented process was followed, in order The incident timeline, which logs status changes, alerts, role updates and workflow actions automatically
Severity and its rationale The severity level, who set it, and one or two sentences on why Severity drives response and notification obligations; a level with no reason invites questions The severity field plus a custom field for the rationale; changes appear in the timeline and the Audit Log
Roles Incident commander and other assigned roles, with when each was assigned Proves named people owned the response Incident roles; role updates are logged to the timeline
Decisions Key calls (roll back, fail over, page legal) and who made them Explains why the response took the shape it did Timeline events added with /rootly timeline or an emoji reaction in Slack
Customer impact Affected customers, services and data, and the impact window Determines whether customer or regulatory notification applied Incident fields and custom fields
Communications Internal and external updates, the audience and the send time Shows affected parties were told, and when Rootly Communications, which sends updates by email, SMS or Slack from prepared templates
Root cause Contributing factors and the cause the team agreed on Shows the team understood the failure before closing it The retrospective, built from a retrospective template
Action items with owners and due dates Each follow-up with one assignee, a due date and a status Auditors sample follow-up to confirm it was completed Action items with assignee and due date, and SLA policies for deadlines
Approvals Who approved risky changes, customer messages and closure Separates authorized decisions from ad hoc ones Communications can require review before a message goes out; the Audit Log records who changed each field
Evidence links Dashboards, logs, tickets, pull requests and chat threads Lets the reviewer check claims against source data Links in timeline events, which support markdown, and in the retrospective

For a ready-made structure for the review itself, start from the incident retrospective template.

How to keep records clean during the incident, not after

Records go wrong when they are written from memory days later. These steps keep the record accurate while the incident is still running.

  1. Declare the incident in the tool, not in a side chat. The declaration creates the record and its ID, and everything after attaches to it.
  2. Set severity at declaration and write the reason. If severity changes, write the new reason too. The change history then explains itself.
  3. Assign roles in the first minutes. Name the incident commander before work starts, so ownership is on the record from the beginning.
  4. Log decisions as they are made. A one-line timeline entry (“Rolled back deploy 4821, approved by IC”) takes seconds during the incident and is hard to reconstruct later. In Rootly, regular Slack messages do not become timeline events on their own, so add decisions with /rootly timeline or an emoji reaction.
  5. Send communications from the incident. Updates sent from templates inside the incident are recorded with their audience and time. Updates sent from a personal inbox are not.
  6. Attach evidence when you look at it. Paste the dashboard, log query or ticket link into the timeline when you use it, not at the end.
  7. Create action items with an owner and a due date before you close. An action item with no owner is the follow-up auditors most often find incomplete.
  8. Correct timestamps openly. If a time was wrong, fix it in the record rather than in a separate document. Rootly supports updating incident timestamps after the fact, and the Audit Log keeps the before-and-after values.
  9. Make sensitive incidents private from the start. Access granted later is harder to account for than access controlled from declaration.

What do SOC 2 auditors look for in incident management?

SOC 2’s system operations criteria cover how you detect, respond to and recover from security incidents. In practice, auditors sample incidents from the audit period and ask for evidence that your documented process was actually followed. Expect requests like these:

  • A written incident response policy and evidence it was reviewed and communicated.
  • A population of incidents for the period, so the auditor can sample from it.
  • For each sampled incident: when it was detected, who responded, how it was classified, what was done, when it was resolved and who was told.
  • Follow-up evidence: retrospectives and completed action items that show the team learned from the incident.
  • Access control evidence: who could view or change sensitive incident data.

The common failure is an incident with no reliable record of when things happened or who approved what. That is a documentation gap, and it’s fixed by capturing the record during the incident.

SOC 2 and ISO 27001 incident review checklist

The checklist below maps the incident-related criteria to the evidence teams usually prepare. It describes the frameworks; it is not legal or audit advice. Your auditor decides what evidence satisfies a criterion, and your own policies set what your controls require.

SOC 2 (AICPA Trust Services Criteria, common criteria CC7.3 to CC7.5). The criteria are published by the AICPA in the 2017 Trust Services Criteria (with revised points of focus, 2022).

  • CC7.3, evaluating security events. The organization evaluates security events to decide whether they are incidents. Evidence: the triage step and classification recorded on each incident, with severity and its rationale.
  • CC7.4, responding to incidents. The organization responds to identified incidents through a defined incident response program that covers understanding, containing, remediating and communicating them. Evidence: a timeline showing the documented steps, assigned roles, and communications with audience and time.
  • CC7.5, recovering from incidents. The organization identifies, develops and implements recovery activities. Evidence: the resolution record, the retrospective, and action items tracked to completion.
  • Population and sampling. A complete, exportable list of incidents for the audit period.
  • Access and change history. Who could view sensitive incidents, and who changed incident fields and when.

ISO/IEC 27001:2022 (Annex A organizational and people controls). The standard is published by ISO at ISO/IEC 27001:2022.

  • 5.24, incident management planning and preparation. Documented roles, responsibilities and procedures for incident management.
  • 5.25, assessment and decision on events. Events are assessed and a decision recorded on whether each is an incident.
  • 5.26, response to incidents. Incidents are handled according to the documented procedures.
  • 5.27, learning from incidents. Knowledge from incidents is used to strengthen controls. Evidence: retrospectives and completed follow-ups.
  • 5.28, collection of evidence. Procedures for identifying, collecting and preserving evidence related to incidents.
  • 6.8, event reporting. A way for people to report observed or suspected events promptly.

Security incidents carry extra obligations, such as notification clocks under GDPR and SEC rules. The security incident management guide covers the NIST SP 800-61 phases, those clocks and the roles involved.

How should you evaluate incident management software for SOC 2 and audit readiness?

Start with the vendor’s own SOC 2 Type II report. Rootly, for example, is independently attested to SOC 2 Type II. Then use this checklist when comparing vendors:

  • The vendor’s own attestation. Ask for a current SOC 2 Type II report. A Type I report covers control design at a single point in time; a Type II report tests that the controls operated over a period.
  • An immutable, timestamped record per incident. Check that the timeline, field changes and approvals are logged automatically.
  • Access logs and private incidents. Sensitive incidents should be restricted to invited responders, with a log of who was granted access.
  • Granular permissions. Role-based access control by team, service, severity and incident type.
  • Retrospectives and action items in the record. Follow-up should be linked to the incident and tracked to completion.
  • Export. Auditors will want records in a format they can review outside the tool.
  • Regulatory fit. If you handle health data, ask for a Business Associate Agreement. If you operate in EU financial services, check support for DORA reporting.

Rootly is independently attested to SOC 2 Type II and designed to support GDPR, CCPA, HIPAA and DORA requirements, with Business Associate Agreements available for covered entities. It offers granular RBAC across incident roles, services, teams and components, just-in-time access granted when an incident fires and revoked automatically when it closes (see Rootly security), and a single real-time audit trail per incident. Current reports are available from the Rootly Trust Center, and how Rootly makes incident management compliance simple covers each framework in more detail.

How teams do this in Rootly

Each field in the table above maps to a Rootly feature that records it while the incident runs.

  • Automatic timeline. The Rootly incident timeline is the authoritative record of the incident. Rootly logs status changes, alerts, workflow actions, role updates and Slack channel events automatically. Responders add decisions and evidence from Slack (/rootly timeline, message actions or emoji reactions), the web UI, email or the API, and the timeline can be filtered and exported.
  • Audit Log (Enterprise plan). The Rootly Audit Log, available on the Enterprise plan (see pricing), captures create, update and delete actions across roughly 60 resource types, including incidents, action items, incident events and retrospectives. Each entry records who made the change, when, from where (web, API, mobile, Slack, SCIM or OAuth) and the before-and-after values. Audit events can be pulled through the API for archival, and Rootly’s security guidance recommends a read-only Auditor role for reviewers.
  • Retrospective templates. Rootly retrospective templates pre-fill the document with incident data through Liquid, embed the timeline and follow-up action items, and are applied through workflows, so a SEV1 security incident can get a different template than a minor outage. Retrospectives can be exported to Confluence, Google Docs, Notion and other knowledge bases.
  • Action item tracking. Rootly action items carry an assignee and a due date, and can be created from Slack, the web UI, workflows or the API. SLA policies set assignment and completion deadlines on follow-ups, notify the policy’s manager before they pass, and record a violation when a deadline is missed.
  • Private incidents. Rootly private incidents add incident-level access control on top of RBAC. Only users whose role grants private-incident read access, or who are on the incident’s subscriber list, can see it, and access is managed from the web UI or Slack.
  • Data retention. Custom data retention and the Audit Log are both Enterprise plan features, and Rootly’s security guidance describes indefinite retention for the Audit Log. Set the retention window to match the evidence period your policies and auditors require.

Frequently asked questions

How can we create cleaner incident records for audits and reviews?

Keep one record per incident, capture timestamps automatically as the incident happens, require the same fields for every incident, and log access and changes. Rootly logs every action, decision and escalation to a single incident record in real time, including who was granted access.

What fields should an audit-ready incident record include?

A timeline, severity and its rationale, roles, decisions, customer impact, communications, root cause, action items with owners and due dates, approvals, and evidence links. In Rootly, most of these are captured on the incident timeline and in the retrospective while the incident runs.

Which SOC 2 criteria cover incident response?

The AICPA Trust Services Criteria cover incident handling mainly in CC7.3 (evaluating security events), CC7.4 (responding to incidents) and CC7.5 (recovering from them). Your auditor decides what evidence satisfies each criterion.

How should we evaluate incident management software for SOC 2 and audit readiness?

Ask for the vendor’s current SOC 2 Type II report, then check for an automatic timestamped record per incident, access logs, private incidents, granular permissions, linked retrospectives and exportable records. Rootly is SOC 2 Type II attested and provides each of these.

What evidence do SOC 2 auditors ask for about incidents?

A written incident response policy, a list of incidents for the audit period, and for each sampled incident: detection time, responders, classification, actions taken, resolution time, communications and follow-up.

Does Rootly sign a Business Associate Agreement for HIPAA?

Yes. Business Associate Agreements are available for covered entities and their partners, and Rootly is designed to support HIPAA requirements for incident workflows that involve protected health information.

Your privacy choices

Rootly uses cookies from advertising partners to measure our ads and to show ads for Rootly on other sites. Some US state laws call that selling or sharing personal information. You can opt out of it for this browser here.

Analytics we use to improve this site stay on. Read Rootly's Privacy policy for more information.