Custom Overrides

Use Custom Overrides to manually override the predefined Verification Gates:

• Define Inclusion (Force Verified) queries to categorize specific devices as verified
• Define Exclusion (Force Unverified) queries to categorize specific devices as unverified
• Manually override the verification status of specific devices directly from the Devices page

Manually Verified / Manually Unverified appear as Verification Reasons for relevant assets in the Devices page.

Overrides are evaluated before the Verification Gates, in the following order:

1. Manual override - Devices you manually marked as Manually Verified or Manually Unverified. The verification process does not change the status of these devices until you remove the override.
2. Force Verified query - Devices that match this query are marked as Verified, with the Verification Reason Manually Verified. Devices with a manual override are not included.
3. Force Unverified query - Devices that match this query are marked as Unverified, with the Verification Reason Manually Unverified.

The Verification Gates are evaluated only for devices that don't match any of these overrides.

Custom Override Guidelines:

• To reset (remove) an override, click the X on the query dropdown to delete the selected query.
• Click View or Edit Query (next to the X) on the query dropdown to modify the selected query, or duplicate it and modify the duplicated version.
• You cannot manually remove the verification tags that are assigned by an override query - if you want to reset these devices' verification status, you must modify or delete the query.
• If there is a conflict between queries, for example, an asset that matches both the Force Verified and the Force Unverified queries, the Force Verified query takes precedence and the device is marked as Verified. In this case, the Verification reason is "Manually verified".
• Overrides are applied at the end of the next discovery cycle, like any other change in the Data Hygiene configuration.
• Open the By Asset tab to see a list of all devices you configured custom override for.

Manually Overriding Devices from the Devices Page

You can manually override the verification status of a single device or of several devices at once (up to 100 devices at a time) from the Devices page.

1. In the Devices page, select the relevant device(s).
2. In the side panel, under Device verification, select Mark as Verified/Unverified.
3. In the dialog, confirm the action.

To remove a manual override, select Remove manual override in the side panel.

[New screenshot required] - the Device verification menu in the side panel, and the override dialog (single device and bulk selection).

• Both actions are always available, regardless of the device's current verification status.
• When you select several devices, the action you choose is applied to all of them, even if a device already has the same verification status. If the selection contains devices with different statuses, all of them are overridden according to your choice.
• The verification process does not change the status of a manually overridden device until the override is removed.

Example Use Case

In this scenario, a specialized server matches the criteria for both automated gate failure AND two manual overrides.

• Device Profile: A critical legacy production server that has been offline for maintenance for 45 days. It has an active manual override to keep it verified, but a separate compliance query accidentally flags it as unverified.

Evaluation Steps:

1. Custom Overrides Evaluation: The engine checks the device against the Custom Overrides queries first:

   • Force Verified Query: The server matches a saved query named "Copy of Out-of-scope devices - Agent Coverage", which explicitly forces all critical production infrastructure to remain verified.
   • Force Unverified Query: The server also matches a saved query named "Out of Compliance Systems" because its operating system is outdated, flagging it to be forcefully unverified.

2. Conflict Resolution: Because the device matches both a Force Verified query and a Force Unverified query, the system applies the built-in precedence rule - Force Verified takes precedence over Force Unverified.

3. Automated Gate Evaluation: The device matched an override rule, so the Verification Gates are skipped for it. The Recency gate, which defines a 30-day limit after which devices become unverified, would otherwise have failed the server, as it has been offline for more than that.

Final Result: The manual inclusion query overrides both the automated failure AND the conflicting manual exclusion query. As a result, the Axonius Verified field is set to Yes, and the system updates its Verification Reason field to Manually Verified.