lacework-global-528
3.1 Set 'Secure transfer required' to 'Enabled' (Automated)
Profile Applicability
• Level 1
Description
Enable data encryption in transit.
Rationale
The secure transfer option enhances the security of a storage account by only allowing requests to the storage account by a secure connection. For example, when calling REST APIs to access storage accounts, the connection must use HTTPS. Any requests using HTTP will be rejected when 'secure transfer required' is enabled. When using the Azure files service, connection without encryption will fail, including scenarios using SMB 2.1, SMB 3.0 without encryption, and some flavors of the Linux SMB client. Because Azure storage doesn’t support HTTPS for custom domain names, this option is not applied when using a custom domain name.
Audit
From Azure Portal
- Go to
Storage Accounts - For each storage account, go to
Configuration - Ensure that
Secure transfer requiredis set toEnabled
From Azure CLI
Use the below command to ensure the Secure transfer required is enabled for all the Storage Accounts by ensuring the output contains true for each of the Storage Accounts.
az storage account list --query "[*].[name,enableHttpsTrafficOnly]"
Remediation
From Azure Portal
- Go to
Storage Accounts. - For each storage account, go to
Configuration. - Set
Secure transfer requiredtoEnabled.
From Azure CLI
Use the below command to enable Secure transfer required for a Storage Account:
az storage account update --name <storageAccountName> --resource-group <resourceGroupName> --https-only true
References
https://docs.microsoft.com/en-us/azure/storage/blobs/security-recommendations#encryption-in-transit
https://docs.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest#az_storage_account_list
https://docs.microsoft.com/en-us/cli/azure/storage/account?view=azure-cli-latest#az_storage_account_update
https://docs.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-data-protection#dp-4-encrypt-sensitive-information-in-transit