Cloudryption Decision OS

The decision and control layer for cloud security

Cloudryption turns cloud security evidence into explicit objectives, competing remediation strategies, governed execution, verified outcomes, and durable decision memory.

Evidence

Risk, attack graph, identity, data, runtime, and cloud-state signals establish the current security state.

Decide & Govern

Decision Objectives define the outcome. Strategy Arena compares alternatives. Decision Governor decides whether execution authority is safe.

Act & Prove

Approved actions execute through Action V2, then post-change evidence verifies the actual result and creates Decision Proof.

EvidenceObserved security state
StrategyCounterfactual action bundles
GovernancePolicy, safety, approval
ProofPredicted vs actual outcome

Cloud security visibility is only the beginning

CSPM, CIEM, DSPM, CWPP, provider-native security services, and attack-path systems can all produce valuable evidence. The harder operating problem begins after the evidence exists: what outcome matters, which action should be selected, whether that action is safe to execute, and whether it actually reduced risk.

Cloudryption Decision OS is designed for that decision lifecycle.

Decision OS operating model

1. Security Evidence

Risk findings, controls, attack paths, reachability, identities, permissions, sensitive data, runtime threat and behavior, and cloud-state context feed a canonical, truth-labelled security state.

2. Current Security State

Cloudryption establishes the decision baseline: what is observed now, what is reachable, which assets matter, and where objective pressure exists.

3. Decision Objective

Define the desired security outcome — for example reducing paths to crown jewels, containing privileged exposure, or reducing reachable critical workloads — together with constraints and targets.

4. Strategy Arena

Evaluate competing counterfactual action bundles rather than presenting one opaque recommendation. Compare expected security impact before committing to change.

5. Decision Governor

Apply policy, reliability, blast-radius, rollback, provider-safety, and approval constraints. Execution authority is earned, not assumed.

6. Controlled Action

Approved, fully bound actions execute through the canonical Action V2 remediation workflow. Unsupported or incomplete recommendations cannot silently become executable actions.

7. Post-change Verification

Execution is not verification. Cloudryption recalculates execution-bound post-change evidence against the original baseline.

8. Decision Proof & Memory

Predicted outcomes are compared with actual verified outcomes. The lifecycle, evidence, action, and proof become replayable decision memory for governance and auditability.

Four planes, one operating system

Evidence Plane

Risk, Attack Graph, Identity, Data, Runtime, findings, controls, and cloud context.

Decision Plane

Current Security State, Decision Objectives, Strategy Arena, and Decision Governor.

Action & Proof Plane

ActionContract, approval, Action V2 execution, post-change evidence, Decision Proof, and Decision Memory.

How Cloudryption fits the security stack

Cloudryption can consume evidence from its own security engines and from the surrounding cloud-security ecosystem. Its role is not simply to add another finding queue. It is the security decision and control layer above the evidence: converting current state into governed action and verified outcome.

See the Decision OS lifecycle in your environment

Walk through a real security objective from evidence and strategy selection to governed action, verification, and proof.