docs(prd): add PRD 0009 — Read the logs for evidence, including the logs that stopped - #58
Merged
Merged
Conversation
…ogs that stopped Logs hold the evidence of an intrusion, but a busy server writes millions of lines a day and a tool that surfaces every 404 on /wp-admin is the output nobody reads. Status code is the discriminator most log tooling underuses: a traversal attempt returning 404 is noise, the same request returning 200 is an incident. Equally important and usually missed — A MISSING LOG IS EVIDENCE. A log that stops mid-day, shrinks, or loses its inode while the service still runs is a strong tampering signal, and it is invisible to anything that only pattern-matches log contents. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specification for the
log-watchercore module, listed inPRD.mdand not yet specified.Logs hold the evidence of an intrusion, but a busy server writes millions of lines a day and a tool that surfaces every 404 on /wp-admin is the output nobody reads.
Status code is the discriminator most log tooling underuses: a traversal attempt returning 404 is noise, the same request returning 200 is an incident. Equally important and usually missed — A MISSING LOG IS EVIDENCE. A log that stops mid-day, shrinks, or loses its inode while the service still runs is a strong tampering signal, and it is invisible to anything that only pattern-matches log contents.
Spec only — no implementation in this PR.