Cyber incident evidence log: set the scope, evidence, and review date

An incident log is the shared memory of a response. It helps a household, small business, insurer, provider, investigator, or lawyer understand what was known at each time and why an action was taken. It is not a place to paste passwords, recovery codes, full identity numbers, malware, or every raw log file.

Preservation needs judgment. Disconnecting a device may limit harm, while powering it off can destroy volatile evidence. Safety and ongoing loss come first, but consequential systems should be handled with qualified incident or forensic support when available.

OwnerName one responsible person
EvidenceKeep a setting, date, or result
Next reviewSchedule it before closing

Complete each item with evidence, not memory

  1. Create the incident header

    Record a neutral name, opened time and timezone, coordinator, affected people or systems, safety issues, business impact, and verified contact routes.

  2. Log the first observation

    Capture who saw what, exact wording, device or account, URL or sender, screenshot identifier, and what was happening immediately before it appeared.

  3. Record containment chronologically

    For each action, note time, person, reason, command or setting, result, error, and evidence created. Never rewrite an earlier entry; add a correction.

  4. Maintain evidence custody

    Assign an identifier, source, collector, date, protected storage location, access history, and hash where qualified practice calls for one.

  5. Close with decisions and follow-up

    Record impact, restored services, notifications, unresolved questions, monitoring dates, evidence retention owner, and the approved lesson or control change.

Capture the exception and its safer next action

Item or blockerWhat it affectsDecision or evidence
Active financial transferLoss may continue while evidence is collectedContact the payment provider immediately and log the call in parallel with technical preservation
Possible stalkerware or abuseChanging the device may alert a dangerous personUse a safer device and a safety-led specialist plan before routine technical steps
Business server may be compromisedShutdown can remove volatile evidence but continued operation can spread harmUse the incident plan and qualified responder to balance isolation, continuity, and preservation
Original screenshot was editedMetadata and integrity may be questionedKeep the original protected and create a labeled working copy for redaction or annotation

Completed example: log a suspicious mailbox rule without overwriting evidence

In this hypothetical small-business event, the incident lead records observations, actions, and evidence references without placing credentials or sensitive files in the worksheet.

Hypothetical completed example
Time and observationAction and ownerEvidence reference
09:12 HKT: finance user reports that invoice replies are missingIncident lead opens the case and confirms the timezoneEV-01 original report email
09:24 HKT: an unknown forwarding rule is foundAdministrator exports the rule details, disables the rule, and revokes sessionsEV-02 settings export; EV-03 security log
10:05 HKT: bank confirms that no transfer left the accountFinance owner records the case and contacts the supplier through a saved numberEV-04 bank case; EV-05 call note

Why this example is useful: The chronology distinguishes what people observed from what they changed and where each original record is protected. A working copy can be annotated without altering the original evidence.

Use these prompts when the checklist is reopened

Use one clock and record timezone

A timeline becomes unreliable when screenshots, emails, bank calls, and system logs use different zones without labels.

Separate observation from interpretation

Write what appeared, where, and when before writing a theory. Later evidence may change the explanation without changing the original fact.

Track every action and actor

Password changes, shutdowns, exports, account locks, rule removal, bank calls, and vendor commands can change evidence and must be attributable.

Reference evidence, do not duplicate secrets

Give each file or message an identifier, protected location, collector, and integrity note. Keep sensitive originals under appropriate access controls.

Sources for Cyber incident evidence log

Confirm current instructions and limits for this specific task before acting.

Keep a chronology that distinguishes observation from interpretation

Write what was observed, the source, and the time before stating what it may mean. For example, an unfamiliar forwarding rule is an observation; who created it may still be unknown. This separation makes the record more useful to responders, providers, insurers, counsel, or law enforcement and reduces confident but unsupported conclusions.

Reference evidence without turning the log into an unsafe data dump. Use identifiers that point to protected copies of messages, logs, screenshots, transaction records, and provider notices. Avoid placing passwords, live tokens, full payment details, unnecessary identity documents, or harmful files directly in a widely shared worksheet.

Record decisions as well as technical actions. Note who authorized containment, which systems were affected, which notifications were considered, what remains unknown, and when each open item will be reviewed. Preserve the original record, restrict editing, and create a clear handoff when ownership changes.

Questions to settle before marking it complete

Is a spreadsheet enough?+

It can be for a lower-impact event if access, version history, backup, and confidentiality are appropriate. Higher-impact incidents may require a case-management or forensic process.

Should I record theories?+

Yes, but label them as hypotheses and record the evidence for and against them. Do not replace the original observation with a later interpretation.

When should I stop collecting evidence myself?+

Escalate when personal safety, regulated data, significant money, criminal activity, legal privilege, insurance conditions, or complex systems are involved, or when an action could destroy important evidence.

Use these guides to complete the harder items

A checklist is more useful when each item points to the guidance needed to complete it well. Use the Security tools, checklists & protection kits hub for the complete topic pathway, then continue with Small-business incident response plan, Personal data breach response kit, and Account takeover response.

After immediate containment, turn unresolved control gaps into scheduled work with the personal security audit.