Skip to main content

📝 Azure Storage Account Secure Transfer Required is not enabled 🟢

  • Contextual name: 📝 Secure Transfer Required is not enabled 🟢
  • ID: /ce/ca/azure/storage/secure-transfer-required
  • Located in: 📁 Azure Storage

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-d95ea48b1

Logic​

Description​

Open File

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​
  1. Go to Storage Accounts.
  2. For each storage account, under Settings, click Configuration.
  3. Ensure that Secure transfer required is set to Enabled.
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:

... see more

Remediation​

Open File

Remediation​

From Azure Portal​

  1. Go to Storage Accounts.
  2. For each storage account, under Settings, click Configuration.
  3. Set Secure transfer required to Enabled.
  4. Click Save.

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

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 APRA CPG 234 → 💼 54 Cryptographic techniques can be used to control access to sensitive data, both in storage and in transit. The strength of the cryptographic techniques deployed would be commensurate with the sensitivity and criticality of the data as well as other supplementary or compensating controls (refer to Attachment E for further guidance).1718
💼 CIS Azure v1.1.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled'11
💼 CIS Azure v1.3.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled' - Level 1 (Automated)11
💼 CIS Azure v1.4.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled' - Level 1 (Automated)11
💼 CIS Azure v1.5.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled' - Level 1 (Automated)11
💼 CIS Azure v2.0.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled' - Level 1 (Automated)11
💼 CIS Azure v2.1.0 → 💼 3.1 Ensure that 'Secure transfer required' is set to 'Enabled' - Level 1 (Automated)11
💼 CIS Azure v3.0.0 → 💼 4.1 Ensure that 'Secure transfer required' is set to 'Enabled' (Automated)1
💼 Cloudaware Framework → 💼 Data Encryption31
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3747
💼 FedRAMP High Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)23165
💼 FedRAMP High Security Controls → 💼 AC-4(4) Flow Control of Encrypted Information (H)2021
💼 FedRAMP High Security Controls → 💼 AC-17(2) Protection of Confidentiality and Integrity Using Encryption (M)(H)13
💼 FedRAMP High Security Controls → 💼 AU-3(1) Additional Audit Information (M)(H)14
💼 FedRAMP High Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)10633
💼 FedRAMP High Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)1610
💼 FedRAMP High Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)610
💼 FedRAMP High Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)1316
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)47
💼 FedRAMP Low Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)23
💼 FedRAMP Low Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)110
💼 FedRAMP Low Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)10
💼 FedRAMP Low Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)16
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)47
💼 FedRAMP Moderate Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)151
💼 FedRAMP Moderate Security Controls → 💼 AC-17(2) Protection of Confidentiality and Integrity Using Encryption (M)(H)13
💼 FedRAMP Moderate Security Controls → 💼 AU-3(1) Additional Audit Information (M)(H)14
💼 FedRAMP Moderate Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)729
💼 FedRAMP Moderate Security Controls → 💼 SC-8 Transmission Confidentiality and Integrity (L)(M)(H)110
💼 FedRAMP Moderate Security Controls → 💼 SC-8(1) Cryptographic Protection (L)(M)(H)10
💼 FedRAMP Moderate Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)16
💼 ISO/IEC 27001:2013 → 💼 A.10.1.1 Policy on the use of cryptographic controls1415
💼 ISO/IEC 27001:2013 → 💼 A.14.1.3 Protecting application services transactions78
💼 ISO/IEC 27001:2022 → 💼 5.14 Information transfer89
💼 ISO/IEC 27001:2022 → 💼 5.28 Collection of evidence1415
💼 ISO/IEC 27001:2022 → 💼 8.15 Logging1920
💼 NIST CSF v1.1 → 💼 DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed1011
💼 NIST CSF v1.1 → 💼 ID.AM-3: Organizational communication and data flows are mapped33
💼 NIST CSF v1.1 → 💼 PR.AC-5: Network integrity is protected (e.g., network segregation, network segmentation)713
💼 NIST CSF v1.1 → 💼 PR.DS-2: Data-in-transit is protected1421
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented4351
💼 NIST CSF v1.1 → 💼 PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity1819
💼 NIST CSF v1.1 → 💼 PR.PT-4: Communications and control networks are protected713
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events89
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained31
💼 NIST CSF v2.0 → 💼 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk13
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected82
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected69
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected67
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage40
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(2) Information Flow Enforcement _ Processing Domains2527
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(14) Information Flow Enforcement _ Security or Privacy Policy Filter Constraints22
💼 NIST SP 800-53 Revision 5 → 💼 AC-17(2) Remote Access _ Protection of Confidentiality and Integrity Using Encryption1113
💼 NIST SP 800-53 Revision 5 → 💼 AU-3(1) Content of Audit Records _ Additional Audit Information1314
💼 NIST SP 800-53 Revision 5 → 💼 SC-8(1) Transmission Confidentiality and Integrity _ Cryptographic Protection810
💼 PCI DSS v3.2.1 → 💼 4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during transmission over open, public networks.169
💼 PCI DSS v4.0.1 → 💼 4.2.1 Strong cryptography and security protocols are implemented to safeguard PAN during transmission over open, public networks.29
💼 PCI DSS v4.0 → 💼 4.2.1 Strong cryptography and security protocols are implemented to safeguard PAN during transmission over open, public networks.29