NoBackups

It worked in staging…

[ 0.000003] // 0x004: ENODATA

Suppose The Company asks you who logged in during the incident. A small question. You make the mistake of sitting down as though it will have a small answer.

The hosted analytics service has restored its activity history. I download the affected period and count the records. Several logins appear twice. Same event ID. Same timestamp. Apparently we have recovered enough history to have some left over.

I deduplicate by event ID. The count falls. My confidence does not improve.

The restoration notes explain that the recovered files overlap with surviving originals. They also explain that some event types are incomplete. The spare copies are not necessarily copies of the events we are missing. You cannot pour them into the gaps.

Naturally I try another query. Narrower time window. Authentication events only. Then I check the other login-related records, because incomplete is not the same as useless, however much I would enjoy putting the laptop in a drawer.

In this little exercise, nothing independently confirms the login I was asked about. An empty result cannot tell me whether it never happened or whether its record is among the missing ones.

Fuck. I have spent the morning removing evidence that something happened twice so I can explain why I cannot establish whether something else happened once.

I begin drafting a process to reconstruct the absent events from the surrounding activity. There would be confidence scores. A neat column. Something sortable.

I delete the column heading before giving it a data type.

The separate export bucket would have helped if we had retained our own copy there. It was not deleted. In this imagined version of my life, we never configured it. We had historical retrieval instead.

I attach the surviving records and write down the limits. No invented login. No reassuring zero.

The incident form requires a name.

I enter mine. There is now a complete record of who failed to find out.