Do the security p&amp;p thing.<p>One other thing that I haven&#x27;t hear yet is that you could do is introduce &quot;identifying easter eggs&quot; into the data if you can. Sorry, not sure what the right word is, but it&#x27;s a proven technique in certain high level negotiations. You make it easy for this employee to obtain an ever so slightly modified recent version of the data. The modifications are minimal, but allow to identify him as the source of the leak.<p>Document the easter eggs in a registered letter to yourself. Wait until fairly sure the &quot;custom&quot; version of the data is on employee&#x27;s machine. Then sue if he leaks.