Skip to content
Off-topic for aiqbench

Off-topic for aiqbench

This story was gathered from a source we follow but falls outside AI and quantum coverage, so there is no aiqbench take for it.

How Data Lineage Catches a File That’s Trying Not to Be Found

Netskope5 min read

A technical look at how Netskope One Data Lineage reconstructs a file’s journey and closes visibility gaps with endpoint events. It almost feels like a Shrödinger riddle: When a user downloads a financial report, renames it (e.g. holiday_photo.jpg), edits it, and uploads it to personal cloud storage, is it still the same file? Arguably not, […]

A technical look at how Netskope One Data Lineage reconstructs a file’s journey and closes visibility gaps with endpoint events. It almost feels like a Shrödinger riddle: When a user downloads a financial report, renames it (e.g. holiday_photo.jpg), edits it, and uploads it to personal cloud storage, is it still the same file? Arguably not, but the data still requires consistent governance. The challenge of course is consistent visibility. Network-based controls would see both ends of the sequence (the download and the upload), but they couldn’t tell if the two events involved the same…

Excerpt shown under the publisher's RSS terms · 94 words · full text and figures are on the publisher's site

Related coverage