Finding F-02
Eight storage accounts accept connections from any network; account keys are enabled on all of them.
Risk Level
Medium
Framework Domain
Data Security & Encryption
CSA CCM v4 Control
DSP-07; DSP-17; IVS-03
Control Title
Data Protection by Design; Sensitive Data Protection; Network Security
5.8
Risk score

Finding Description

Eight of the twelve storage accounts in the production subscription have publicNetworkAccess set to Enabled with the default rule Allow, so any address on the internet may attempt to reach their endpoints. On the same eight accounts allowSharedKeyAccess is true: a leaked account key grants full data-plane access without an identity, a sign-in or a conditional-access policy in the path. Three of the accounts hold exported customer statements; the others hold build artefacts and diagnostics.

Impact

A single leaked key, for example in a build log or a decommissioned laptop, reads or deletes every blob in the account from anywhere, and the access leaves no sign-in record because keys are not identities. The exposure is not exploitable by itself; it removes the two controls that would contain a credential leak.

References

  • CCM v4 DSP-07Data protection by design and by default
  • CCM v4 IVS-03Network security: restrict access to the services needed
  • CIS Azure 3.8, 3.9Default network access rule set to Deny; shared key authorization disabled
  • EvidencePage 12, capture 1 and the Resource Graph query

Affected Resources

8 of 12 storage accounts, sub-corporate-prod, public network access Enabled stcorpstatements01, stcorpstatements02, stcorpexports (customer data) allowSharedKeyAccess: true on all eight

Remediation & Solution Strategy

1. Set public network access to Disabled, or to Selected networks with the application subnets and the office egress address listed; expose the three customer-data accounts through private endpoints only.
2. Disable shared-key authorization (allowSharedKeyAccess: false) and move the two services that still use keys to managed identities with the Storage Blob Data Contributor role.
3. Enforce both settings with an Azure Policy assignment at the subscription scope in Deny mode, so a new account cannot recreate the exposure; see F-11 for the policy baseline.