What's shipping today

Lineage View is the feature most of our customers have been asking for. It traces sensitive data movement across the systems Argus monitors — databases, object stores, SaaS apps, data warehouses — so you can see where personal data flows after it enters your environment.

What it does

The interface is a graph of your sensitive data movement. A column containing email addresses in your production database connects to the analytics warehouse it's replicated to, the BI tool that queries it, the marketing platform that exports it, and the partner integration that receives a derived version. Each edge shows the system, the timing, and the access pattern that produced the link.

You can filter by classification, by system, or by specific record types. The common workflow is to start with a sensitive data category — say, payment information — and walk forward to see everywhere it ends up.

Why it was hard

The hard part wasn't the visualization. It was making the lineage accurate without requiring teams to manually map their pipelines, because nobody actually does that, and the maps are stale within weeks when they do.

Argus infers most flows from a combination of access patterns, schema relationships, and metadata fingerprints. We surface the parts that need human confirmation rather than guessing silently and presenting fabricated edges as fact. The result is a graph that reflects reality, with explicit gaps where reality is uncertain.

Getting started

Lineage View is available now in the main interface. No additional setup is required if you're already running scans — the data has been there, we just hadn't shipped the view. The full launch post on our engineering blog covers the inference approach in more detail for the teams that want to understand what's happening under the hood.