Cloud security
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
| Area | Checks | Why it matters |
|---|---|---|
| Network exposure | Network security group rules that allow 22, 3389, 1433, 5432 or 5985 and 5986 from the Internet, also inside port ranges and prefix lists | A management port open to the Internet is scanned within minutes |
| Storage | Storage accounts that allow anonymous blob access, do not require secure transfer, or accept TLS below 1.2 | Data readable by anyone, or sent in the clear |
| Vaults | Key vaults without purge protection or soft delete; Recovery Services vaults without soft delete | Without them, one deletion destroys secrets or backups for good, a common ransomware tactic |
| Access | Owner or Contributor role assignments added or removed | Unreviewed privilege grants in your subscriptions |
| Defender for Cloud | Unhealthy 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 action | Brings Microsoft's own posture assessment next to everything else |
| Wazuh | Alerts 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 states | Host intrusion detection, file integrity and CVE findings, attached to the matching host |
| Excubius itself | Critical vulnerabilities in the platform's own container images, from Trivy reports | The 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:
Switch Effect 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
subscriptionsoption limits the subscriptions; otherwiseAZURE_SUBSCRIPTION_IDSdoes, or else every subscription the identity can read. -
Azure roles on the subscriptions:
Role Role ID For Reader acdd72a7-3385-48ef-bd42-f606fba81ae7Resource Graph checks and role assignments Security Reader 39bc4728-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-*andwazuh-states-vulnerabilities-*indices and, optionally,agents:readon the manager API. Setindexer_url, andapi_urlfor agent details, in the check's parameters. The optionverify_tlsof the credential istrueby 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 toPOST /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}/checkswith an emptycheck_idslist.
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.