Permissions for Forest Recovery in Cayosoft Guardian
Cayosoft Guardian uses multiple identities such as connection accounts and Microsoft Entra applications to access and manage your environment.
When you add an Azure subscription under Forest Recovery > Cloud Services, the Add Azure subscription wizard supports two paths, with different prerequisites:
- Create a new application — Cayosoft Guardian creates the Microsoft Entra application automatically. The signed-in account must be able to create app registrations and grant the required API permissions in the tenant; this typically requires the Global Administrator role (or an equivalent privileged role).
- Use an existing application — the customer pre-creates the Entra application, service principal, and certificate, then provides the Subscription ID, Application ID, Tenant ID, and certificate during registration. No Global Administrator role is required in the tenant for this path. The pre-created service principal only needs the Azure RBAC roles listed in the tables below.
Microsoft Azure permissions
The roles that Cayosoft Guardian needs depend on how the recovery site is deployed:
- Cayosoft Guardian creates the Azure resources (default). Use the roles in the Create resources and Manage backups tables. These requirements are unchanged from earlier versions.
You provide the Azure resources (7.4 and later). When Use precreated resources is selected in the recovery site settings, Cayosoft Guardian never creates a resource group, virtual network, storage account, or Relay namespace. Grant the service principal the roles in the Customer-provided Azure resources table instead of the Contributor role.
Create resources
| System or task | Permissions | Details |
|---|---|---|
| Create Azure resources for recovery site | Contributor role in the resource group | Create a resource group manually and only allow Cayosoft Guardian to create the resources. |
| Create Azure resources for recovery site | Contributor role for the subscription | Assign this role to an account used to add a new subscription under Cloud Services. This allows the creation of resources across the subscription. |
Customer-provided Azure resources
Assign the following roles to the service principal when the recovery site uses precreated resources. Scope each role to the resource that it applies to, or to the resource group that contains the precreated resources.
| System or task | Permissions | Details |
|---|---|---|
| Read and write agent installers and backup data in the staging storage account | Storage Blob Data Contributor | Required on the customer-provided storage account. Cayosoft Guardian uploads agent installers and backup data, and deletes the backup data when recovery finishes. See Microsoft documentation. |
| Create the recovery site virtual machines, disks, and network interfaces | Virtual Machine Contributor | Required on the customer-provided resource group. Grants permission to create, configure, and remove the recovery site virtual machines and their disks and network interfaces. See Microsoft documentation. |
| Attach the recovery site to customer-provided Azure network resources | Network Contributor role on the existing virtual network (and on the network security group, if used) | Applies from version 7.3, when customer-provided network resources were introduced. Grants permission to attach network interfaces to the subnet and associate the existing network security group without modifying the network configuration itself. When the network resources live in a different resource group than the recovery site, assign this role at the network resource group scope. |
| Configure the Azure Relay hybrid connection | Azure Relay Owner on the Relay namespace | Cayosoft Guardian creates a hybrid connection inside your Azure Relay namespace and removes it with the recovery site. |
| Configure the Azure Relay hybrid connection with granular permissions | Custom role with the actions listed below |
Use instead of Azure Relay Owner if your organization requires least privilege:Microsoft.Relay/namespaces/readMicrosoft.Relay/namespaces/hybridConnections/readMicrosoft.Relay/namespaces/hybridConnections/writeMicrosoft.Relay/namespaces/hybridConnections/authorizationRules/writeMicrosoft.Relay/namespaces/hybridConnections/authorizationRules/listKeys/action
|
NOTE: Cayosoft Guardian does not change the configuration of resource groups, virtual networks, subnets, network security groups, storage accounts, or Relay namespaces supplied by the customer. It creates only the recovery site virtual machines and their disks and network interfaces, blobs in the storage account, and a hybrid connection in the Relay namespace. Inbound rules required by Cayosoft Guardian (WinRM and agent ports — see Planning and preparation: Required ports for Cayosoft Guardian) must be configured on the customer-managed network security group before deployment.
Manage backups
| System or task | Permissions | Details |
|---|---|---|
| Create an Azure share for backups | Contributor role in the resource group | Create a resource group manually and only allow Cayosoft Guardian to create resources, such as Azure file shares, for backups. |
| Using an Azure blob storage in backup plans | Storage Blob Data Contributor role | Assign this role to an account used to add a new subscription under Cloud Services. Grants read, write, and delete access to blob data within the assigned subscription for backup and recovery purposes. |
Manage storage
| System or task | Permissions | Details |
|---|---|---|
| Azure Storage access | Enabled from all networks | Applies when Cayosoft Guardian creates the storage account. Ensure network access is not restricted in Azure Storage Account settings to allow backup and recovery tasks. |
| Azure Storage access for a customer-provided staging storage account | Public network access disabled, with private endpoints | Supported in version 7.4 and later. You can disable public network access on your staging storage account if you create a private endpoint for the recovery site virtual network and another for the Cayosoft Guardian-side virtual network, and configure name resolution for both. See Configure Azure private endpoints for the staging storage account. |
NOTE: Cayosoft Guardian does not modify existing virtual networks, subnets, or network security groups supplied by the customer. Inbound rules required by Cayosoft Guardian (WinRM and agent ports — see Required Ports for Cayosoft Guardian) must be configured on the customer-managed NSG before deployment.
Manage backups
| System or task | Permissions | Details |
|---|---|---|
| Create an Azure share for backups | Contributor role in the resource group | Create a resource group manually and only allow Cayosoft Guardian to create resources, such as Azure file shares, for backups. |
| Using an Azure blob storage in backup plans | Storage Blob Data Contributor role | Assign this role to an account used to add a new subscription under Cloud Services. Grants read, write, and delete access to blob data within the assigned subscription for backup and recovery purposes. |
Manage storage
| System or task | Permissions | Details |
|---|---|---|
| Azure Storage access | Enabled from all networks | Ensure network access is not restricted in Azure Storage Account settings to allow backup and recovery tasks. |
AWS permissions
To back up to S3 storage and create resources in AWS, Cayosoft Guardian requires an account with the following permissions:
Create resources
| System or task | Permissions | Details |
|---|---|---|
| Provision and manage EC2 instances for the recovery site | AmazonEC2FullAccess | Full access to EC2 instances for provisioning, managing, and recovering resources at the recovery site. |
| Create and managing AWS resources | AWSCloudFormationFullAccess | Automating the deployment of the recovery site using infrastructure-as-code templates and defining the infrastructure setup in CloudFormation stacks. |
| Run automation scripts for failover, configuration adjustments, and recovery tasks | AWSLambda_FullAccess | Full access to AWS Lambda to run automation scripts for handling instance failover, configuration adjustments, and other event-driven recovery tasks. |
| Create and manage IAM roles and policies | IAMFullAccess | Create and manage IAM roles and policies required for the recovery site's services and components. Assign necessary permissions to recovery resources (e.g., allowing EC2 instances to access S3 or SSM). |
| Organize recovery-related resources using tags and resource groups |
ResourceGroupsandTagEditor FullAccess |
Organize recovery-related resources using tags and resource groups. Automate tagging of new resources to maintain proper tracking and cost allocation. |
Manage backups
| System or task | Permission/Role |
Details |
|---|---|---|
| Store recovery site backups, logs, and configurations | AmazonS3FullAccess | Full access to Amazon S3 for storing recovery site backups, logs, and configurations. |
| Enable automated retrieval of backup data when initiating recovery | AmazonS3FullAccess | Retrieve backup data stored in S3 buckets when initiating recovery processes. |
| Automate recovery processes using AWS Systems Manager | AmazonSSMFullAccess | Full access to AWS Systems Manager to automate recovery processes, including instance management, patching, and configuration. |
NOTE: Cayosoft recommends creating a separate organization and accounts for instant forest recovery, so the service accounts can only access resources required for forest recovery, and do not have access to production workloads.
Comments
0 comments
Please sign in to leave a comment.