One line hid what no one expected: a full name, an email, and a set of digits no log should ever hold. That’s how PII slips through—silent, invisible until it’s not. And once it’s there, it’s there for good.
Lnav makes searching logs painless. But searching for PII in real time? That’s a higher bar. PII detection in lnav goes from theory to urgent reality when you realize a rogue debug line can expose addresses, phone numbers, credit cards, or IDs. Every system writes logs. Not every system keeps them safe.
Lnav PII detection is about two things: finding sensitive data fast and stopping it before it spreads. The core idea is simple—use patterns, use rules, parse streams, detect everything from an email regex to a custom token. The execution has to be fast, local, and precise. Because logs are high-volume. Because every false negative costs more than a false positive.
With proper configuration, lnav can highlight PII inline as you scroll. It can tag matched sequences so you can export and clean them. It can search across rotated files without breaking the flow. Combine that with smart pattern collections—emails, SSNs, driver’s licenses, IPs—and you get a detection engine riding inside your favorite log viewer.