A system, comprising: a sensor (111, 203, 309, 511, 611) configured to: passively read data in packets as the packets are in motion on a network; and a processor (205, 607) cooperatively operable with the sensor (111, 203, 309, 511, 611), and configured to: receive (617, 703) the read data from the sensor (111, 203, 309, 511, 611); originate (619, 707) real-time map profiles of files and file data, both from the read data from the sensor (111, 203, 309, 511, 611), as the passively read packets are in motion on the network, wherein the map profile is a topographical map of the locations of the files on the network, wherein the map profile further designates hosts which contain the files, destinations to where the files were transferred, and file directories of the files on the hosts and destinations; extract metadata from the read data in the passively read packets to generate passively discovered metadata, as the packets are in motion on the network, the read data including: the main hash of the entire file, the block hash of individual blocks within the file, the directory listing of files with file names, dates, time stamps, size, and file owners; the hash being a cryptographic hash unique to the file; store the passively discovered metadata, attributes of the files, and the file data, in a relational database; and store the passively discovered metadata in a data map of passively discovered metadata; wherein the sensor (111, 203, 309, 511, 611) is further configured to embed a honeytoken into voids inside the file contained in the passively read packets when the file has a file format predetermined to have dead data that can be overwritten, wherein the honeytoken is used to aid tracking of the file's movement around and outside the network. a sensor (111, 203, 309, 511, 611) configured to: passively read data in packets as the packets are in motion on a network; and a processor (205, 607) cooperatively operable with the sensor (111, 203, 309, 511, 611), and configured to: receive (617, 703) the read data from the sensor (111, 203, 309, 511, 611); originate (619, 707) real-time map profiles of files and file data, both from the read data from the sensor (111, 203, 309, 511, 611), as the passively read packets are in motion on the network, wherein the map profile is a topographical map of the locations of the files on the network, wherein the map profile further designates hosts which contain the files, destinations to where the files were transferred, and file directories of the files on the hosts and destinations; extract metadata from the read data in the passively read packets to generate passively discovered metadata, as the packets are in motion on the network, the read data including: the main hash of the entire file, the block hash of individual blocks within the file, the directory listing of files with file names, dates, time stamps, size, and file owners; the hash being a cryptographic hash unique to the file; store the passively discovered metadata, attributes of the files, and the file data, in a relational database; and store the passively discovered metadata in a data map of passively discovered metadata; receive (617, 703) the read data from the sensor (111, 203, 309, 511, 611); originate (619, 707) real-time map profiles of files and file data, both from the read data from the sensor (111, 203, 309, 511, 611), as the passively read packets are in motion on the network, wherein the map profile is a topographical map of the locations of the files on the network, wherein the map profile further designates hosts which contain the files, destinations to where the files were transferred, and file directories of the files on the hosts and destinations; extract metadata from the read data in the passively read packets to generate passively discovered metadata, as the packets are in motion on the network, the read data including: the main hash of the entire file, the block hash of individual blocks within the file, the directory listing of files with file names, dates, time stamps, size, and file owners; the hash being a cryptographic hash unique to the file; store the passively discovered metadata, attributes of the files, and the file data, in a relational database; and store the passively discovered metadata in a data map of passively discovered metadata; wherein the sensor (111, 203, 309, 511, 611) is further configured to embed a honeytoken into voids inside the file contained in the passively read packets when the file has a file format predetermined to have dead data that can be overwritten, wherein the honeytoken is used to aid tracking of the file's movement around and outside the network.