Configuration posture
See failed controls across clouds in one normalised view without losing the provider evidence behind them.
← Exposure ManagementAvailableCSPM · Built on Skyreach Orion
Understand cloud misconfiguration in the context of what it exposes.
CSPM continuously aligns configuration evidence from AWS, Microsoft Azure and Google Cloud to Orion's shared ontology. Instead of stopping at a failed control, it connects the affected resource to identities, networks, data and workloads so teams can see whether the weakness creates meaningful exposure.
Evidence in
What Orion connects
The exact coverage depends on the integrations and authorised evidence available in your environment. Every record retains where it came from.
Example sources
- AWS accounts and organisations
- Azure subscriptions and management groups
- Google Cloud organisations and projects
- Cloud configuration and security services
- Kubernetes clusters and cloud-managed services
- Imported findings from existing security tools
What the ontology models
- Cloud accounts, subscriptions and projects
- Resources, regions and organisational scope
- Configurations, policies and security controls
- Public endpoints and network relationships
- Workload and service identities
- Findings, evidence and ownership
Intelligence out
What visibility and insight you gain
The module uses the shared Orion model, so its findings can be understood through evidence collected by other security disciplines.
Exposure-aware priority
Raise the importance of a weakness when the resource is public, reachable, privileged or connected to sensitive data.
Cross-cloud consistency
Apply a common risk language across AWS, Azure and Google Cloud while retaining provider-specific detail.
Remediation context
Show the affected resource, contributing evidence, surrounding relationships and the change likely to reduce risk.
Connected analysis
An example of the exposure Orion can reveal
This is an illustrative relationship chain, not a claim that every path represents a confirmed compromise. Orion preserves evidence and confidence so teams can validate what is effective.
Public cloud endpoint→Permissive configuration→Workload identity→Sensitive resource
Risks made visible
What the module is looking for
- Public storage, databases, APIs and management interfaces
- Missing or weak encryption, logging and protective controls
- Overly permissive resource policies and trust relationships
- Secrets and credentials with unsafe lifecycle settings
- Cloud resources outside expected regions, ownership or governance
- Combinations of configuration, identity and network weakness
Questions it helps answer
Move from findings to decisions
- Which cloud findings create an internet-to-data path?
- Which critical resources have weak controls and no clear owner?
- Where does the same control fail across multiple providers?
- Which single remediation would break the most exposure paths?
Why Orion matters
This discipline does not operate in isolation
Cloud Security Posture Management contributes its evidence to the same ontology used by the rest of Exposure Management. That allows a finding to inherit network reachability, identity privilege, data sensitivity, software, application and business context where those facts exist.
See the complete Exposure Management productCSPM evidence+Shared ontology+Cross-domain context=Prioritised exposure
See what this means in your environment
Tell us which sources you use and the questions your teams struggle to answer today.