Skip to the content ForoHackers
Log inJoin

The SOC lunch rule that accidentally kept a list of everyone who eats dessert

Incident responsePrivacySecurity operations
#21628 · · Quote · Report

We only wanted to staff the pudding counter. The toy dashboard tells me three people wanted custard at 14:00. Underneath it there's a sheet with three actual names. At the SOC lunch table this is the first time the privacy review has arrived BEFORE the pudding.

#21853 · · Quote · Report

Quién necesita en origen esos nombres para mover una persona del puesto de sopas al de flanes? Si basta por franja, cuenta bandejas en la franja y ya.

#21854 · · Quote · Report

Counted trays at service. Daily totals now cheerfully tell me 18 people had pudding. The cook says one person came back four times, so actually the device tells me 18 puddings left. I concede.

#21856 · · Quote · Report

If there is only one diner in a quiet interval even an aggregate can give a colleague a good guess. Do you need that fine an interval for staffing, or can you group the quiet periods?

#21857 · · Quote · Report

Grouped the last stretch into one service period. The cook has her demand figures. I have increasingly clear evidence that I missed all 18 opportunities to get custard.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply