Skip to content

Commit d2407fa

Browse files
author
David Curwin
committed
add network access section
1 parent 970ac87 commit d2407fa

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/backup/security-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ This article introduces security capabilities in Azure Backup that help you prot
1313

1414
With Azure Backup, which includes full IaaS VM backup and SQL/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. In the case of IaaS VM 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. In the case of SQL and HANA, the backup extension gets temporary access to write to specific blobs. In this way existing backups can't be tampered with or deleted by the guest, should it be compromised.
1515

16+
## Azure VM backup doesn't require network connectivity
17+
18+
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/FQDNs or any other methods to allow network access.
19+
1620
## Manage and control identity and user access
1721

1822
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.

0 commit comments

Comments
 (0)