Listed here are all the CQL values that can be used to perform searches, queries, and filters in the system. The CQL values are used to create reports and triggers, and are used to filter source activity for investigations.
Use the following list as a reference when you enter queries in the simplified query builder or when you enter the queries manually.
NOTE: Some values are only listed in the web interface if they are available to the query type.
By default, all searches and  trigger queries must begin with the WHERE clause.
You can create complex queries by joining CQL values together using Boolean search operators. For example:
WHERE (cmd_user_typed = 'true' and cmd = 'clear') and (cmd_hour_of_day < '08' or cmd_day_of_week IN 'saturday,sunday')
            The example query would return results where (the user manually typed the command, and the command is "clear") and (the command was executed before 8am or on Saturday/Sunday).
| Boolean operators | Description | 
|---|---|
| ' ' | Quotation marks are used to contain the search values. | 
| ( ) | Parentheses are used to group CQL values to create complex queries. | 
| and | All of the queries must be true | 
| or | Any of the queries must be true | 
You can use the following operators to define specific CQL query values:
| CQL Operator | Description | 
|---|---|
| = | Is equal to 
 | 
| != | Is not 
 | 
| < | Less than. When used with time or dates, it represents "before". 
 | 
| > | Greater than. When used with time or dates, it represents "after". 
 | 
| <= | Less than or equal to 
 | 
| >= | Greater than or equal to 
 | 
| IN | Includes Should only be used when looking for specific values, do not use to find random wildcards. 
 | 
| NOT IN | Excludes Should only be used when looking for specific values, do not use to find random wildcards. 
 | 
| * | Wildcard Supported by most CQL values except where noted. 
 | 
| Query | Description | 
|---|---|
| cmd | Command 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| cmd_date | Command date For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 
 | 
| cmd_day_of_week | Command day of week. For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| cmd_exec_path | Command executable path 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| cmd_file_modified | Command file that was modified 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| cmd_first_time_command | Command that is executed for the first time 
 Supports the following CQL operator: = 
 
 | 
| cmd_first_time_command_root | Root command that is executed for the first time. 
 Supports the following CQL operator: = 
 
 | 
| cmd_has_alert | Trigger matching this command generates an alert 
 Supports the following CQL operator: = 
 
 | 
| cmd_has_error | Command generates an error output 
 Supports the following CQL operator: = 
 
 | 
| cmd_has_modified_files | Command that modified files 
 Supports the following CQL operator: = 
 
 | 
| cmd_has_output | Command generated an output 
 Supports the following CQL operator: = 
 
 | 
| cmd_has_violation | Command caused a violation 
 Supports the following CQL operator: = 
 
 | 
| cmd_hour_of_day | Command hour of day. For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operator: =, !=, <, >, IN, NOT IN 
 
 | 
| cmd_include_system_calls | Command including system calls 
 Supports the following CQL operator: = 
 
 | 
| cmd_parameters | Command parameters 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| cmd_parent_cmd | Command's parent command 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| cmd_parent_pid | Command's parent process ID 
 Supports all CQL operators. 
 
 | 
| cmd_pid | Command process ID 
 Supports all CQL operators. 
 
 | 
| cmd_root | Command root 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| cmd_working_directory | Command working directory 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| Query | Description | 
|---|---|
| session | Session ID NOTE: Wildcard queries are not supported. You must enter the exact session ID. The session ID can be found on the Sources page, under the Sessions tab. The session ID value is case sensitive. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| session_city | Session city 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_command_count | Total of user entered commands during a session 
 Supports all CQL operators. 
 | 
| session_connect | Session connected 
 Supports the following CQL operator: = 
 
 | 
| session_country | Session country. Use the 2 character ISO country abbreviation (link goes to a third-party site). 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_date | Session date For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 
 | 
| session_day_of_week | Session day of the week For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_dualauth_approved | Multi-factor authentication is approved for the session 
 Supports the following CQL operator: = 
 
 | 
| session_dualauth_provider | Session used a specific 2-factor authentication provider. Options include: 
 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_dualauth_required | Session required 2-factor authentication 
 Supports the following CQL operator: = 
 
 | 
| session_duoapi_approved | Session activity is successfully authenticated through Duo Security 
 Supports the following CQL operator: = 
 
 | 
| session_duoapi_approver | Session activity is approved by a specific Duo Security user 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| session_duoapi_required | Session activity required authentication through Duo Security 
 Supports the following CQL operator: = 
 
 | 
| session_duration | Session duration 
 Supports the following CQL operators: >=, <= 
 | 
| session_first_time_ip | Session initiated from a new IP address 
 Supports the following CQL operator: = 
 
 | 
| session_has_alert | Trigger matching this session generated an alert that is still unresolved. 
 Supports the following CQL operator: = 
 
 | 
| session_has_violation | Trigger matching this session generated a violation. Includes resolved and unresolved alerts. 
 Supports the following CQL operator: = 
 
 | 
| session_hour_of_day | Session hour of day For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operator: =,!=, <, >, IN, NOT IN 
 
 | 
