Skip to main content
Version: 0.4 · current

Cloud security

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansPro · EnterpriseDeploymentSelf-hosted

The cloud security module checks the posture of your Azure estate and gathers the findings of the security tools you already run: management ports open to the Internet, storage and vaults without protection, changes in Owner and Contributor assignments, Defender for Cloud assessments, Wazuh alerts and vulnerabilities, and the vulnerabilities of Excubius's own images. It only detects; Excubius never changes a resource.

What it monitors​

AreaChecksWhy it matters
Network exposureNetwork security group rules that allow 22, 3389, 1433, 5432 or 5985 and 5986 from the Internet, also inside port ranges and prefix listsA management port open to the Internet is scanned within minutes
StorageStorage accounts that allow anonymous blob access, do not require secure transfer, or accept TLS below 1.2Data readable by anyone, or sent in the clear
VaultsKey vaults without purge protection or soft delete; Recovery Services vaults without soft deleteWithout them, one deletion destroys secrets or backups for good, a common ransomware tactic
AccessOwner or Contributor role assignments added or removedUnreviewed privilege grants in your subscriptions
Defender for CloudUnhealthy assessments, one per assessment and resource. High severity is a critical finding; medium and low are recommendations, with Defender's remediation text as the suggested actionBrings Microsoft's own posture assessment next to everything else
WazuhAlerts of the last 24 hours at level 7 or above, one per agent and rule (12 and above critical, 7 to 11 a warning), plus critical and high vulnerability statesHost intrusion detection, file integrity and CVE findings, attached to the matching host
Excubius itselfCritical vulnerabilities in the platform's own container images, from Trivy reportsThe monitoring platform should not be the weak point

Findings feed the cloud area of the security score; recommendations count only while they are shown. A change in role assignments is an event: it is reviewed and resolved by hand. How findings, accepted risks and the score work: Security posture.

Every check, with its rule, cause and action, is in the reference for cloud security checks.

Before you begin​

  • The feature switches. A super administrator sets them in Settings › Instance:

    SwitchEffect
    securityThis module, identity security and SQL Server security, the Security posture page and the score
    security.defenderCollects Defender for Cloud assessments. Off by default
    security.wazuhCollects Wazuh alerts and vulnerabilities. Off by default
    security.recommendationsShows Defender's medium and low assessments as recommendations, counts them in the score and lists them in the inbox. Off, only high-severity findings remain

    Switching Defender or Wazuh off stops collecting; findings already raised stay open until someone resolves them.

  • An Azure identity: the server's managed identity, or an Azure service principal credential. With a service principal, the subscriptions option limits the subscriptions; otherwise AZURE_SUBSCRIPTION_IDS does, or else every subscription the identity can read.

  • Azure roles on the subscriptions:

    RoleRole IDFor
    Readeracdd72a7-3385-48ef-bd42-f606fba81ae7Resource Graph checks and role assignments
    Security Reader39bc4728-0917-49c7-9d2c-d95423bc2eb4Defender for Cloud assessments
  • For Wazuh, a read-only Wazuh user stored as an HTTP user and password credential, with read access to the wazuh-alerts-* and wazuh-states-vulnerabilities-* indices and, optionally, agents:read on the manager API. Set indexer_url, and api_url for agent details, in the check's parameters. The option verify_tls of the credential is true by default. Excubius sends Wazuh only searches and the manager's sign-in call; anything else is refused in code. Wazuh agents are deployed by your own tooling, never by Excubius.

  • For the platform images, a super administrator posts Trivy reports: run trivy image --format json <image> and post the result to POST /api/v1/security/platform-report. The latest report per image counts.

Add a resource​

  • Platform-wide checks (role assignments, Defender for Cloud, Wazuh, platform images) run on a Monitoring platform itself resource. Add one on the root entity if you do not have one yet.
  • Posture checks run on a resource of the matching type: an Azure network resource, storage account, key vault or Recovery Services vault. They look only at the resource's resource_id, which can be one resource, a resource group or a whole subscription (/subscriptions/<id>). One resource scoped to a subscription covers every matching resource in it.
  • Resources that the Azure Monitor source added get the posture checks when an editor calls POST /api/v1/resources/{id}/checks with an empty check_ids list.

Defender assessments and Wazuh findings are attached to the inventory resource that matches them, by Azure resource ID or by the agent's name, host, IP or machine name; otherwise to the platform resource. See Add a resource.

Next steps​