How can you protect your quarterly reports, annual reports, and analytics from leaks?

Often, confidential information is leaked after you have given someone legal access to the document containing it. For example, say you work for a trading company and prepare an annual report presentation. You send it to trusted people, but in the end, one of them leaks the document. Who was it? It could be one person in a hundred or even a thousand.

Or, say you are preparing a quarterly analytics report that can be downloaded only by a limited number of people from your website. Someone downloads it and then uploads it to the network. How do you determine who exactly it was? Again, there are many suspects.

Imagine if each of these people immediately received their own labeled copy with a unique marking, which is invisible, but by which it is possible to identify the owner in the event of a leak. This would greatly simplify the search for violators and reduce the number of leaks.

How do you implement such mass labeling? The solution is offered by the G-71 company, which created the LeaksID solution. When exchanging documents, the G-71 recommends you send not just a link to the cloud where the document is stored, but a link to the document in the LeaksID storage (virtual room).

This will be the same link as, for example, on Google Drive, but when someone clicks on it, not just the document will be downloaded, but a unique copy that is instantly individually marked. The system will automatically create an individual copy for each user. Even if a fragment of such a marked report is published somewhere, then the source of the leak and the owner of the particular copy can be determined from the photo or screenshot.

At the same time, using the LeaksID solution, copies will be created not only when downloaded from a link but also when opened in a viewer. And if the violator decides to use a phone to take a photo of an open document and post it somewhere, then even from the photo, it will be possible to reveal it.

The marking will be created every time someone accesses the document which has been posted by the link (including even just viewing it).

You may also find this interesting