P REVENTING D ATA L EAKAGE VIA E MAIL Rostislav Pinski Dmitry Kaganov Eli Shtein Alexander Gorohovski

 Most of the people that use communication can confirm that at least once they have sent an to the wrong recipient.  Such a mistake can be very damaging. Inappropriate jokes may be sent to a supervisor, financial reports may be sent to a competitor or a broker, love letter to the wrong man or woman.  An example of such incident was published on portfolio.com site on February 5th 2008: “One of Eli Lilly & Co.'s sub-contracted lawyers at Philadelphia based Pepper Hamilton had mistakenly ed confidential Eli Lilly's discussions to Times reporter Alex Berenson (instead of Bradford Berenson, her co-counsel), costing Eli Lilly nearly $1 billion.”

 Modern business activities rely on extensive exchange. “wrong recipients” mistakes have become widespread, and the severe damage caused by such mistakes constitutes a disturbing problem both for organizations and for individuals.  Various solutions to this problem are continuously emerging, however there is still no “silver-bullet” solution: many addressing mistakes are not detected and in many cases correct recipients are wrongly marked as potential addressing mistake.

To develop a “ Preventing Data Leakage via » system for some client. The system will work using a theoretic model developed by Douche Telecom researchers and presented in the “Analyzing Group Communication for Preventing Data Leakage via “ article.

 The user composes an and pushes “send” button.  The is sent for inspection and validation by the system.  In case non-valid recipients are detected, a list of non- valid recipients will be displayed to the user for confirmation whether to continue sending to the non-valid recipients or no.  Optionally - a list of additional suggested recipients for this will be displayed to the user.  Optionally - the user will be able to send the easily to any of the recipients from the suggested recipients list.

 Changing the “send” button functionality (without having an access to its’ code).  Developing a system that can be relative easily adapted to any client.  Developing a server that can serve a plenty of clients simultaneously.  The delay in sending the should be linear to the s’ size and not longer than half a minute.  Data Security  Modularity