May 2, 2019

The following is provided from Microsoft Security and Compliance blogs at TechCommunity:

As part of our commitment to providing our customers with the peace of mind that your applications, and data, are safe and available in Office 365, we are pleased to announce that Microsoft Office 365 has achieved ISO 22301 certification. ISO 22301 is the premium standard for business continuity, and certification demonstrates conformance to rigorous practices to prevent, mitigate, respond to, and recover from disruptive incidents.

 

For years, we’ve heard from organizations about the importance of disaster preparedness and continuous improvement in their operations to ensure their IT systems can survive, and be restored, in the aftermath of major incidents (such as natural disasters, power outages, or cyber-attacks). We were the first major cloud provider to prove our commitment of being fully prepared for all eventualities through this internationally recognized standard for business continuity. 

 

What does this mean for our customers? It gives you the assurance that you can trust Microsoft Office 365 with your mission critical content by providing an extensive independent 3rd party audit of all aspects of Office 365’s business continuity. This includes the following:

  • how backups are validated
  • how recovery is tested
  • documented training for critical staff
  • the level of resources available
  • buy-in by senior management
  • how risks are assessed/mitigated
  • adherence to legal/regularly requirements
  • the process for response to incidents
  • the process for learning from incidents

 

Achieving the ISO 22301 certification demonstrates the seriousness of our commitment to providing you the highest quality of service, and we’ll continue to prioritize our customer data’s continuity and ensure we are handling it responsibly.

 

To learn more about Microsoft Office 365’s ISO 22301 certification and download a copy of the certification, please see the resources below:

The above was provided from Microsoft Security and Compliance blogs at TechCommunity

You May Also Like…