From the AD Group dropdown list, select the desired Active Directory (AD) group. EMS considers the endpoint as satisfying the rule if the logged in user belongs to the selected AD group. The rule considers the logged-in user's group membership, not the computer's attributes.

You can use the NOT option to indicate that the rule requires that the logged in user does not belong to certain AD groups. You cannot use the NOT option to indicate that the rule requires that the logged in user does not belong to any AD group. EMS does not support a rule to dynamically group all endpoints that do not belong to a domain.

To use this option, you must configure your domain under Endpoints. See Adding endpoints using an AD domain server.

From the AV Software dropdown list, select the desired conditions. You can require that an endpoint have AV software installed and running and that the AV signature is up-to-date. You can also use the NOT option for the rule to require that the endpoint does not have AV software installed or running or that the AV signature is not up-to-date. This rule applies for FortiClient AV and third-party AV software that registers to the Windows Security Center. The third-party software notifies the Windows Security Center of the status of its signatures. FortiClient queries the Windows Security Center to determine what third party AV software is installed and if the software reports signatures as up-to-date.

For Windows, this feature supports third party AV applications. For macOS and Linux, this feature can only check if FortiClient AV protection is enabled and does not recognize third party AV applications.

The endpoint must satisfy all configured conditions to satisfy this rule.

In the Subject CN and Issuer CN fields, enter the certificate subject and issuer. You can also use the NOT option to indicate that the rule requires that a certain certificate is not present for the endpoint.

For Windows and macOS, FortiClient checks certificates in the current user personal store and local computer personal store. It does not check in trusted root or other stores.

For Linux, FortiClient checks root CA certificates installed on the system. For Ubuntu, FortiClient checks /etc/ssl/certs/ca-certificates.crt. For CentOS and Red Hat, FortiClient checks /etc/pki/tls/certs/ca-bundle.crt. For Linux, FortiClient does not check user certificates.

The Subject CN and Issuer CN fields do not support wildcards.

The endpoint must satisfy all conditions to satisfy this rule. For example, if the rule is configured to require certificate A, certificate B, and NOT certificate C, then the endpoint must have both certificates A and B and not certificate C.

EMS considers the endpoint as satisfying the rule if the endpoint has FortiClient installed and Telemetry connected to EMS.

In the File field, enter the file path. You can also use the NOT option to indicate that the rule requires that a certain file is not present on the endpoint.

The endpoint must satisfy all configured conditions to satisfy this rule. For example, if the rule is configured to require file A, file B, and NOT file C, then the endpoint must have both files A and B and not file C.

In the Domain field, enter the domain name. If the rule is configured for multiple domains, EMS considers the endpoint as satisfying the rule if it belongs to one of the configured domains.

From the OS Version field, select the OS version. If the rule is configured for multiple OS versions, EMS considers the endpoint as satisfying the rule if it has one of the configured OS versions installed.

The following options are available for Windows:

• Enable latest update check: FortiClient checks if Windows OS updates were recently installed.
• Latest update within: Configure the amount of time after the last system update was received that FortiClient considers the OS outdated. For example, if you configure this option to be 60 days, FortiClient considers the OS outdated 61 days after the most recent system update.

By default, the rule requires that the endpoint is on-Fabric. You can also use the NOT option to indicate that the rule requires that the endpoint is off-Fabric.

In the Registry Key field, enter the registry path or value name. End the path with \ to indicate a registry path, or without \ to indicate a registry value name. You can also use the NOT option to indicate that the rule requires that a certain registry path or value name is not present on the endpoint. This rule does not support using the value data.

For example, the following shows a system where Firefox is installed. In this example, the registry path is HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Mozilla Firefox\88.0 (x64 en-US)\Main. The value name is Install Directory, and the value data is C:\Program Files\Mozilla Firefox. You can configure a registry key rule to match HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Mozilla Firefox\88.0 (x64 en-US)\Main as the path or Install Directory as the registry value name, but you cannot configure a rule to match C:\Program Files\Mozilla Firefox.

