Find the metric or system
Use By Metric to inspect a metric across systems or By Device to inspect the metrics for a system. Search and inspector filters narrow the current view; the device view also offers a company filter. Use pagination to reach later results. Do not treat the visible page as the entire integration or assume the global company selector scopes this tenant integration view. Open a row to inspect its details. Compare the value, status, company/system identity and Last Evaluated time. Summary pass/fail/warning counts describe imported evaluations; Linked describes a mapping, not a successful compliance assessment.
Use By Metric to compare a metric across systems, or By Device to inspect a system.
Create a linked check
1
Open an unlinked metric
Open its details and choose Create Compliance Check. A metric already linked within this integration shows its linked state instead of another creation action.
2
Review the check details
Review Check Title, Description, Status List, optional Compliance Group, and Check Type. Device, Company and Control are different scopes; review the suggested type before saving. Choose a status list with suitable positive and negative outcomes.
3
Choose automatic evaluation
Auto-update from Liongard starts enabled. When enabled, choose Use Liongard status (pass/fail/warning) or Custom rules under Status Evaluation. These form choices remain a draft until creation.
4
Create and verify
Click Create Compliance Check. Reopen the metric and check the created library entry, group membership if selected, and subsequent run results. Creating a link is distinct from completing an assessment.
Understand evaluation
In native mode, Liongard Pass becomes the positive compliance outcome. Fail, Warning, an unknown status, or a missing status on an available metric value becomes the negative outcome. The compliance bridge does not preserve a third Warning outcome even though the imported metrics view displays warnings. Custom rules run from top to bottom; the first match wins. If no rules match supplies the fallback and initially defaults to Fail.
Use Add Rule to add each condition, threshold where needed, and Pass/Fail result. Arrange the intended order when building the list. For an illustrative requirement of a numeric value of at least 12, use Greater or equal
12 → Pass, then keep the fallback Fail. This does not let a missing or nonnumeric value pass through a default Pass result. Validate the provider’s actual value format before applying any example to an assessment.
If no stored custom rules are available, the bridge falls back to native status evaluation. Selecting Custom rules alone is not evidence that custom comparisons ran.
Understand automatic updates
Updates run through background synchronization. They depend on saved mappings, Auto-update, available metric values, a suitable status list and system/device/company matching. They are not a real-time or fixed completion-time guarantee.- Device checks: linked systems identify devices for individual evaluation. The bridge can create missing device-check assignments in active runs for the matching company, as well as update existing assignments. Consider all active runs for that company before enabling this automation.
- Company-level assignments: the bridge chooses a metric value using the worst imported native status for that company, then evaluates that selected value. With custom rules, this is not an evaluation of every value followed by the worst custom-rule result.
- No matching metric data: the assignment can be skipped; no change is not evidence of a new Pass.
- Completed runs: this bridge skips them. That does not establish that all application features make completed assessments immutable.
Frequently asked questions
Is a Linked badge proof that the compliance check passed?
Is a Linked badge proof that the compliance check passed?
No. Linked means the metric has a compliance mapping. Verify the actual assignment outcome, matching system/company and evaluation time.
Does a Liongard Warning remain Warning in compliance?
Does a Liongard Warning remain Warning in compliance?
No. The native bridge maps only Pass to the positive outcome. Warning and other non-pass statuses on an available metric value use the negative outcome.
What happens when none of my custom rules match?
What happens when none of my custom rules match?
The selected fallback applies; it initially defaults to Fail. Keep missing and nonnumeric data in mind before choosing Pass as a fallback.
Are Equals and Contains case-insensitive?
Are Equals and Contains case-insensitive?
No. They compare case-sensitive text. Exact formatting matters for Equals, and numeric comparisons should use the greater/less operators.
Can the bridge add checks to active runs?
Can the bridge add checks to active runs?
Yes. For mapped Device checks, it can create missing device assignments in active runs for the matching company. Do not assume it only updates assignments you previously added manually.
Does company-level evaluation test every device against my custom rules?
Does company-level evaluation test every device against my custom rules?
No. It selects a value by the worst imported native status for the company, then evaluates that selected value. This is not the worst result after evaluating every value against custom rules.
Does no data mean the check passes?
Does no data mean the check passes?
No. An assignment with no matching metric value can be skipped. An unchanged status does not prove a fresh successful evaluation.
Can I rely on the creation toast to confirm all custom rules saved?
Can I rely on the creation toast to confirm all custom rules saved?
No. The check or mapping can exist even if a later rule save fails. Verify actual evaluations and inspect existing records before retrying creation.
Are completed runs updated by the Liongard bridge?
Are completed runs updated by the Liongard bridge?
This bridge selects non-completed runs and skips completed ones. That behavior does not make every completed-run field immutable throughout the application.