BasicSec.org

IntroductionContentsReviewsToolsUpdatesPurchaseContact
Home / Practical guides

An incident timeline a second volunteer can check

· · Worked example and worksheet

At 10:16 the rota coordinator hears that a private shift note was visible in the shared calendar at about ten. Writing “calendar exposed at 10:16” would quietly change the evidence. That was the time the coordinator heard the report. The start time is still unknown. A shared incident log can preserve that distinction without reproducing the note.

1. Keep two times

In this fictional exercise, all times are local on the same date, with a UTC offset of −05:00. Give each entry both an event time and a time entered. At 10:16 the coordinator can write “Volunteer reported seeing a private shift note at approximately 10:00.” Mark the event time as an estimate. Leave the start of exposure open. If several teams use different time zones, keep the original offset alongside each time.

2. Record where the evidence lives

Use a reference that the person responsible for the original can resolve, such as “restricted report R-07, entry 1.” In the shared log record the role, observation, action and outstanding question. A name, the shift-note text and a screenshot add nothing to this example. Keep the underlying record with its authorized custodian under the organization’s retention rules. Check that people with access to the shared log cannot open the restricted record solely because they know its reference.

Google’s incident-management chapter describes a shared working record and a handoff. The OWASP logging guide distinguishes event time from logging time and discusses excluding secrets and sensitive personal data. The two-column example here adapts those ideas for a volunteer coordinator.

3. Add a correction someone can trace

At 10:24 the calendar owner checks the sharing view and sees the note. At 10:29 they remove it from that view. At 10:35 a second volunteer checks the same view and reports the note is absent. These observations bracket the change in that view. They cannot establish who else saw the note or whether another copy exists.

At 11:05 the first volunteer clarifies that they looked at 10:08 on their watch. Add a row referring back to R-07 and describing the correction. Keep the first estimate in its original entry. A reader can now see what the coordinator knew at 10:16 and what changed later.

4. Give the next shift one open question

Hand over “Could the note be seen through another shared view?” with an owner and a next check. A fresh reader should be able to identify the earliest confirmed observation, the later independent check and the remaining uncertainty from the filled timeline and blank row. If the question concerns an unexpected reset, use the shared-mailbox reset exercise. For a public list of group contacts, check the directory export before sharing it.

IntroductionContentsReviewsToolsUpdatesPurchaseContact
Analytics privacy
Microsoft Clarity / Privacy