More Info:

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 does not support HTTPS for custom domain names, this option is not applied when using a custom domain name.

Risk Level

Medium

Address

Security

Compliance Standards

SOC2, PCIDSS, ISO27001, HIPAA, CISAZURE, CBP, HITRUST, NISTCSF

Triage and Remediation

Remediation

To remediate the “Secure Transfer (HTTPS) Not Enforced” misconfiguration in Azure, follow these steps:

  1. Log in to the Azure portal.

  2. Navigate to the storage account that needs to be remediated.

  3. Click on the “Firewalls and virtual networks” tab.

  4. Ensure that “Allow access from” is set to “Selected networks”.

  5. Click on the “Selected networks” tab and ensure that “All networks” is not selected.

  6. Add the IP addresses or ranges that need to access the storage account.

  7. Click on the “Secure transfer required” toggle switch to enable HTTPS.

  8. Click on the “Save” button to save the changes.

  9. Verify that HTTPS is enforced by attempting to access the storage account using HTTP. Access should be denied.

By following these steps, you can remediate the “Secure Transfer (HTTPS) Not Enforced” misconfiguration in Azure.

Additional Reading: