Data Flow

From cloud evidence to governed, verified decisions

This page explains how customer-authorized evidence becomes Current Security State, a governed decision, controlled action, verified outcome, Decision Proof, and durable Decision Memory.

1. Connect

The customer authorizes scoped, read-only evidence collection for selected cloud environments.

2. Collect evidence

Cloudryption collects authorized metadata about assets, identities, permissions, workloads, vulnerabilities, data posture, network reachability, security findings, and relationships.

3. Normalize

Provider-specific evidence is transformed into a common, evidence-aware model with provenance and confidence.

4. Build Current Security State

Assets, identities, workloads, data stores, networks, policies, findings, and attack paths become a connected security state.

5. Define the Decision Objective

The desired outcome, target, constraints, and reduction goal are made explicit before action selection.

6. Compare strategies

Strategy Arena evaluates competing FixSets and simulates expected outcomes against supported security-state metrics.

7. Govern authority

Decision Governor applies policy, RBAC, reliability, blast radius, rollback, provider safety, and approval requirements.

8. Plan, ticket, and assign

The approved strategy becomes a remediation plan with accountable owners and work issued through Cloudryption Native Tickets, Jira, or ServiceNow.

9. Execute and track

Approved actions progress through explicit execution states. A completed task is recorded separately from verification.

10. Verify post-change evidence

Cloudryption re-evaluates the affected security state and records the actual outcome after execution.

11. Create Decision Proof

Predicted and verified actual outcomes are compared without manufacturing after-values.

12. Preserve Decision Memory

Evidence, objective, alternatives, approval, execution, verification, and proof remain replayable for governance and audit.

Data minimization

Cloudryption focuses on control-plane metadata and risk context. Standard operation does not require production data records, source code, secrets, or broad application logs.

Data outputs

  • Normalized cloud asset inventory and evidence provenance.
  • Current Security State, decision-graph nodes, edges, attack paths, and exposure chains.
  • Decision Objectives, competing strategies, FixSets, confidence, and simulated expected outcomes.
  • Remediation plans, approval state, accountable owners, tickets, execution status, and exceptions.
  • Post-change evidence, verified actual outcomes, residual exposure, and Decision Proof.
  • Decision Memory plus executive, technical, HLD, and LLD reports.

Retention and deletion

Customer data is retained according to the data-retention policy and the customer agreement. Deletion and export requests are supported through the support contact.

Need this in your enterprise security review?

Cloudryption can provide a security packet, technical walkthrough, and pilot evidence pack for your evaluation process.