Book a demo
All platforms

OCI assurance across tenancies and compartments

Statepoint.Build + Statepoint.Operate

Carry OCI landing zone intent across compartments, identities, networks and workloads.

Statepoint connects approved OCI architecture, ownership, policy and cost intent with current evidence across tenancies, compartments, IAM, networks and workloads. Assurance Intelligence explains material differences and recommends action while people retain approval of every response.

Explore the OCI lifecycle Review OCI context

The daily OCI engineering reality

An OCI issue rarely stays within one compartment or one control boundary.

A production path can cross tenancy policy, a dynamic group, network security boundaries, routes, vaults and workloads. Statepoint connects those relationships to the approved architecture, responsible owner and current evidence so teams can decide and verify the response.

Govern tenancy, compartment and workload intent before delivery

Explain effective access across IAM and network boundaries

Tie human-approved responses to current OCI evidence

One governed OCI lifecycle

Carry tenancy decisions into the evidence engineers use every day.

Statepoint.Build preserves tenancy, compartment and architecture intent. Statepoint.Operate connects current IAM, network, workload and cost evidence. Statepoint Assurance Intelligence analyses it and recommends accountable action for human approval and verification.

01Statepoint.Build

Build governed OCI intent

Statepoint.Build establishes tenancy structure, compartment ownership, architecture, dependencies, controls and cost boundaries before approved infrastructure is delivered.

02Statepoint.Operate

Observe the OCI estate

Statepoint.Operate connects current tenancy, IAM, network, workload, software and cost evidence to the intent behind the environment.

03Assurance Intelligence

Explain and recommend

Statepoint Assurance Intelligence analyses material differences between approved intent and operating evidence, then recommends an explainable response.

04Human approval

Keep people in control

The accountable owner reviews the evidence and recommendation, then approves, modifies or rejects the proposed response.

05Operate verification

Verify the outcome

Statepoint.Operate reassesses the current OCI estate and records whether the approved response produced the intended result.

Real OCI operating paths

Compartment policy, workload identity and network paths need one explanation.

Statepoint connects tenancy and compartment context, effective IAM policy, reachable network paths and workload evidence without flattening the OCI detail that explains the outcome.

Tenancies and compartments

Relate tenancy and compartment boundaries to the approved owner, workload purpose, security expectations and financial responsibility.

Effective access

Understand users, groups, dynamic groups and policies as connected access paths rather than isolated IAM objects.

Network reachability

Connect VCNs, routes, gateways, security lists and network security groups to show which path exists and whether it was intended.

Workloads and Oracle Kubernetes Engine

Evaluate OCI identity and network foundations together with OKE, workload, software and operating evidence.

Connected OCI coverage

The context engineers need to decide and verify.

Statepoint.Build + Statepoint.Operate

Architecture and delivery

  • Tenancy, compartment and workload ownership
  • Approved architecture and service dependencies
  • Security, policy and financial boundaries
  • Cost awareness before provisioning
  • Versioned infrastructure delivery artifacts

Identity, network and workloads

  • Tenancy, compartment and resource relationships
  • Users, groups, dynamic groups, policies and effective access
  • VCNs, routes, gateways, security lists and network security groups
  • Compute, Vault, OKE and workload evidence
  • Container image inventory and digest-linked software evidence

Decision and verification

  • Risk and cost recommendations with context
  • Accountable ownership for every response
  • Human approval preserved with the evidence
  • Current OCI estate reassessed after action
  • Outcome and residual exposure recorded

Coverage noteOCI coverage spans Statepoint.Build and Statepoint.Operate. Available design components, evidence sources and assurance checks remain explicit during evaluation so teams can confirm the capability relevant to their estate.

DeploymentInfrastructure coverage describes what Statepoint observes, not where Statepoint is hosted. Statepoint runs as a dedicated instance in your nominated AWS account or Azure subscription. Review deployment and security.

ConnectionOCI resources connect through cloud provider APIs. Statepoint Scout is used only for on-premises collection and is not part of this cloud connection path.

Continue exploring

Next: Kubernetes

Explore Kubernetes

Oracle Cloud Infrastructure assurance

Govern OCI across compartments.
Verify what changed.

Connect tenancy intent, IAM, network paths, workloads and controlled change in one explainable operating record.

Book a demo