By Arun Verma
Investor and Advisor, NakodaX ·
NakodaX blog/Perspective·2 min read
Five everyday ways a good team loses control of files
A good team loses control of files in five normal situations: a partner sees more data than needed, a proposal outlives a lost deal, a developer keeps the code, an employee keeps downloads, and a vendor keeps your data. NakodaX lets you change access after sharing in each case.
In each case, the file left for a good reason, and the reason ended before the file did.
When people picture a leak, they picture a villain. Most leaks are not like that. They are side effects of doing business with other people. Here are five that happen in almost every company.
1. The partner who sees more than they should
A logistics partner needs delivery addresses. You send the order table, which also holds phone numbers, order values and purchase history.
What NakodaX changes: Data Protection gives the partner their own file with only the columns they need. Other columns are left out, or sealed so the partner cannot read the values.
2. The proposal that outlives the deal
Your best proposal goes to a prospect. They pick someone else. Your pricing and approach stay in their inbox.
What NakodaX changes: Document Protection lets you revoke the proposal after the decision. The protected file stops opening.
3. The developer who moves on
An engineer finishes their time with you. Removing their repository access does not remove the copy already on their laptop.
What NakodaX changes: Source Protection encrypts the files that matter in the release. They run only with a license. End the license, and the protected files stop working at the next key request.
4. The employee who did nothing wrong
A colleague leaves on good terms. Their laptop and personal cloud hold three years of downloads. They will probably never open them. Probably.
What NakodaX changes: revoke at offboarding, and each protected file you shared with them stops opening, wherever the copy is.
5. The vendor you stopped using
An analytics vendor held your data for a year. The contract ended. Their backups did not.
What NakodaX changes: the vendor received protected files under their own license. End it, and keys stop being released, so new files cannot be opened. Files they had already opened stay with them.
The takeaway
Look at the five again. At least one has already happened in your business.
Common questions
Do leaks need a bad person?
No. Most come from normal work: a file sent for a good reason that stayed after the reason ended.
Which NakodaX product fits which situation?
Document Protection for documents like proposals and decks, Data Protection for tables and feeds, and Source Protection for code.
What can NakodaX not do in these situations?
It cannot take back what someone has already read, copied or photographed. It ends access that comes later.
