How do organizations with BYOD policy handle code theft?
<p>Some corporations have a Bring Your Own Device (BYOD) policy, and some may allow their employees to take their laptops home for usage. What if an employee takes the code and develops something outside of their employment scope?  </p>

<p>An organization may be able to file a patent infringement lawsuit if their code is used, but what if a malicious employees steals non patented or patent pending code and sell it to someone else? How do the organizations handle these cases?</p>

<p>EDIT:<br>
I agree with the copyright answer. I will search it further on the law Stack exchange site as suggested in the answer and the comments.
This is different from <a href="https://security.stackexchange.com/questions/109087/how-do-large-companies-protect-their-source-code">the other question</a> because there they OP is asking about ways to protect the source code. I am interested in impact of code theft and ways to handle it.</p>

<p>Patents are not that relevant in this case. Software patents are unenforceable in most parts of the world anyway.</p>

<p>What matters here is copyright. Every work contract has a clause that everything an employee creates as part of their employment is copyrighted by the company. So using company-owned code to build an own project would be a copyright violation. There are also other legal tools in some jurisdiction which can be used against employees trying to misuse intellectual company property. But that's a topic for <a href="https://law.stackexchange.com/">Law Stackexchange</a>.</p>

<p>Also, this isn't really related to a BYOD policy. Being able to bring your own device to work and then back home might make data theft more convenient, but isn't required. There are many other ways to steal sourcecode, like USB drives or uploading them to the internet. </p>

<p>To prevent the first you would have to design your software development offices like a supermax prison facility with meter-high walls (so nobody can throw a device over it) and strip searches on everyone leaving the building. This is neither feasible nor reasonable for anything below matters of national security.</p>

<p>To prevent the second, you would have to completely prevent internet access from developer workstations, which would greatly impede the productivity of any software developer.</p>

<p>So most companies do not even try to physically prevent employees from stealing sourcecode. They rather rely on the legal safeguards and on maintaining a mutual trust relationship with their employees. It might seem counter-intuitive to some, but when you do <strong>not</strong> treat your employees like potential criminals they are in fact <strong>less</strong> likely to betray you.</p>

<p>So you are afraid that if I bring my own computer to work, then I could steal code. I'll let you in on a secret: I sometimes work from home, and take my company supplied computer to my home. Now you can try to tell me how that situation would be different. I have a computer at home that contains a lot of my company's source code, and I could just copy it. </p>

<p>I'll let you in on another secret: Amazon sells 128 GB flash drives for under £30. Nobody would notice if a plug that drive into my computer at work, copied everything to the flash drive, and took it home. </p>

<p>The method of sending source code through the internet was mentioned; but that is a stupid thing to do, because that would allow you to be caught. </p>

<p>There are several reasons why I don't do this and use the source code to develop something outside work, or sell it to a competitor: First, I'm an honest person. Second, I know that if I did anything that damaged the company, they would drag me into court and would make my life hell. Instead of living in a nice home, I would end up living in a cardboard box. Third, if I tried to sell this source code to any competitor, their legal department would immediately call my company's legal department, and the same things as under (Second) would happen. Fourth, many developers write software that wouldn't actually be of any use to any competitor. </p>

copyright