Skip to content

Commit 820b0e7

Browse files
authored
Merge pull request #107474 from dcurwin/security-overview-march2020
Security Overview Page
2 parents 5fb693b + e34c6b3 commit 820b0e7

File tree

3 files changed

+122
-0
lines changed

3 files changed

+122
-0
lines changed
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: Azure Backup compliance offerings
3+
description: Summary of compliance offerings for Azure Backup
4+
ms.topic: conceptual
5+
ms.date: 03/16/2020
6+
---
7+
8+
# Azure Backup compliance offerings
9+
10+
To help organizations comply with national, regional, and industry-specific requirements governing the collection and use of individuals' data, Microsoft Azure & Azure Backup offer a comprehensive set of certifications and attestations.
11+
12+
You can find below compliance offerings for Azure Backup to ensure your service is regulated when using the Azure Backup service.
13+
14+
## Global
15+
16+
* [CSA-STAR-Attestation](https://docs.microsoft.com/microsoft-365/compliance/offering-csa-star-attestation)
17+
* [CSA-Star-Certification](https://docs.microsoft.com/microsoft-365/compliance/offering-csa-star-certification)
18+
* [CSA-STAR-Self-Assessment](https://docs.microsoft.com/microsoft-365/compliance/offering-csa-star-self-assessment)
19+
* [ISO 20000-1:2011](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-20000-1-2011)
20+
* [ISO 22301](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-22301)
21+
* [ISO 27001](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-27017)
22+
* [ISO 27017](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-27017)
23+
* [ISO 27018](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-27018)
24+
* [ISO 9001](https://docs.microsoft.com/microsoft-365/compliance/offering-iso-9001)
25+
* [SOC 1,2,3](https://docs.microsoft.com/microsoft-365/compliance/offering-soc)
26+
27+
## US Government
28+
29+
* [DoD DISA L2, L4, L5](https://docs.microsoft.com/microsoft-365/compliance/offering-dod-disa-l2-l4-l5?view=o365-worldwide)
30+
* [FedRAMP](https://docs.microsoft.com/microsoft-365/compliance/offering-fedramp)
31+
* [FIPS 140-2](https://docs.microsoft.com/microsoft-365/compliance/offering-fips-140-2)
32+
33+
## Industry
34+
35+
* [HIPAA](https://docs.microsoft.com/microsoft-365/compliance/offering-hipaa-hitech)
36+
* [HITRUST](https://docs.microsoft.com/microsoft-365/compliance/offering-hitrust)
37+
* [PCI DSS](https://docs.microsoft.com/microsoft-365/compliance/offering-pci-dss)
38+
39+
## Regional
40+
41+
* [CCSL/IRAP (Australia)](https://docs.microsoft.com/microsoft-365/compliance/offering-ccsl-irap-australia)
42+
* [GDPR (EU)](https://www.microsoft.com/trustcenter/privacy/gdpr)
43+
44+
## Next steps
45+
46+
Find the latest coverage and details about compliance in [Microsoft TrustCenter](https://www.microsoft.com/TrustCenter/Compliance/default.aspx).

articles/backup/security-overview.md

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: Overview of security features
3+
description: Learn about security capabilities in Azure Backup that help you protect your backup data and meet the security needs of your business.
4+
ms.topic: conceptual
5+
ms.date: 03/12/2020
6+
---
7+
8+
# Overview of security features in Azure Backup
9+
10+
One of the most important steps you can take to protect your data is to have a reliable backup infrastructure. But it's just as important to ensure that your data is backed up in a secure fashion, and that your backups are protected at all times. Azure Backup provides security to your backup environment - both when your data is in transit and at rest. This article lists security capabilities in Azure Backup that help you protect your backup data and meet the security needs of your business.
11+
12+
## Internet connectivity not required for Azure VM backup
13+
14+
Backup of Azure VMs requires movement of data from your virtual machine's disk to the Recovery Services vault. However, all the required communication and data transfer happens only on the Azure backbone network without needing to access your virtual network. Therefore, backup of Azure VMs placed inside secured networks doesn't require you to allow access to any IPs or FQDNs.
15+
16+
## Private Endpoints for Azure backup
17+
18+
You can now use [Private Endpoints](https://docs.microsoft.com/azure/private-link/private-endpoint-overview) to back up your data securely from servers inside a virtual network to your Recovery Services vault. The private endpoint uses an IP from the VNET address space for your vault, so you do not need to expose your virtual networks to any public IPs. Private Endpoints can be used for backing up and restoring your SQL and SAP HANA databases that run inside your Azure VMs. It can also be used for your on-premises servers using the MARS agent.
19+
20+
>[!NOTE]
21+
> This feature is currently in limited availability. Please fill out [this survey](https://forms.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR0H3_nezt2RNkpBCUTbWEapUQk5EQ1QxRzVOWDNDS1Y1Q0xLTkdLQ0U0RC4u) and email us at [email protected] if you are interested in using Private Endpoints for Azure Backup. The ability to use this feature is subject to approval from the Azure Backup service.
22+
23+
## Separation between guest and Azure storage
24+
25+
With Azure Backup, which includes virtual machine backup and SQL and SAP HANA in VM backup, the backup data is stored in Azure storage and the guest has no direct access to backup storage or its contents. With virtual machine backup, the backup snapshot creation and storage is done by Azure fabric where the guest has no involvement other than quiescing the workload for application consistent backups. With SQL and SAP HANA, the backup extension gets temporary access to write to specific blobs. In this way, even in a compromised environment, existing backups can't be tampered with or deleted by the guest.
26+
27+
## Management and control of identity and user access
28+
29+
Azure Backup enables you to manage fine-grained access using [Azure Role-Based Access Control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles). RBAC allows you to segregate duties within your team and grant only the amount of access to users necessary to do their jobs.
30+
31+
Azure Backup provides three built-in roles to control backup management operations:
32+
33+
* Backup Contributor - to create and manage backups, except deleting Recovery Services vault and giving access to others
34+
* Backup Operator - everything a contributor does except removing backup and managing backup policies
35+
* Backup Reader - permissions to view all backup management operations
36+
37+
Learn more about [Role-Based Access control to manage Azure Backup](https://docs.microsoft.com/azure/backup/backup-rbac-rs-vault).
38+
39+
Azure Backup has several security controls built into the service to prevent, detect, and respond to security vulnerabilities. Learn more about [security controls for Azure Backup](https://docs.microsoft.com/azure/backup/backup-security-controls).
40+
41+
## Encryption of data in transit and at rest
42+
43+
Encryption protects your data and helps you to meet your organizational security and compliance commitments. Within Azure, data in transit between Azure storage and the vault is protected by HTTPS. This data remains on the Azure backbone network.
44+
45+
* Backup data is automatically encrypted using Microsoft-managed keys. You can also encrypt your backed up managed disk VMs in the Recovery Services Vault using [customer managed keys](https://docs.microsoft.com/azure/backup/backup-azure-security-feature-cloud#encryption-of-backup-data-using-customer-managed-keys) stored in the Azure Key Vault. You don't need to take any explicit action to enable this encryption. It applies to all workloads being backed up to your Recovery Services vault.
46+
47+
* Azure Backup supports backup and restore of Azure VMs that have their OS/data disks encrypted with Azure Disk Encryption (ADE). [Learn more about encrypted Azure VMs and Azure Backup](https://docs.microsoft.com/azure/backup/backup-azure-vms-encryption).
48+
49+
## Protection of backup data from unintentional deletes
50+
51+
Azure Backup provides security features to help protect backup data even after deletion. With soft delete, if user deletes the backup of a VM, the backup data is retained for 14 additional days, allowing the recovery of that backup item with no data loss. The additional 14 days retention of backup data in the "soft delete" state doesn't incur any cost to the customer. [Learn more about soft delete](https://docs.microsoft.com/azure/backup/backup-azure-security-feature-cloud#soft-delete).
52+
53+
## Monitoring and alerts of suspicious activity
54+
55+
Azure Backup provides [built-in monitoring and alerting capabilities](https://docs.microsoft.com/azure/backup/backup-azure-monitoring-built-in-monitor) to view and configure actions for events related to Azure Backup. [Backup Reports](https://docs.microsoft.com/azure/backup/configure-reports) serve as a one-stop destination for tracking usage, auditing of backups and restores, and identifying key trends at different levels of granularity. Using Azure Backup's monitoring and reporting tools can alert you to any unauthorized, suspicious, or malicious activity as soon as they occur.
56+
57+
## Security features to help protect hybrid backups
58+
59+
Azure Backup service uses the Microsoft Azure Recovery Services (MARS) agent to back up and restore files, folders, and the volume or system state from an on-premises computer to Azure. MARS now provides security features to help protect hybrid backups. These features include:
60+
61+
* An additional layer of authentication is added whenever a critical operation like changing a passphrase is performed. This validation is to ensure that such operations can be performed only by users who have valid Azure credentials. [Learn more about the features that prevent attacks](https://docs.microsoft.com/azure/backup/backup-azure-security-feature#prevent-attacks).
62+
63+
* Deleted backup data is retained for an additional 14 days from the date of deletion. This ensures recoverability of the data within a given time period, so there's no data loss even if an attack happens. Also, a greater number of minimum recovery points are maintained to guard against corrupt data. [Learn more about recovering deleted backup data](https://docs.microsoft.com/azure/backup/backup-azure-security-feature#recover-deleted-backup-data).
64+
65+
## Compliance with standardized security requirements
66+
67+
To help organizations comply with national, regional, and industry-specific requirements governing the collection and use of individuals' data, Microsoft Azure & Azure Backup offer a comprehensive set of certifications and attestations. [See the list of compliance certifications](compliance-offerings.md)
68+
69+
## Next steps
70+
71+
* [Security features to help protect cloud workloads that use Azure Backup](backup-azure-security-feature-cloud.md)
72+
* [Security features to help protect hybrid backups that use Azure Backup](backup-azure-security-feature.md)

articles/backup/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -338,6 +338,8 @@
338338
href: backup-rm-template-samples.md
339339
- name: Security
340340
items:
341+
- name: Overview
342+
href: security-overview.md
341343
- name: Role-Based Access Control
342344
href: backup-rbac-rs-vault.md
343345
- name: Security for cloud workloads
@@ -384,6 +386,8 @@
384386
href: /azure/templates/microsoft.recoveryservices/allversions
385387
- name: Resources
386388
items:
389+
- name: Compliance
390+
href: compliance-offerings.md
387391
- name: Azure Roadmap
388392
href: https://azure.microsoft.com/roadmap/
389393
- name: MSDN forum

0 commit comments

Comments
 (0)