Question

VMware does have some built in solution for these situations. You can hard code the IP and you can force the MAC address to follow in the same cluster. From a risk assessment for the project this was hard to plan against since it was a small item to consider. That is why I usually have a burn in period before the system goes live just in case these type of situation

Think of the projects that you have done or are working on currently. Looking at the risk assessments how do you go about calculating this type of issues? Do you add in a "burn in period"? Do you normally add over head into the project for items that may go wrong?

CMGT/442 Information Systems Risk Management

Answer 1

I work in an IT company where projects keep coming continuously. So we do not have a relaxation time while switching from one project to another. The developers need to keep testing the code so that all loopholes are addressed before project release. However sometimes it does happen that a minor modification is detected near the closing phase of the project. Though the modification would have no major impact on the project but leaving the loophole as is, might be risky and make the project prone for various attacks. In such scenario, the team takes a decision to have a burn in period so that the project budget is not modified and the changes can be integrated smoothly.

Its our company’s policy not to add any overhead or charge the client for anything which went wrong from our side. We are an ethical company and we charge only for the successful work that we deliver.