*https://www.salesforce.com/solutions/industries/healthcare/overview/?bc=DB

 

If I were to pick something to support locally, I would pick jabber and cisco telemedicine. I would have a local server on site that is going to support the capabilities to be able to use this technology. Essentially the only thing that you do once it is set up, is updates and just make sure that you have backups just in case if an update break something. 

 

 

Even though, cloud computing is beginning to improve our day to day operations, there are a couple services that we would keep in our current on premise solution. Depending on whether or not the service has been implemented plays a huge role in whether it should stay on premise or moved to the cloud. Active Directory falls into the category of “if it’s not broke don’t fix it”, meaning that either Azure or a physical server hosting AD is fine, but will cause more hassle to migrate. In my opinion, file servers should remain on premise because it is a lot easier to plug in an encrypted drive to copy data to, instead of having to move file to the cloud. There is a bigger sense of physical security of the system that should be only accessible through our internal network. 

 

Sources Used

https://www.purestorage.com/products/staas/pure-as-a-service.html#:~:text=Whether%20on%2Dpremises%20or%20in,storage%20you've%20ever%20managed.&text=Deliver%20storage%20as%20a%20service,security%20of%20on%2Dpremises%20infrastructure.

https://www.modmed.com/

           I’d choose to have core services like DHCP, DNS, AD DS, and database services in house and also replicated in the cloud as part of a disaster recovery plan but turned off. This way I would be able to limit the attack vector of the company but at the same time be able to recover fast in an emergency. I’d choose to move web applications to the cloud. This would allow me to put the outside applications on another platform and use next generation equipment provided by the cloud vendor to further mitigate against possible security breaches. I’d also move the email service to a cloud platform, passing the headache of the hardware portion of enterprise mail to the service provider.

 

Resources

·       The Pro's & Con's of moving email services to the cloud

·       Migrating your Business to the Cloud: 5 Pro's & Con's

·       Hybrid Architecture & Security

https://www.linode.com/ (My favorite one)

 

Things I would keep in-house with cloud backup are DNS and file services, so they would still be available intranet should internet connections go out

The only things I would keep strictly in-house would be sensitive data that must remain secure.

 

https://sysgen.ca/cloud-vs-in-house-servers/

https://blog.storagecraft.com/cloud-vs-in-house-servers/

https://azure.microsoft.com/en-us/overview/

 

https://www.microsoft.com/en-us/microsoft-365/enterprise

I would maintain email and productivity software such as cloud solutions such as the Microsoft Enterprise Suite. Long term file storage backup would be kept cloud based however. Other solutions such as SalesForce cloud solutions for interacting and managing customer profiles and engagement (Client Relationship Management).

https://www.microsoft.com/en-us/microsoft-365/enterprise 

https://aws.amazon.com/ 

https://www.bluehost.com/ 

Most network services would be kept in-house such as AD and DHCP to name a few. It would also be beneficial to utilize Azure services for data analytics and database caching.