Understand cloud risk. Prioritize what matters.

Cloud Defense brings inventory, security posture and identity permissions into a connected view of your cloud environment. Identify potential attack paths, assess the reach of a compromised resource and prioritize remediation across AWS, Azure, Google Cloud and Kubernetes.

Connect asset visibility to risk priorities.

Inventory and posture in context

Explore connected resources, identities and security findings across supported cloud environments.

Review resource exposure alongside permissions and security configuration.
Investigate findings through the assets and relationships they affect.
Track security-relevant changes as your cloud environment evolves.

Attack paths and remediation priorities

Trace potential connections between external exposure, identity permissions and sensitive resources.

Assess risk through exposure, privilege and potential impact.
Identify shared resources where a change could disrupt multiple attack paths.
Review prioritized actions with a clear explanation of their security value.

Capabilities for cloud risk management.

Attack paths

Visualize potential routes from exposed entry points to sensitive resources. Network relationships and identity permissions provide context for understanding how access could extend across your environment.

Choke points

Find resources shared by multiple attack paths and assess where remediation could have the broadest effect. Use this context to focus changes on high-impact dependencies.

Toxic combinations

Identify resources where exposure, elevated permissions, sensitive data and vulnerability findings combine to increase risk. Investigate the contributing factors together to assess remediation priority.

Privilege escalation

Analyze permissions and trust relationships for potential privilege escalation. Review the affected identity, the relevant actions and the resources that additional access could expose.

Posture and compliance

Organize posture findings by supported compliance frameworks and control references. Use resource-level evidence to support gap analysis, remediation planning and assessment preparation.

Change over time

Track changes to exposure, permissions and security posture across collection cycles. Review history to understand how risk evolves and evaluate the effect of remediation work.

Turn cloud insight into a remediation plan.

Move from a prioritized finding to the affected resources, suggested changes and operational considerations your team needs to act.

Plan the next action

Review recommended commands, policies or infrastructure-as-code changes where supported. Each recommendation connects the issue to its security context so your team can assess and implement the appropriate fix.

Assess affected dependencies

Explore the reach of a resource and the dependencies a proposed change may affect. Consider operational impact alongside security priority when planning remediation.

Review risk over time

Use subsequent collections and finding history to review changes in exposure and posture. Keep engineering and security aligned on outstanding risks and remediation progress.

Questions

What access does Cloud Defense need?

Read-only access to the configuration of each account, granted through the cloud provider's own mechanisms. Cloud Defense does not change your resources and does not read the data inside them.

How is an attack path different from a list of findings?

A finding describes one resource. A path connects several: a machine open to the internet that can assume a privileged role that can read a sensitive database. Fixing one link in that chain can matter more than fixing many isolated findings.

Does it cover machines inside the cloud?

Cloud Defense looks at configuration and permissions. For the software running inside each machine, add the Vorpcel agent with Vulnerability Management.