Menu

Every Process Has a Parent: Logster and the Context That Started Before You Looked
📰

Every Process Has a Parent: Logster and the Context That Started Before You Looked

DEV Community: cybersecurity·Chad Ray·about 2 hours ago
#xSARjTzH
#devtocybersecurity#devto#dev#parent#process
Reading 0:00
15s threshold

Every detection starts in the middle of a story. A detector reviews a stretch of recent activity, decides what it means, and moves on. Processes don't care where that stretch begins. A shell opened at nine in the morning is still running at noon, and when it finally does something interesting, the moment it was born may be hours outside anything the detector is looking at.

That gap is easy to miss, because it doesn't look like a gap. It looks like a command that came from nowhere.

Key Takeaways

"What launched this?" is usually the first question in an investigation, and the answer often lies outside the period a detector is reviewing.

Long-lived parents (open shells, remote sessions, services started at boot) outlast any review, so activity launched from them, which is where hands-on-keyboard work lives, is the most likely to arrive without a parent.

The fix is a reliable process identity plus a memory of earlier activity, and an honest "not observed" when the parent can't be found.

The first…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.