Hi Scott, Thanks for the response.
The difficulty with applying encryption, is that the source has to be decrypted for the developer to work on it. Now you're back to square one. *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…* * GPG: *1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A On Thu, Dec 17, 2015 at 11:16 AM, Mayott, Scott [USA] <[email protected]> wrote: > Have you tried encryption utilizing a certificate with what you already > have? > > On Dec 17, 2015, at 11:04 AM, Andrew S. Baker <[email protected]> wrote: > > Good morning: > > Does anyone happen to have any experience with the protection of sensitive > source code? > > Essentially, we're looking to ensure that we can adequately mitigate the > risk of critical portions of the code being copied and used inappropriately. > > This is beyond any protections (real or imagined) offered by the > following, which we have in place today: > > -- An NDA > -- Restricted access to the source code repository, on a need to know basis > -- Two-factor authentication to access the repository (being considered) > > > An air-gapped network is not currently on the table for discussion. :) > > > Regards, > > > > > *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> > *Providing Virtual CIO Services (IT Operations & Information Security) for > the SMB market…* > > * GPG: *1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A > >
