Cloud security checks
The security_cloud module has 8 checks. Cloud posture (Azure Resource Graph, Defender for Cloud) and optional Wazuh findings, read-only. Resource Graph checks only look at the resource's resource_id (a resource, a resource group or a whole subscription); params.scope = resource makes that attribute required and params.scope = all looks at every subscription the identity can read. Defender for Cloud and Wazuh are switched on separately (features security.defender, security.wazuh); recommendations can be hidden (security.recommendations).
This page is generated from the product's check catalog when the documentation is built, so the rules, intervals and default severities always match the version you are reading. Thresholds are defaults; entities and resources can override them.
| Check | Every | Default severity | Rule |
|---|---|---|---|
security_cloud.nsg_exposed_portsManagement ports open to the Internet | 900s | critical | warning >= 1 count / critical >= 1 count |
security_cloud.public_storageStorage accounts allowing anonymous blob access or weak transport | 3600s | warning | publicBlob = false, httpsOnly = true, minTls = TLS1_2 |
security_cloud.keyvault_protectionKey Vault purge protection and soft delete | 3600s | warning | purge = true, softDelete = true |
security_cloud.rsv_protectionRecovery Services Vault soft delete and immutability | 3600s | warning | softDelete = Enabled,AlwaysON |
security_cloud.role_assignment_changesRBAC Owner / Contributor assignment changes | 600s | critical | any change |
security_cloud.defender_assessmentsDefender for Cloud recommendations and secure score | 3600s | warning | warning >= 1 count |
security_cloud.wazuh_alertsWazuh alerts (HIDS, FIM, CVE, CIS) | 300s | warning | warning >= 1 count |
security_cloud.platform_imagesPlatform container images and dependencies (CVE scan) | 3600s | warning | warning >= 1 count / critical >= 1 count |
Checks
security_cloud.nsg_exposed_ports
Management ports open to the Internet
- Measures
exposed_rules(count) · every900s·azure_graph- Rule
warning >= 1 count / critical >= 1 count· Default severity: critical- Action
- Find who needs the access. Replace the rule with Azure Bastion, a VPN or Defender for Cloud just-in-time VM access; if a public rule must stay, restrict its source to known addresses. Change the NSG in a change window and confirm the service is still reachable from where it should be.
- Baseline
- CIS Microsoft Azure Foundations Benchmark 6.x: never expose 22/3389/1433/5432/5985/5986 to the Internet; use Bastion, a VPN or just-in-time access. · source
security_cloud.public_storage
Storage accounts allowing anonymous blob access or weak transport
- Measures
posture· every3600s·azure_graph- Rule
publicBlob = false, httpsOnly = true, minTls = TLS1_2· Default severity: warning- Action
- Check with the application owner that no client reads blobs anonymously (storage metrics show anonymous requests), then set "Allow Blob anonymous access" to Disabled, "Secure transfer required" to Enabled and the minimum TLS version to 1.2 on the account, in a change window.
- Baseline
- CIS Azure Foundations 3.x. An unset allowBlobPublicAccess is reported for review (older accounts may still allow it). · source
security_cloud.keyvault_protection
Key Vault purge protection and soft delete
- Measures
posture· every3600s·azure_graph- Rule
purge = true, softDelete = true· Default severity: warning- Action
- Enable purge protection on the vault (it cannot be turned off again, and a deleted vault then stays recoverable for its retention period). Plan it with the vault owner, since automation that deletes and recreates vaults with the same name will stop working.
- Baseline
- CIS Azure Foundations 8.x. Soft delete can no longer be turned off on new vaults; purge protection is off unless enabled. · source
security_cloud.rsv_protection
Recovery Services Vault soft delete and immutability
- Measures
posture· every3600s·azure_graph- Rule
softDelete = Enabled,AlwaysON· Default severity: warning- Action
- Turn soft delete on for the vault (Properties › Security settings) and, for production vaults, consider "always on" soft delete and an immutable vault. Coordinate with the backup owner because deleted backup data is then kept (and billed) for the retention period.
- Baseline
- Soft delete protects backups from ransomware deletion; immutability is recommended for production vaults. · source
security_cloud.role_assignment_changes
RBAC Owner / Contributor assignment changes
- Measures
assignments· every600s·azure_graph- Rule
any change· Default severity: critical- Action
- Look up the change in the subscription's Activity Log (operation "Create role assignment") to see who made it, and confirm an approved request exists. Remove an unapproved assignment and review the principal's activity; prefer PIM-eligible assignments for Owner. Resolve the event once reviewed.
- Baseline
- Owner (8e3af657…) and Contributor (b24988ac…) assignments added or removed raise an event (the first run only records the baseline); the Activity Log names the actor. · source
security_cloud.defender_assessments
Defender for Cloud recommendations and secure score
- Measures
unhealthy_assessments(count) · every3600s·defender- Rule
warning >= 1 count· Default severity: warning- Action
- Follow the remediation steps Defender for Cloud gives for the recommendation (shown with the finding), with the owner of the resource and in a change window. Exempt it in Defender, or accept the risk here, when it does not apply.
- Baseline
- Category 'recommendation'; hidden when the entity disables recommendations. High severity maps to critical findings. · source
security_cloud.wazuh_alerts
Wazuh alerts (HIDS, FIM, CVE, CIS)
- Measures
alerts(count) · every300s·wazuh- Rule
warning >= 1 count· Default severity: warning- Action
- Open the alert in the Wazuh dashboard (agent and rule shown with the finding) and follow the rule's guidance; for a vulnerability, update the package named in the evidence through your patching process. Tune or silence a rule in Wazuh when it is noise.
- Baseline
- Rule level 7–11 → warning, 12+ → critical; vulnerabilities Critical → critical, High → warning. Wazuh agents are deployed by NinjaOne, never by the platform. Source can be disabled per entity. · source
security_cloud.platform_images
Platform container images and dependencies (CVE scan)
- Measures
critical_cves(count) · every3600s·manual- Rule
warning >= 1 count / critical >= 1 count· Default severity: warning- Action
- Upgrade to the newest release of the platform, which rebuilds the images with fixed packages; if none fixes the vulnerability yet, check whether the affected package is reachable in this deployment and accept the risk with that reason until a release does.
- Baseline
- Trivy and pip-audit run in CI; the report is posted to the API and shown as the platform self-check area. · source
Related content
- Cloud security: prerequisites and how to add resources
- Thresholds and baselines: how a default threshold is overridden