Vérifications de la sécurité du cloud
Le module security_cloud compte 8 vérifications. Posture de sécurité du cloud (Azure Resource Graph, Defender for Cloud) et constats Wazuh facultatifs, en lecture seule. Les vérifications Resource Graph examinent uniquement le resource_id de la ressource (une ressource, un groupe de ressources ou un abonnement entier) ; params.scope = resource rend cet attribut obligatoire et params.scope = all examine tous les abonnements que l'identité peut lire. Defender for Cloud et Wazuh s'activent séparément (fonctionnalités security.defender, security.wazuh) ; les recommandations peuvent être masquées (security.recommendations).
Cette page est générée à partir du catalogue des vérifications du produit lors de la génération de la documentation : les règles, les intervalles et les gravités par défaut correspondent donc toujours à la version que vous consultez. Les seuils sont des valeurs par défaut ; les entités et les ressources peuvent les remplacer.
| Contrôle | Intervalle | Gravité par défaut | Règle |
|---|---|---|---|
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 |
Vérifications
security_cloud.nsg_exposed_ports
Management ports open to the Internet
- Mesure
exposed_rules(count) · toutes les900s·azure_graph- Règle
warning >= 1 count / critical >= 1 count· Gravité par défaut: 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.
- Base de référence
- 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
- Mesure
posture· toutes les3600s·azure_graph- Règle
publicBlob = false, httpsOnly = true, minTls = TLS1_2· Gravité par défaut: 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.
- Base de référence
- 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
- Mesure
posture· toutes les3600s·azure_graph- Règle
purge = true, softDelete = true· Gravité par défaut: 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.
- Base de référence
- 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
- Mesure
posture· toutes les3600s·azure_graph- Règle
softDelete = Enabled,AlwaysON· Gravité par défaut: 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.
- Base de référence
- Soft delete protects backups from ransomware deletion; immutability is recommended for production vaults. · source
security_cloud.role_assignment_changes
RBAC Owner / Contributor assignment changes
- Mesure
assignments· toutes les600s·azure_graph- Règle
any change· Gravité par défaut: 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.
- Base de référence
- 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
- Mesure
unhealthy_assessments(count) · toutes les3600s·defender- Règle
warning >= 1 count· Gravité par défaut: 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.
- Base de référence
- 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)
- Mesure
alerts(count) · toutes les300s·wazuh- Règle
warning >= 1 count· Gravité par défaut: 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.
- Base de référence
- 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)
- Mesure
critical_cves(count) · toutes les3600s·manual- Règle
warning >= 1 count / critical >= 1 count· Gravité par défaut: 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.
- Base de référence
- Trivy and pip-audit run in CI; the report is posted to the API and shown as the platform self-check area. · source
Contenu connexe
- Sécurité du cloud : prérequis et ajout de ressources
- Seuils et bases de référence : comment remplacer un seuil par défaut