Skip to main content
Liongard compliance metrics let you link automated configuration audit data directly to your compliance checks. Instead of manually assessing configuration-based requirements, you can define rules that automatically evaluate Liongard metric values and update compliance check statuses in real time.
This feature requires an active Liongard integration. Set up Liongard first if you haven’t already.

​
Accessing Compliance Metrics

Navigate to Settings > Compliance and click the Metrics tab. This page shows all configuration audit metrics synced from your Liongard instance. If no Liongard integration is connected, you will see a prompt to set one up from the Integrations page.

​
Browsing Metrics

The metrics page offers two views:
Groups data by metric name. Each row shows:
ColumnDescription
MetricThe configuration audit data point name
InspectorThe Liongard inspector type (e.g., Windows Workstation, Active Directory)
DevicesNumber of devices evaluated for this metric
StatusPass, fail, and warning counts across all devices
Last EvaluatedWhen Liongard last evaluated this metric
Click any metric row to open a detail panel showing all devices with their individual values and statuses.
Use the search bar to find specific metrics or devices, and the filter dropdowns to narrow by inspector type or company.

​
Summary Strip

At the top of the metrics page, a summary strip shows:
  • Total passing, failing, and warning counts across all metrics
  • Number of metrics linked to compliance checks
  • Last synced timestamp

​
Creating a Compliance Check from a Metric

1

Find the Metric

Browse or search for the metric you want to track in compliance. Click the metric row to open the detail panel.
2

Click Create Compliance Check

In the detail panel, click Create Compliance Check. This button only appears for metrics not yet linked to a check. Already-linked metrics show a Linked to Compliance badge.
3

Configure the Check

Fill in the compliance check details:
FieldDescription
Check TitlePre-filled with the metric name. Edit as needed.
DescriptionPre-filled with metric and inspector details
Status ListSelect which status list to use for pass/fail options
Compliance GroupOptionally assign the check to a compliance group
Auto-updateEnable to have the check status update automatically when Liongard syncs
4

Choose Evaluation Mode

When auto-update is enabled, choose how the check status is determined:
  • Use Liongard status - Directly uses the pass/fail/warning status from Liongard
  • Custom rules - Define your own rules based on the metric value (see below)
5

Create

Click Create Compliance Check. The metric is now linked and will show a Linked badge in the metrics table.

​
Custom Rules

Custom rules let you define exactly when a metric should pass or fail based on its value. This is useful when Liongard’s native pass/fail does not match your compliance requirements, or when you need threshold-based evaluation.

​
How Rules Work

  • Rules are evaluated in order from top to bottom
  • The first matching rule wins and determines the status
  • If no rules match, the default result applies (configurable as pass or fail)

​
Available Operators

OperatorDescriptionExample
Greater thanNumeric comparisonValue > 90 = Pass
Greater or equalNumeric comparisonValue >= 100 = Fail
Less thanNumeric comparisonValue < 10 = Pass
Less or equalNumeric comparisonValue <= 0 = Fail
EqualsExact string or numeric matchValue = “Enabled” = Pass
Not equalsDoes not matchValue != “Disabled” = Pass
ContainsSubstring matchValue contains “error” = Fail
Does not containSubstring absenceValue does not contain “warning” = Pass
Is emptyNo value presentEmpty = Fail
Is not emptyAny value presentNot empty = Pass

​
Building Rules

1

Select Custom Rules

In the Create Compliance Check dialog, set the evaluation mode to Custom rules.
2

Add a Rule

Click Add Rule. Each rule has three parts:
  1. Operator - How to compare the value (e.g., Greater than, Contains)
  2. Threshold - The value to compare against (not needed for Is empty/Is not empty)
  3. Result - Pass or Fail when the rule matches
3

Add More Rules

Add additional rules as needed. Rules are evaluated top to bottom, so place your most specific conditions first.
4

Set Default Result

Choose what happens when no rules match: Pass or Fail. This defaults to Fail for safety.
For numeric metrics like password length or patch percentage, use Greater than / Less than operators. For text metrics like “Enabled” or “Disabled”, use Equals or Contains.

​
Example: Password Policy Check

To create a rule that fails when the minimum password length is below 12:
  1. Add Rule: Less than 12 = Fail
  2. Default result: Pass
This means any value below 12 fails, and anything 12 or above passes.

​
Example: Feature Status Check

To verify a security feature is enabled:
  1. Add Rule: Equals Enabled = Pass
  2. Add Rule: Equals True = Pass
  3. Default result: Fail
Any value other than “Enabled” or “True” will fail.

​
How Auto-Sync Works

When a metric-linked compliance check has auto-update enabled, the background sync handles updates automatically:
  1. Liongard syncs metrics on a recurring schedule (hourly)
  2. The compliance bridge evaluates each mapped metric against its rules
  3. Only active compliance runs are updated - completed runs are frozen as historical snapshots
  4. Per-device assignments are matched individually, so each device gets its own pass/fail status based on its specific metric value
The sync only updates existing compliance assignments in active runs. You still need to manually add metric-linked checks to your compliance runs (directly or through groups). The sync then keeps those assignments current.

​
Active vs. Completed Runs

Run StatusBehavior
Active (not completed)Metric values update the check status on every sync cycle
CompletedFrozen snapshot. The status reflects whatever the metric value was when the run was completed.
This gives you a historical audit trail. Each compliance run captures the state of your Liongard metrics at that point in time. When you start a new run with the same checks, it begins tracking from the current metric values.

​
Device-Level Assignments

When you assign a metric-linked check to a compliance run with device scope, each device that has a corresponding Liongard system gets its own assignment. The sync evaluates each device independently:
  • Device A may pass while Device B fails for the same metric
  • Only devices with linked Liongard systems receive updates
  • Company-level assignments (no device scope) use the worst status across all devices in that company

​
Best Practices

Start with High-Value Metrics

Focus on metrics that directly map to compliance requirements: MFA status, backup verification, encryption settings, and firewall rules.

Use Custom Rules for Thresholds

Liongard’s native pass/fail may not match your compliance thresholds. Custom rules let you set exact boundaries that align with your policies.

Group Metric Checks Together

Assign metric-linked checks to compliance groups so they can be added to runs as a batch instead of individually.

Review After Completing Runs

Before marking a run as completed, review the auto-synced statuses. Once completed, the run becomes a frozen historical record.