Description:

The Data in the storage account has various levels of security to protect the data from anonymous access, they are CORS, Management plane & Data plane, Encryption(at rest, in transit). Encryption in transit protects the sensitive data by encrypting it while it was transferred from one location to other.


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.


Impact:

We can harden the level of security of data stored in the storage account by accepting only secure requests.

Default Value:

By default, Secure transfer required is set to enabled.

Audit:

  1. Sign in to your Azure account.

  2. Go to Storage Accounts

  3. For each storage account, go to Configuration

  4. Check that the Secure transfer required is set to Enabled(In this scenario it is enabled as default).

Remediation:

Pre-requisites:

  1. An Azure account

  2. Storage account within an Azure subscription.

Implementation Steps:

  1. Sign in to your Azure account.

  2. Go to Storage Accounts

  3. For each storage account, go to Configuration

  4. Set the Secure transfer required setting to Enabled(for Encryption in Transit) and click on Save.

Backout Plan:

  1. Sign in to your Azure account.

  2. Go to Storage Accounts

  3. For each storage account, go to Configuration

  4. Set the Secure transfer required setting to Disabled(to allow the unsecured connections[HTTP]) and click on Save.

References: