The Logs Say It Was You: Audit Trails, Shared PINs and a Short Story About a Feed Store Register
Every developer who has worked on a point-of-sale system, an admin panel or an internal tool has heard some version of this sentence: "The logs say it was you." I recently read a short story that turns that sentence into
Every developer who has worked on a point-of-sale system, an admin panel or an internal tool has heard some version of this sentence: "The logs say it was you." I recently read a short story that turns that sentence into a family drama, and it is one of the better illustrations I have seen of why shared credentials quietly destroy the value of an audit trail.
No code in this post. Just a story, and the engineering lessons hiding inside it.
The setup: eleven refunds under one code
The story takes place at a family-owned feed store in rural Texas. The narrator has run the cash drawer for twenty-one years. One evening her husband sits down at the kitchen table with a stapled report from the store's register system: eleven cash refunds since July, all under her employee code. August deposits came in about sixteen hundred dollars under the previous August. The report does not accuse anyone. It does not have to. It lists her code down the left-hand column and a dollar figure beside every line.
Her code is 0827. Their wedding anniversary.
"Half of Lometa Springs could guess it," she says.
That one line is a whole security postmortem.
Lesson 1: An audit log is only as good as its authentication
The register does exactly what it was designed to do. It records which code was entered for each transaction. What it cannot record is who typed the code. When the identifier is a four-digit number based on a public date, the log is not answering the question "who did this?" It is answering "which secret was used?" Those are very different questions, and the story is a neat demonstration of what happens when people treat them as the same.
If you build systems like this, it is worth asking:
- Is the credential tied to a person, or merely to a role or a shared terminal?
- Can it be guessed from public information (birthdays, anniversaries, employee numbers)?
- Do reports present the credential as if it were proof of identity?
Lesson 2: Reports carry authority they have not earned
What makes the scene at the kitchen table painful is how official the paper looks. A printed, stapled monthly summary feels objective. The husband says "I hear you" in a way that means he has not decided, and the narrator notes that this is worse than shouting. The data has shifted the burden of proof onto her.
Anyone who has shipped a dashboard should recognize this. Numbers on a report acquire credibility simply by being formatted neatly. If a report attributes actions to people, the tool owes users a clear note about what the attribution actually means and how confident it is.
Lesson 3: Look for corroborating signals
Without spoiling the plot, the narrator does what a good incident responder does. She stops arguing with the summary and starts looking for other evidence: timing, physical access, who was actually standing at the counter, and what else changed around the same time. There is also a second thread involving a buyer's offer on the store that someone has been hiding in a truck for weeks, which raises the question of motive.
In engineering terms, a single log source is a weak signal. Correlating it with door access, shift schedules, camera footage or a second system is what turns suspicion into an answer.
Lesson 4: Small systems need security design too
It is tempting to think a small family business does not need real access control. Everyone knows everyone. But that familiarity is exactly why weak codes are dangerous: the people most able to guess your PIN are the people closest to you. The story makes that point far more memorably than any compliance checklist.
Practical takeaways for small deployments:
- Unique, non-guessable credentials per person, rotated when staff change.
- Manager approval (a second credential) for cash refunds above a threshold.
- Reports that show the terminal, time and approver, not just a code.
- A simple process for an employee to dispute an attribution.
Why read fiction for this?
Postmortems describe what happened. Stories make you feel the cost of it. Watching a twenty-one-year employee defend herself against a report built on a guessable PIN is a better argument for proper authentication than most slide decks I have sat through.
The story is free to read on TaleHour, a site of English short fiction that keeps surprising me with how often its everyday mysteries map onto real systems problems. Give it twenty minutes, then go check what your own admin panel is really logging.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.