Documentation menu

Docs · SecOps

Cloud Security — CSPM

Cloud Security Posture Management like Cortex and Defender for Cloud. Evaluate your cloud resource configuration against CIS-style checks, or import an existing Prowler scan — and watch the posture score.

Best-of
Palo Alto Cortex · Microsoft Defender for Cloud
Module
nexus_secops/cloud.py
Edition
Pro/Enterprise (advanced-rules gate)
API
/api/v1/cloud/scan · /cloud/findings · /cloud/posture

What it does

Cloud evaluates resource configuration against CIS-derived checks and turns failures into the same alerts and incidents as the rest of the platform. It ties cloud risk to endpoint risk in one place — the core idea behind "cloud security" in Cortex XDR and Defender for Cloud.

How to use it

1
Evaluate a config
Feed resource configuration (from your inventory or a collector) and get findings + a posture score.
bash
POST /api/v1/cloud/scan
{
  "provider": "aws", "account": "123456789012",
  "resources": [
    { "type": "s3_bucket", "id": "public-bucket", "public": true },
    { "type": "iam_user", "id": "root", "mfa": false }
  ]
}
2
Or import Prowler
Already run Prowler (the desktop Cloud Config Checker wraps it)? Import its output directly.
bash
POST /api/v1/cloud/scan   { "prowler": <prowler-json> }
3
Track posture
bash
GET /api/v1/cloud/posture     # 0-100, overall + per provider
GET /api/v1/cloud/findings

CIS-style checks

  • Public storage — a bucket reachable by the world (and unencrypted / no logging).
  • Open security group — ingress from 0.0.0.0/0 on all ports or admin ports (22/3389).
  • Identity — root without MFA, root access keys, IAM wildcard *:*.
  • Database — publicly accessible or unencrypted RDS.
  • Compute / account — unencrypted volumes, audit logging (CloudTrail) disabled.

High/critical findings emit a cloud_finding event → alert NEXUS-CLOUD-001 with the CIS reference and a remediation.

How it feeds the pipeline

Cloud findings join the same alert stream, so a misconfiguration sits next to endpoint and network risk. The AI includes them when it triages, and SOAR's PB-CLOUD-NOTIFY alerts the cloud team on the serious ones.

Tips

  • Re-scan after every infrastructure change to watch the posture score recover.
  • Findings are de-duplicated per (provider, account, check, resource) — no noise on repeat scans.
  • Only high/critical findings alert by default; everything is still listed in /cloud/findings.
Your config, your checks. CSPM evaluates the configuration you provide (from inventory or Prowler). The checks are real CIS-derived rules — nothing is assumed or invented.