Cloud Agents

Protect cloud control planes and resources at scale.

Cloud Agents protect AWS, Azure, GCP, and hybrid environments. They monitor cloud assets, IAM changes, resource configurations, control plane activity, and exposed services. They detect misconfigurations, privilege drift, abnormal workloads, and cloud-native attack paths.

Request early access →

The Ollandi defense loop

Every agent follows the same cycle, producing auditable, coordinated response.

01

Observe

Ingest domain-specific signals in real time with full telemetry fidelity.

02

Reason

Correlate local evidence with the shared threat model and adjacent agents.

03

Validate

Check policy boundaries, blast radius, and consensus before acting.

04

Act

Execute bounded, reversible actions through approved control interfaces.

05

Evidence

Record every observation, decision, and action in an auditable bundle.

What it protects

  • AWS, Azure, and GCP accounts
  • IAM policies, roles, and bindings
  • Compute, storage, and database resources
  • Network ACLs and security groups
  • Serverless and container workloads

What it monitors

  • CloudTrail, CloudWatch, and equivalent audit logs
  • IAM policy and role changes
  • Resource creation, deletion, and modification
  • Exposed storage buckets and public endpoints
  • Cost and usage anomalies

What it detects

  • IAM privilege escalation and policy misconfiguration
  • Publicly exposed resources and data leakage
  • Unauthorized resource provisioning
  • Cloud credential abuse
  • Lateral movement through cloud roles

What it can do

  • Remediate misconfigurations through approved APIs
  • Restrict overly permissive IAM bindings
  • Isolate compromised resources into quarantine groups
  • Trigger evidence snapshots of cloud state
  • Coordinate with Identity and Network agents on cross-domain events

What evidence it generates

  • Cloud resource state snapshot before and after action
  • IAM policy diff and change history
  • API call timeline with principal attribution
  • Cross-agent consensus record
  • Rollback plan and safety check results

One working agent experience

See how an cloud agent moves through the defense loop on a real incident.

1

Observe

S3 bucket data-exports-prod changed from private to public-read.

2

Reason

No approved change ticket; bucket contains sensitive telemetry; public exposure risk is critical.

3

Validate

Validate blast radius with Network Agent; confirm no legitimate public access pattern.

4

Act

Revert bucket ACL, notify owner, create evidence snapshot.

5

Evidence

ACL change history, blast-radius assessment, and remediation action logged.

Part of a coordinated defense

Cloud Agents share resource and IAM context with Identity, Network, and Runtime agents so cross-domain attacks are tracked as a single coordinated incident.

Identity
Cloud
Endpoint
Network
Runtime