ASD's Blueprint for Secure Cloud

Backup and Operational Management

This section describes the design decisions associated backup and operational management configuration for system(s) built using ASD's Blueprint for Secure Cloud.

Estimated reading time: 7 minutes

RTO, RPO, and Retention

As with an on-premises environment, backups play an important part of an overall cloud solution capability. It is important that critical information is backed up to enable recovery for scenarios such as accidental deletion or corruption.

To ensure a successful backup, configuration of the following items should be taken into consideration:

  • What to backup - understanding what configuration data, files, and mailboxes need to be backed up is important. If only a partial configuration is backed up, successful restoration may not be possible.
  • Restoration destination - where will backed up data be restored. An Exchange Online mailbox, for example, may not be easily restored to an Exchange Server given differences in the underlying code bases.
  • Recovery Point Objective (RPO) - RPO defines an acceptable loss of data (in time) for a data type in a data-loss event. RPOs are expressed in hours / days and directly influence the backup approach, and how backups are performed with sufficient frequency to meet the defined RPO. For example, if an RPO of 12 hours was defined for a given data type, backups of this data type could not be scheduled further than 12 hours apart.
  • Recovery Time Objective (RTO) - RTO is used to define the acceptable level of service interruption (in time) between a data loss event and the recovery of the data to a point at which normal service is resumed. When determining RTOs for a given data type, consideration must also be given to any additional recovery process that are undertaken after the restoration of data. The RTO directly influences the type of backups performed and may dictate additional protection mechanisms outside of the backup platform for data types where a very short RTO is defined.
  • Legislative Requirements – The Essential Eight details that backups of important information, software and configuration settings are performed. More detail on these controls are listed in the Department of Home Affairs’ Protective Security Policy Framework and ASD’s Essential Eight Maturity Model.

It is important that prior to defining the backup and restore policies, RTO and RPO objectives for each data type hosted within the environment are defined in line with business requirements and Service Level Agreements (SLA).

There are several enterprise backup solutions which can backup data whether it is located on-premises or in the cloud. Depending on the organisations requirements, a backup solution may need to cover the following scenarios:

  • Backup local data directly to on-premises infrastructure from on-premises.
  • Backup local data to on-premises infrastructure and to the Azure storage blob from on-premises.
  • Backup cloud data directly from the cloud.

Using the native Microsoft 365 tools only, in combination with recycle bins, the following data recovery options and retention periods are available:

  • What to backup - understanding what configuration, files and mailboxes that need to be backed up is important. If only a partial configuration is backed up, successful restoration may not be possible.
  • Documents, Desktops and Pictures for each user is redirected from the Windows client device to OneDrive using Windows Known Folders providing a backup of data to the cloud.
  • OneDrive includes recycle bins allowing recovery of data for up to 93 days.
  • SharePoint Online data includes recycle bins allowing recovery of data for up to 93 days.
  • Teams chat, channel and files data retained indefinitely by default unless retention policies have been implemented.
  • Exchange Online has a recover deleted items from server option allowing recovery of data for up to 30 days.

The Blueprint defines retention policies, which can be modified to ensure that data is retained for longer than the defined seven years:

  • Exchange
  • SharePoint
  • OneDrive
  • Microsoft 365 groups
  • Skype for Business
  • Exchange Public Folders
  • Teams channel messages
  • Teams chats

Workstation configuration is stored within Microsoft Intune (Autopilot rebuild).

Organisations should review native Microsoft 365 capabilities and determine whether they meet data preservation requirements, or whether a third-party backup solution is required.

Cloud native deployments

Hybrid deployments

Data availability

Microsoft Azure services are available globally and provides geographical, regional, data centre, virtual infrastructure, and application resiliency. This enables the Microsoft Azure platform and Microsoft 365 to combat and minimise potential disasters such as customers loss of connectivity to data or loss of data.

The cloud-based services of Microsoft 365 replicate and store organisation’s data in multiple data centres which are geographically dispersed to provide the greatest possible availability for organisational data. Data resiliency in Microsoft 365 and Exchange Online data resiliency in Microsoft 365 provide further information.

Data availability and resiliency of Microsoft 365 cloud service is in-built and managed by Microsoft.

Security & Governance

  • None identified

Design

  • None identified

References

Do you have a suggestion on how the above page could be improved? Get in touch! ASD's Blueprint for Secure Cloud is an open source project, and we would love to get your input. Submit an issue on our GitHub, or send us an email at blueprint@asd.gov.au

Acknowledgement of Country icon

Acknowledgement of Country
We acknowledge the Traditional Owners and Custodians of Country throughout Australia and their continuing connections to land, sea and communities. We pay our respects to them, their cultures and their Elders; past, present and emerging. We also recognise Australia's First Peoples' enduring contribution to Australia's national security.

Authorised by the Australian Government, Canberra