elastic / elastic/cloudbeat

Support for CIS Microsoft Azure Storage Services Benchmark

Open
#6,575 0 comments 0 reactions 0 assignees View on GitHub
Team:Cloud Security
Dominant language
Go
Stars
58
Forks
55
Avg merge
9h 9m
Merged PRs (30d)
424

Description

**Is your feature request related to a problem? Please describe.**

Yes. Elastic CSPM for Azure currently only implements the CIS Microsoft Azure Foundations Benchmark (v2.0.0). Anyone who requires deeper, resource-specific compliance auditing cannot validate their environments against specialized, standalone CIS benchmarks.

Specifically, we noted that advanced storage rules (such as blocking public network access or enforcing private endpoints) are missing the specific framework mappings and granular checks found in dedicated storage compliance profiles.

**Describe the solution you'd like**

Expand Elastic CSPM coverage to support the dedicated CIS Microsoft Azure Storage Services Benchmark (starting with v1.0.0). This includes mapping and implementing specific rules, such as:

- Rule 17.13: Ensure that 'Allow Blob Anonymous Access' is set to 'Disabled'
- Rule 17.2.1: Ensure Private Endpoints are used to access Storage Accounts
- Rule 8.3.7: Ensure Public Network Access is Disabled

**Describe alternatives you've considered**

Using the existing Azure Foundations Benchmark v2.0.0 rules (e.g., Rule 3.7 for public access and Rule 3.10 for Private Endpoints) as a workaround. While the underlying security checks are similar, this is not a sustainable alternative because the rule numbering, framework mapping, and compliance reporting do not accurately reflect the dedicated CIS Storage Benchmark required by auditors.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.