Loading…
Loading documentation...
Query security events with KQL in Cloud SIEM, run automated SOAR playbooks, scan CSPM and EASM posture and classify sensitive data.
Commands checked on 2026-11-12 with SAU Cloud SIEM & Security Posture v1.7, KQL, sau CLI 0.2.0.
Your team will operate a unified, first-party SecOps and Data Governance control plane across Operations > Cloud SIEM & SOAR (/dashboard/sentinel) and Operations > Security posture & DLP (/dashboard/defender-purview), running Kusto-style (KQL) threat-hunting queries across platform and network telemetry (5 GiB/mo SIEM ingestion included free), triggering automated SOAR containment playbooks and AI incident triage, continuously scoring CSPM / CWPP posture, scanning external domains with EASM, and classifying sensitive PII / PCI / HIPAA payloads with Data Loss Prevention (DLP).
/dashboard.cloud:read and cloud:write scopes (Account settings > API keys at /account/api-keys), or the Cloud SIEM Responder RBAC role in Operations > Resource manager & settings (/dashboard/resource-manager).First, confirm your Resource Manager diagnostic stream forwards control-plane, Key Vault, and network events into Cloud SIEM (sendToSentinel: true is enabled automatically when you run sau monitor diagnostics-create).
Open Operations > Cloud SIEM & SOAR (/dashboard/sentinel) or run KQL queries straight from your terminal to hunt for high-severity events, anomalous authentication spikes, or blocked perimeter probes:
# Inspect your Cloud SIEM workspace, open incidents, and active playbooks
sau sentinel show
# Execute KQL threat-hunting queries
sau sentinel kql "SecurityEvent | where Severity in ('HIGH', 'CRITICAL') | sort by Timestamp desc | limit 25"
sau sentinel kql "AuditLog | where OperationName contains 'vault' or OperationName contains 'ssh' | limit 20"
Turn repeatable detection patterns into zero-touch response playbooks (CREATE_INCIDENT_ONLY, BLOCK_SOURCE_IP, or WEBHOOK_POST):
# Automatically block attacking source IPs on CRITICAL detections
sau sentinel playbook-create auto-block-critical-scanners \
--severity CRITICAL \
--action BLOCK_SOURCE_IP
# Notify your on-call webhook on HIGH severity incidents
sau sentinel playbook-create page-secops-oncall \
--severity HIGH \
--action WEBHOOK_POST \
--webhook "https://hooks.example.com/services/secops-alerts"
# Run automated AI root-cause & MITRE ATT&CK triage on an incident ID
sau sentinel triage YOUR_INCIDENT_ID
The AI triage summary correlates related events across compute, network, and identity planes, maps the technique to MITRE ATT&CK tactics, and recommends concrete containment actions without auto-banning verified customer or search-crawler traffic.
Open Operations > Security posture & DLP (/dashboard/defender-purview) to audit your infrastructure against CIS and zero-trust benchmarks—checking for unencrypted volumes, missing CanNotDelete locks, wide-open firewall rules, or unrotated keys—and scan your public domains for unintended external exposure:
# View your current Cloud Secure Score, CSPM findings, and DLP labels
sau security posture
# Trigger a fresh live CSPM posture evaluation across your fleet
sau security scan
# Run an External Attack Surface Management (EASM) scan against your public domain
sau security easm-scan app.example.com
On the Data Governance & DLP tab of Operations > Security posture & DLP (/dashboard/defender-purview) (or via POST /api/v1/defender-purview), run deterministic pattern + structural classifiers over sample payloads, storage containers, or database schemas to detect credit-card PANs (PCI-DSS), Social Security / national ID numbers, health identifiers (HIPAA), and leaked API credentials, then bind sensitivity labels (PUBLIC, INTERNAL, CONFIDENTIAL, HIGHLY_CONFIDENTIAL_DKE) with Double-Key Encryption (DKE) policies.
curl -fsSL -X POST "https://serversareup.com/api/v1/defender-purview" \
-H "Authorization: Bearer sau_your_token_here" \
-H "Content-Type: application/json" \
-d '{
"action": "classify-dlp",
"assetUri": "/providers/SAU.Storage/containers/customer-exports",
"sampleText": "Customer billing export check for PCI and PII exposure"
}' | jq .
Confirm your Cloud Secure Score updates after remediating a finding (such as adding a CanNotDelete lock or closing an unused port), and verify your SOAR playbook appears as ENABLED:
sau sentinel show -o json | jq '{
openIncidents: (.incidents | length),
activePlaybooks: [.playbooks[] | {name, minSeverity, actionType}]
}'
sau security posture -o json | jq '.secureScore'
WEBHOOK_POST SOAR playbook rejects an internal IP URL. Webhook sinks enforce strict SSRF protection and require a public routable https:// endpoint; internal 127.0.0.1 or RFC1918 destinations are refused.--severity INFO on a WEBHOOK_POST playbook. Informational audit events fire on routine logins and deployments. Reserve WEBHOOK_POST paging for HIGH and CRITICAL severities, and keep BLOCK_SOURCE_IP scoped to CRITICAL high-confidence attack rules./dashboard/defender-purview—missing 2FA/Passkeys, unlocked production Resource Groups, or unencrypted BYO backups also factor into your score./dashboard/sentinel) at the start of every engineering shift.sau security easm-scan <domain> every time you launch a new subdomain or microservice to verify TLS grades, CAA/DMARC records, and zero shadow ports./dashboard/blob-storage) for 1-year forensic retention.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.