For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

Local users used for Azure Storage misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID

APPSEC_AZURE_244

Category - Subcategory

Public Exposure - Storage Buckets

Provider

AZURE

Severity

LOW

Framework

Terraform, Terraform Plan

Impact

This rule detects whether local users are used within Azure Storage accounts. Local users can pose a security risk as they may have direct access to the storage account, which could lead to unauthorized data access or compromise if their credentials are exposed or not managed securely. The best practice is to use Azure Active Directory (AD) identities or managed identities for access control. Azure AD offers advanced security features, centralized management, and stronger authentication methods, reducing the risk of unauthorized access compared to local users, which rely solely on static credentials.

How to Fix

Resource: azurerm_storage_account

  • Arguments: local_user_enabled

Use Azure Active Directory or other centralized identity management solutions to control access to Azure Storage accounts. Relying on Azure AD reduces the dependency on static credentials. Avoid using local users, as they depend on static credentials, which can be less secure and harder to manage.

In this example, the configuration of the Azure Storage account is modified to disable the use of local users by switching the local_user_enabled setting from true to false, ensuring the use of centralized identity management. [source,go]

resource "azurerm_storage_account" "fail" { ...

  • local_user_enabled = true

  • local_user_enabled = false }


Last updated

Was this helpful?