Skip to content

feat(azure): add cosmosdb_account_backup_policy_continuous check#11032

Open
s1ns3nz0 wants to merge 2 commits intoprowler-cloud:masterfrom
s1ns3nz0:feat/azure-cosmosdb-backup-check
Open

feat(azure): add cosmosdb_account_backup_policy_continuous check#11032
s1ns3nz0 wants to merge 2 commits intoprowler-cloud:masterfrom
s1ns3nz0:feat/azure-cosmosdb-backup-check

Conversation

@s1ns3nz0
Copy link
Copy Markdown

@s1ns3nz0 s1ns3nz0 commented May 6, 2026

Summary

Adds a check that verifies CosmosDB accounts use the Continuous backup policy, enabling point-in-time restore for data recovery from accidental deletes or corruption.

What's added

  • New check: cosmosdb_account_backup_policy_continuous — FAIL when backup_policy_type != Continuous

Dependency

Depends on CosmosDB service-layer additions in #11031.

Context

Split from #10809 per @jfagoagas's review request to submit one PR per check.

s1ns3nz0 added 2 commits May 6, 2026 11:45
Adds a check that verifies CosmosDB accounts have automatic
failover enabled across multiple regions for resilience against
regional outages.

Includes service-layer additions for the CosmosDB check group:
enable_automatic_failover, backup_policy_type, public_network_access,
minimal_tls_version fields needed across the CosmosDB check stack.
Adds a check that verifies CosmosDB accounts use the Continuous backup policy, enabling point-in-time restore for data recovery from accidental deletes or corruption.

## What's added

- New check: `cosmosdb_account_backup_policy_continuous` — FAIL when `backup_policy_type != Continuous`

## Dependency

Depends on CosmosDB service-layer additions in prowler-cloud#11031.
@s1ns3nz0 s1ns3nz0 requested a review from a team as a code owner May 6, 2026 02:45
@github-actions github-actions Bot added provider/azure Issues/PRs related with the Azure provider metadata-review community Opened by the Community labels May 6, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Opened by the Community metadata-review provider/azure Issues/PRs related with the Azure provider

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant