Skip to main content

Ownership & Routing

To fix violations efficiently, findings must be routed to the right owners. Compliance Engine leverages CMDB and metadata to determine who should act on each finding.

Deriving Ownership​

Ownership can be inferred from:

  • CMDB relationships – for example, application, service, or business unit linked to the asset.
  • Tags and labels – such as Owner, Team, Service, or CostCenter.
  • Account or subscription owners – where responsibility is assigned at the account level.

Policies and output objects can copy or reference these fields so that each finding carries clear ownership context.

Routing Strategies​

Common routing patterns include:

  • Assigning violations to application or service owners based on CMDB relationships.
  • Routing benchmark checks to a central security or cloud governance team.
  • Sending notifications to different teams based on environment, severity, or asset type.

Routing can be implemented via:

  • Workflows and automation in Cloudaware.
  • ITSM integrations (for example, Jira, ServiceNow, ServiceDesk).
  • Collaboration integrations (for example, Slack or Teams channels).

See Remediation & Workflows and Integrations for examples.

On this page