Do not use square brackets when configuring this rule type.

The endpoint must satisfy all configured conditions to satisfy this rule. For example, if the rule is configured to require registry key A, registry key B, and NOT registry key C, then the endpoint must have both registry keys A and B and not registry key C.

In the Running Process field, enter the process name. You can also use the NOT option to indicate that the rule requires that a certain process is not running on the endpoint.

The endpoint must satisfy all configured conditions to satisfy this rule. For example, if the rule is configured to require process A, process B, and NOT process C, then the endpoint must have both processes A and B running and process C not running.

From the Sandbox Detection dropdown list, select the desired condition. You can require that Sandbox detected malware on the endpoint in the last seven days. You can also use the NOT option for the rule to require that Sandbox did not detect malware on the endpoint in the last seven days.

Only FortiClient 6.2.2+ endpoints support this rule type.

Under User Identity, select the following:

• User Specified: endpoint user manually entered their personal information in FortiClient.
• Social Network Login: endpoint user provided their personal information by logging in to their Google, LinkedIn, or Salesforce account in FortiClient. You can further select one of the following:
  • All Accounts: all endpoints where the user logged in to the specified social network account type.
  • Specified: enter a specific Google, LinkedIn, or Salesforce account. For example, you can enter joanexample@gmail.com to configure the rule to apply specifically to only that Google account. You can specify multiple social network accounts.
• Verified User: endpoint user must be a verified user that has authenticated their connection to EMS as a member of an authorized user group. See User Management.

EMS considers the endpoint as satisfying the rule if it satisfies one of the conditions.

You can also use the NOT option for the rule to require that the endpoint user has not manually entered user details or logged in to a social network account to allow FortiClient to obtain user details.

FortiClient iOS does not support social network login with LinkedIn or Salesforce. FortiClient Android does not support social network login with Salesforce.

From the Severity Level dropdown list, select the desired vulnerability severity level. If the rule is configured for multiple severity levels, EMS considers the endpoint as satisfying the rule if it has a vulnerability of one of the configured severity levels or higher.

Select the checkbox to require that File Vault is enabled on the endpoint. You can also use the NOT option to indicate that the rule requires that File Vault is disabled on the endpoint.

From the Windows Security dropdown list, select the desired conditions. You can require that an endpoint have one or more of the following applications enabled:

• Windows Defender: antimalware component of Windows. Scans files to detect and remediate threats.
• Bitlocker Disk Encryption: data protection feature that integrates with the operating system (OS) and addresses the threats of data theft or exposure from lost, stolen, or inappropriately decommissioned computers. BitLocker enhances file and system protections and helps render data inaccessible when computers are decommissioned or recycled. See BitLocker.
• Exploit Guard: automatically applies exploit mitigation techniques to OS processes and applications. When Exploit Guard finds a mitigation, Windows displays a notification from the Action Center. See Protect devices from exploits.
• Application Guard: helps to prevent old and newly emerging attacks by isolating enterprise-defined untrusted sites. For example, Application Guard helps prevent untrusted Microsoft Word, PowerPoint, and Excel files from accessing trusted resources by opening untrusted files in an isolated Microsoft Hyper-V-enabled container. See Microsoft Defender Application Guard overview.
• Windows Firewall: firewall component of Windows. Helps prevent hackers and malicious software from gaining access to the device through the Internet or a network.

You can also use the NOT option for the rule to require that the endpoint have one or more of the listed applications disabled.

The endpoint must satisfy all configured conditions to satisfy this rule.

In the CVEs field, enter the common vulnerabilities and exposures (CVE) ID in the format CVE-xxxx-xxxxx. For example, you could enter CVE-2020-26950. You can also use the NOT option to indicate that the rule requires that a CVE is not present on the endpoint.

EMS considers the endpoint as satisfying the rule if it satisfies one of the conditions.