Verificações de segurança de nuvem
O módulo security_cloud tem 8 verificações. Postura de nuvem (Azure Resource Graph, Defender for Cloud) e descobertas opcionais do Wazuh, somente leitura. As verificações do Resource Graph examinam apenas o resource_id do recurso (um recurso, um grupo de recursos ou uma assinatura inteira); params.scope = resource torna esse atributo obrigatório e params.scope = all examina todas as assinaturas que a identidade consegue ler. O Defender for Cloud e o Wazuh são ativados separadamente (opções de recurso security.defender, security.wazuh); as recomendações podem ser ocultadas (security.recommendations).
Esta página é gerada a partir do catálogo de verificações do produto quando a documentação é compilada, portanto as regras, os intervalos e as severidades padrão sempre correspondem à versão que você está lendo. Os limites são valores padrão; entidades e recursos podem substituí-los.
| Verificação | Intervalo | Gravidade padrão | Regra |
|---|---|---|---|
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 |
Verificações
security_cloud.nsg_exposed_ports
Management ports open to the Internet
- Métrica
exposed_rules(count) · a cada900s·azure_graph- Regra
warning >= 1 count / critical >= 1 count· Gravidade padrão: critical- Ação
- 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.
- Linha de base
- 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. · fonte
security_cloud.public_storage
Storage accounts allowing anonymous blob access or weak transport
- Métrica
posture· a cada3600s·azure_graph- Regra
publicBlob = false, httpsOnly = true, minTls = TLS1_2· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- CIS Azure Foundations 3.x. An unset allowBlobPublicAccess is reported for review (older accounts may still allow it). · fonte
security_cloud.keyvault_protection
Key Vault purge protection and soft delete
- Métrica
posture· a cada3600s·azure_graph- Regra
purge = true, softDelete = true· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- CIS Azure Foundations 8.x. Soft delete can no longer be turned off on new vaults; purge protection is off unless enabled. · fonte
security_cloud.rsv_protection
Recovery Services Vault soft delete and immutability
- Métrica
posture· a cada3600s·azure_graph- Regra
softDelete = Enabled,AlwaysON· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- Soft delete protects backups from ransomware deletion; immutability is recommended for production vaults. · fonte
security_cloud.role_assignment_changes
RBAC Owner / Contributor assignment changes
- Métrica
assignments· a cada600s·azure_graph- Regra
any change· Gravidade padrão: critical- Ação
- 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.
- Linha de base
- 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. · fonte
security_cloud.defender_assessments
Defender for Cloud recommendations and secure score
- Métrica
unhealthy_assessments(count) · a cada3600s·defender- Regra
warning >= 1 count· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- Category 'recommendation'; hidden when the entity disables recommendations. High severity maps to critical findings. · fonte
security_cloud.wazuh_alerts
Wazuh alerts (HIDS, FIM, CVE, CIS)
- Métrica
alerts(count) · a cada300s·wazuh- Regra
warning >= 1 count· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- 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. · fonte
security_cloud.platform_images
Platform container images and dependencies (CVE scan)
- Métrica
critical_cves(count) · a cada3600s·manual- Regra
warning >= 1 count / critical >= 1 count· Gravidade padrão: warning- Ação
- 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.
- Linha de base
- Trivy and pip-audit run in CI; the report is posted to the API and shown as the platform self-check area. · fonte
Conteúdo relacionado
- Segurança de nuvem: pré-requisitos e como adicionar recursos
- Limites e linhas de base: como substituir um limite padrão