The fine folks over at Veeam have recognized this reality and recently released v4 of the Veeam Backup for Office 365 applications. There’s little added value to an Organization running their own email infrastructure, so there has been an explosion in usage of Office 365 over the past few years. What I’d like to cover today is a brief exploration of the Veeam Backup for Microsoft Office 365. With this in mind, it seemed like an opportune time to look at how we’re protecting our Office 365 assets. Gartner has a good whitepaper (behind paywall, so not linked here) laying out that YOU are responsible for YOUR data, so you can’t presume that your Cloud provider is protecting it for you AWS alludes to this with their shared security model, but other cloud providers bury this fact in their T’s & C’s. But cutting straight to the chase, it’s your responsibility to ensure that your data is protected. But what about the data? Who is responsible for making sure that it’s protected? It’s a good fundamental question that there is a lot of FUD around. The premise of the conversation is that with Cloud, you push off ownership of the infrastructure/platform. I’ve had a debate with myself as to whether this is akin to when you buy a car, all of a sudden you notice just how many of your car are on the road OR as we’re approaching 2020 is everyone coming to the realization that even in the cloud you need to protect your assets and that not everything can be ephemeral. The topic of data protection for cloud services seems to surfacing a lot lately.
0 kommentar(er)
