Skip to main content

Findings & Output Objects

Findings and output objects are how Compliance Engine represents the result of policy evaluations. They form the core evidence used for dashboards, reports, and workflows.

Output Object Types​

Compliance Engine primarily uses two output object types:

  • CloudAware Policy Violation – captures violations for most Cloudaware and custom policies.
  • CloudAware Benchmark Check – captures evaluation results for CIS benchmark policies and similar packs.

Each output object is:

  • Linked to the policy that produced it.
  • Linked to the asset (CMDB object) being evaluated.
  • Populated with status, severity, timestamps, and evidence fields.

These objects behave like any other Cloudaware objects: they can be queried, reported on, and used in workflows and integrations.

Why Output Objects Matter​

Using persistent output objects instead of ephemeral scan results allows you to:

  • Track historical posture and reconstruct past states.
  • Build dashboards that show trends over time.
  • Measure remediation performance (for example, MTTR, violation age).
  • Drive ticketing, automation, and notifications from a consistent data model.

The guides below describe the schema, ownership and routing patterns, and export options in more detail.

Schema​

Understand the core fields, statuses, timestamps, evidence, and ownership context stored on Compliance Engine findings.

Ownership & Routing​

Route findings to the right application, service, platform, or security owners using CMDB relationships and metadata.

Exports​

Plan exports for analytics, ticketing, SIEM/SOAR, audit evidence, and downstream reporting workflows.

On this page