prevent code stealing
-
heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports Hire honest people and pay them enough so that they won't feel that stealing your software is necessary. I don't know how many of the top pieces of information are actually feasable in your instance - but I worked at a place that had nearly that exact same setup...
Before I got my current job I spent a long period temping, and one of the assignments was at an RAF base They were in the process of rolling out a new system that was incredibly paranoid From memory: Only internal email (there'd be a departmental email address that was visable from outside, that only a particular computer could access, so people had to go to that and forward stuff to their own internal account) No internet access No access to *any* drive or folder on the computer bar My Documents DirectX, Media Player, and any kind of audio/video codec stripped out Firewire, USB, serial, parallel all disabled Network printing disabled (erm... how can you print?) and hundreds of other little things that you'd always find yourself needing Oh, by the way, I was working in a graphics/media shop (doing lots of graphics and video work - so the lack of the ability to print or use video would've been quite a problem, as was the fact that the promo videos being produced would no longer play on anybody's computers due to the lack of player codecs) Joy -- Help me! I'm turning into a grapefruit! Phoenix Paint - back from DPaint's ashes!
-
hello I supervise a team for developing software in c# and I always worry some of my members may steal the code to modify part of them and then to sell them as software components or as a complete program. What measures could I take to prevent this ? We develop in a software components approach to build up a large software.
Just to add to your paranoia. No matter what measures you take, you can not take away their knowledge to produce the code again...and second time round it is likely to be better! ;) Seriously, you need to trust your co-workers and make them feel important / wanted. In this sort of environment people are less likely to want to stray. Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Bobum wrote: heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports heh - heh, and then watch your developers leave, good one - not.
norm.net wrote: Bobum wrote: heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports heh - heh, and then watch your developers leave, good one - not. Believe it or not, that's standard for military projects like the one I'm working on :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
If they are your employees, make 'em sign a Non-Disclosure Agreement and/or Non-Compete Agreement. If they are your business partners and you're that paranoid, then maybe you shouldn't be in business with people you're afraid will rob you blind. Jeremy Falcon
A no-compete agreement can be successfully defeated in court in right-to-work states. Afterall, you gain a certain level of expert knowledge for a program you write, and you can take that expert knowledge with you to another company, and write different code based on that knowledge. Nobody can legally prevent you from exercising your expert knowledge or you chosen profession of "programmer". For instance, I spent 12 years writing estate planning software for one company and I gained a LOT of knowledge about the tax codes and other estate planning related stuff , and I could have quit at any time and went to work for one of our competitors, and my old employer couldn't have done a thing about it UNLESS I also used code fromt their program, and at that point, they could have sued my new employer as well. Employers are also reluctant to allow a programmer to bring in code from outside (code from CP notwithstanding). ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports Hire honest people and pay them enough so that they won't feel that stealing your software is necessary. I don't know how many of the top pieces of information are actually feasable in your instance - but I worked at a place that had nearly that exact same setup...
Bobum wrote: heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports Jail?... I guess nobody would like to work on a place like that.
-- **Ricky Marek** (_AKA: rbid_)-- "Things are only impossible until they are not" --- Jean-Luc Picard My articles -
Bobum wrote: Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports Woah woah woah! Better not stop there, gotta disable all the development tools also, and maybe the OS just to be safe. Can't be having those developers writing software that might allow them to transmit data using radio signals generated by altering their monitor refresh rates. Hmm, better take away the monitor too, as they might be able to read the code and remember it long enough to copy it down when they got home. Oh, and don't forget about strip searches...
Shog9
I'm not the Jack of Diamonds... I'm not the six of spades. I don't know what you thought; I'm not your astronaut...
You must not be aware of Longhorn's ability to allow System Admins to turn off access to ALL removable storage media. Want to burn a CD with source code? Nope, can't do it. Okay then, I'll just stick in a thumb drive... nope, the USB ports don't recognize storage devices. You think it's difficult for a Sys Admin to monitor EVERYTHING you do on your computer? Longhorn will make it even eaiser. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
heh - this is a good one... Remove Internet Access, LAN only access Remove CDRW burners from dev PC's Remove Floppydrives Remove/disable USB ports Remove any network printers from dev PC's Remove/diasble com & parrallel ports Hire honest people and pay them enough so that they won't feel that stealing your software is necessary. I don't know how many of the top pieces of information are actually feasable in your instance - but I worked at a place that had nearly that exact same setup...
You forgot to enable the case intrusion alarm... In case they take the whole hard drive home for the evening...
