New answers tagged

0

You can secure your code in a limited fashion. Create a dedicated development environment where: The developers can connect with remote desktop only. All shared drives, clipboard sharing, local printing, etc. is disabled. The environment has no Internet access - or if it does, it's heavily restricted. With this setup, developers can view the code but ...


0

How can you place measures to prove later in court that that source code is yours? Place a copy in escrow prior to showing the code to anyone. When you form a partnership or employ someone, you might get them to sign a statement, preferably in front of witnesses, that acknowledges your ownership of a specified body of code. The statement might include a ...


2

It depends against what you want to secure your code. If this is code which will be used (as source code) in development then obviously you cannot secure anything. My rule of thumb is that one someone can see anything then you cannot secure it (this extends to all kind of DRM protected documents which you take a photo of, run though OCR and poof, there goes ...


1

There is an application called "OpenDLP" (data loss prevention) that can be used to scour your network for sensitive data. It is based on regexs so you could configure it to search for whatever you'd like: Passwords, keywords in intellectual property, social security numbers, credit cards. This would definitely help minimize the occurrences of data leakage. ...


2

The important files vary by programming language, and environment. For example, if you're running nginx, .htaccess files, by default, won't affect the behaviour of the server. However, those same files could really mess things up if someone loaded your application into an Apache environment. Therefore, you need to customise any list to your own needs. There ...


0

It looks like you want to consider Data Loss Prevention tools (https://en.wikipedia.org/wiki/Data_loss_prevention_software). However before you go straight to the technology solution, you have to understand what "normal" file access looks like. If you do not know what that looks like it becomes impossible to know what abnormal looks like. This is ...



Top 50 recent answers are included