| session_how_connected | Session connected via a specific method. Options include: 
 
 Supports the following CQL operator: =, != 
 | 
| session_ip | Session IP address 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_ip_type | Session IP address type can be internal or external. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_jira_approved | Session activity is linked to a valid Jira ticket 
 Supports the following CQL operator: = 
 
 | 
| session_jira_required | Session activity must be linked to a Jira ticket 
 Supports the following CQL operator: = 
 
 | 
| session_jira_ticket | Session activity is linked to a specific Jira ticket 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| session_open | Session is open. Tip: A session is considered closed if it is inactive for 3 minutes. 
 Supports the following CQL operator: = 
 
 | 
| session_pid | Session process ID 
 Supports all CQL operators. 
 
 | 
| session_region | Session state or province Use the 2 character ISO abbreviation (link goes to a third-party site). 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_user | Session user Use the server username, or the Cmd username. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_user_job | Session user's assigned job category A user's job category is listed in their Cmd user account. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| session_violation_count | Session violation total 
 Supports all CQL operators. 
 
 | 
| Query | Description | 
|---|---|
| server | Server ID NOTE: Wildcard queries are not supported. You must enter the exact server ID. The server ID can be found on the Sources page, under the Server tab. 
 Supports the following CQL operator: = 
 | 
| server_added | Server is added on specified date For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 
 | 
| server_capture_output | Server output that has been captured by the system 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 
 | 
| server_city | Server city 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_command_count | User entered command total on the server 
 Supports all CQL operators. 
 
 | 
| server_country | Server country Use the 2 character ISO country abbreviation (link goes to a third-party site). 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_date | Date on the server For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 | 
| server_get_file_diff | Server captures file differences 
 Supports the following CQL operator: = 
 
 | 
| server_group | Server group 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_has_alert | Trigger matching this server generates an alert that is still unresolved. 
 Supports the following CQL operator: = 
 
 | 
| server_has_violation | Trigger matching this session generated a violation. Includes resolved and unresolved alerts. 
 Supports the following CQL operator: = 
 
 | 
| server_hostname | Server hostname 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| server_ip | Server IP address 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_last_login | Server last login date You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 | 
| server_name | Server name 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_os | Server operating system Include the build or kernel version to narrow the query. 
 Supports the following CQL operators: =, != 
 
 | 
| server_region | Server state or province Use the 2 character ISO abbreviation (link goes to a third-party site). 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| server_session_count | Server session total 
 Supports all CQL operators. 
 
 | 
| server_violation_count | Server violation total 
 Supports all CQL operators. 
 
 | 
| Query | Description | 
|---|---|
| trigger_date | Trigger date For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. You can also enter time frames, like "yesterday", "4 days ago" or "last month." Be aware that integer values will be treated as Unix timestamps and non-integer values will be treated as date strings. 
 Supports the following CQL operators: =, !=, >, <, >=, <= 
 
 | 
| trigger_day_of_week | Trigger day of the week For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| trigger_group | Trigger group name 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| trigger_has_unresolved | Trigger has unresolved alerts 
 | 
| trigger_has_violation | Trigger has resolved and unresolved alerts 
 | 
| trigger_hour_of_day | Trigger hour of day For triggers, the date is in UTC. For all other CQL search queries, the date is based on your local time. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 | 
| trigger_name | Trigger name 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| trigger_risk_level | Trigger violation risk level 
 Supports all CQL operators. 
 
 | 
| trigger_verified_by_name | Trigger is resolved by Cmd user 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
Macros are CQL trigger queries that have been saved and are used in other triggers. Macro queries are always prefixed with macro_ followed by the user defined name. For more information, see Macros.
The query itself would be in this format:
macro_<user defined macro name> = '<true or false>'
            
Supports the following CQL operator: =
macro_stop_sudo = 'true'
            
| Query | Description | 
|---|---|
| mfa_dualauth_approved | 2-factor authentication is approved 
 Supports the following CQL operator: = 
 
 | 
| mfa_dualauth_provider | 2-factor authentication method. Typically Google or Duo. 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| mfa_dualauth_required | 2-factor authentication is required 
 Supports the following CQL operator: = 
 
 | 
| mfa_duoapi_approved | 2-factor authentication by Duo is approved 
 Supports the following CQL operator: = 
 
 | 
| mfa_duoapi_approver | 2-factor authentication is approved by specified Duo user 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 | 
| mfa_duoapi_required | 2-factor authentication is required through Duo 
 Supports the following CQL operator: = 
 
 | 
| mfa_jira_approved | Authenticated user is linked to a valid Jira ticket 
 Supports the following CQL operator: = 
 
 | 
| mfa_jira_required | Authenticated user activity must be linked to a Jira ticket 
 Supports the following CQL operator: = 
 
 | 
| mfa_jira_ticket | Authenticated user activity is linked to a specific Jira ticket 
 Supports the following CQL operators: =, !=, IN, NOT IN 
 
 |