I have a client that needs to launch a hippa compliant application running on Windows 2003/Coldfusion/Oracle. They are also trying to save costs since this deployment will be a backup, and not the primary site. It still needs to be active though, so that it can receive updates to the data, etc. If there is ever a disaster, we can re-allocate resources to the server pretty quickly, in case capacity needs to grow.
Having said that, can a secure Virtual Machine be hippa compliant since the hardware is still shared? Nobody else would be getting into their OS, etc. but there would be multiple virtual machines running from the same NAS. So technically, the data is on a shared storage system.
Assuming all of their other practices are hippa compliant, would this still be applicable?
Having said that, can a secure Virtual Machine be hippa compliant since the hardware is still shared? Nobody else would be getting into their OS, etc. but there would be multiple virtual machines running from the same NAS. So technically, the data is on a shared storage system.
Assuming all of their other practices are hippa compliant, would this still be applicable?