/
Automation Account Variables Should be Encrypted
Automation Account Variables Should be Encrypted
Description:
It is important to enable encryption of Automation account variable assets when storing sensitive data.
Solution/Reference:
You should encrypt Automation Account Variables that store sensitive data. This step can only be taken at creation time. If you have Automation Account Variables storing sensitive data that are not already encrypted, then you will need to delete them and recreate them as encrypted variables. To apply encryption of the Automation account variable assets, in the Azure CLI - run the following command:
Set-AzAutomationVariable -AutomationAccountName '{AutomationAccountName}' -Encrypted $true -Name '{VariableName}' -ResourceGroupName '{ResourceGroupName}' -Value '{Value}'
, multiple selections available,
Related content
[Enable if Required] Azure Machine Learning Workspaces Should Be Encrypted With a Customer-Managed Key (CMK)
[Enable if Required] Azure Machine Learning Workspaces Should Be Encrypted With a Customer-Managed Key (CMK)
More like this
Cognitive Services Accounts Should Enable Data Encryption
Cognitive Services Accounts Should Enable Data Encryption
More like this
Storage Accounts Should Use Customer-Managed Key (CMK) for Encryption
Storage Accounts Should Use Customer-Managed Key (CMK) for Encryption
More like this
Disk encryption should be applied on virtual machines
Disk encryption should be applied on virtual machines
More like this
[Enable if Required] Cognitive Services Accounts Should Enable Data Encryption With a Customer-Managed Key (CMK)
[Enable if Required] Cognitive Services Accounts Should Enable Data Encryption With a Customer-Managed Key (CMK)
More like this
[Enable if Required] Azure Cosmos Db Accounts Should Use Customer-Managed Keys to Encrypt Data at Rest
[Enable if Required] Azure Cosmos Db Accounts Should Use Customer-Managed Keys to Encrypt Data at Rest
More like this