Browse Docs

Supported Trust Profile Check Types

In this document

Supported Platforms
All Checks at a Glance
Comparisons
Patterns (Glob)
Things to Keep in Mind
Articles by Category

This article lists every check you can add to a trust profile, grouped by the categories used in the Add a check menu, with the platforms that support each one. Each category has its own article with full details.

Supported Platforms

Platform

Checks available

Windows

File, Process, Application, Registry, Security, Operating System, Domain, Versions

macOS

File, Process, Property List, Security, Operating System, Domain, Versions

iOS

None. The platform can only be allowed or blocked.

Android

None. The platform can only be allowed or blocked.

Generic (every platform)

Network (IP Country)

All Checks at a Glance

Comparisons

Checks that compare a value have a drop-down next to their name. Depending on the check, the options are:

Comparison

Used for

equals, does not equal

Names and identifiers: countries, machine roles, domain names, GUIDs, join types, encryption methods. Also available on all version and text checks.

is less than, is less than or equal, is greater than, is greater or equal

Versions and numbers: DefensX Agent Version, Windows build number, macOS versions, Application Version, Registry Value, Preference key.

starts with, ends with, contains, matches (glob)

Text values. Only on Registry Value and Preference key.

Version comparisons work number by number, so 1.10 is higher than 1.9, and a missing part counts as zero (14.5 is the same as 14.5.0).

Patterns (Glob)

Several fields accept a glob pattern:

* matches any run of characters.
? matches exactly one character.
A value without * or ? must match exactly.

Patterns are not case sensitive. For example, Mozilla Firefox* matches Mozilla Firefox (x64 en-US).

Things to Keep in Mind

NOT reverses a check. Tick NOT to require the opposite. For example, NOT Reboot is required passes only on computers that don’t need a restart.
Missing is not the same as different. For comparison checks on a registry value, a preference key, an installed application or a domain name, a value that doesn’t exist at all makes both equals and does not equal fail. Add the matching exists or installed check if you need to decide what happens when the value is missing.
Errors never pass. If the agent cannot inspect something a check needs, the whole profile fails on that endpoint. An example is a folder it is refused access to. The Online Check detail page shows the reason.
Prefer positive checks. If a check name is unknown to an older agent, it answers false. Under NOT, a false turns into a pass. Keep agents up to date when you use newer checks.

Knowledge Base

Browse Docs

Introduction

Deployment

Management

Integrations

Nexi AI

Policy Management

Secure Access (ZTBA, formerly ZTNA)

Auto Pilot

Training Videos

Questions & Answers

MSP Automation