Real-time preservation of your most recent code changes inevitably affects your ability to expect the unexpected. If you must think long and hard about who has access to the registry, and who is responsible for the backup and off-site storage, you are exposed. If you can’t name the person responsible for leading your disaster recovery team, you are overexposed.

How can these issues be addressed? First, Management must put more emphasis on the security of the code. Just backing up the code on another box and occasionally making sure that the latest version installs is not enough -- security is important.

You can never be too careful about off-site storage. When we run a security audit, developers tell us how they’d like to save their original code nightly. Think of the consequences to the software company stakeholders if the code is lost.

It is incumbent upon the General Manager to designate a responsible team member to put a plan in place, and practice it. This protects your company from an easily avoidable risk.

The security audit is your primary initiative to get your latest product to market on time and on budget. A security audit will help you sleep at night.