Search by Field | Search without Field | String matching | Exact matching | Full text search | Suffix matching | Prefix matching | Is Null queries | Range searches | Date searches | Multiple values (In, Not In) | Boolean operators | Nested queries | Query limits
Enter the field name, then a colon, then your query. Nested fields are dot separated.
When your query doesn’t have a field name we’ll perform the broadest possible search across the attributes of all fields in the asset index (100+ field names). Keep in mind some fields are not included in the asset index, like tag name and vulnerability title, and for those you’ll need to search by field name.
How it works - A search for “win” without a field name will return assets where win appears in the asset name, hostname, operating system, software name, and so on.
Syntax help - Use single quotes or double quotes around your query to match a string. If you want to perform prefix matching or suffix matching using wildcards, you’ll need to search using the field name (see above).
Use single quotes or double quotes around your query to match a string with more than one word. Note that interfaces.address and software.version are text fields and support string matching.
tags.name: "Cloud Agent"
operatingSystem: 'Microsoft Windows'
vulnerabilities.vulnerability.title: "Remote Code Execution
Example using wildcard: If you want to search for exact count you should use asterisk (*). For example to find assets with name starting with WINDOWS2008 use this query:
Note that wildcards can only be used for prefix and suffix matching (as described below). We do not support substring wildcards, meaning you cannot search for a string in the middle of another string.
Use backticks to exactly match a string. Your results will include any asset with the EXACT value returned.
operatingSystem:`Windows 7 Ultimate
Service Pack 1`
Many asset fields containing text allow you to use full text search and advanced search capabilities. If your query does not include quotes (single or double) then we'll perform the broadest search.
Show any findings related to this title
vulnerabilities.vulnerability.title: Remote Code Execution
Show any findings that contain "Remote" or "Code" in title
vulnerabilities.vulnerability.title: "Remote Code"
Show any findings that match exact value "Remote Code"
vulnerabilities.vulnerability.title: `Remote Code`
Show any findings that match nested query. Both sub fields must match in order for an asset to be returned.
vulnerabilities.vulnerability: (title: `Remote Code` AND patchAvailable:
Suffix matching is supported when searching assets (on your Assets list) for the fields "name", "tags.name" and "netbiosName". Match asset values "ending in" a string you specify - using a string that starts with *. Matches are case insensitive.
Example: This query matches assets with an asset name ending in "53" like QK2K12QP3-65-53.
Example: This query matches assets with tag names ending in "region east" like Region East, region east, Region EAST.
Suffix matching is also supported for the field "interfaces.hostname" but the syntax is different.
Example: These queries match assets with the hostname "com-pa3020-36.eng.sjc01.qualys.com".
Prefix matching is supported when searching assets (on your Assets list) using certain text fields. Match asset values "starting with" a string you specify - using a string that ends with *. Matches are case sensitive.
Example: This query matches assets with an asset name starting with "xp" like xpsp2-jp-26-111.
Example: This query matches assets with tag names starting with "Win" like Windows XP, Windows 2012, Windows Hosts.
Example: This query matches assets with a hostname starting with "com-pa30" like com-pa3020-36.eng.sjc01.qualys.com.
Example: This query matches assets with an operating system starting with "Lin" like Linux 2.4-2.6.
Want to match an empty/null value for a field? You'll need to remove the colon and then write "is null". For example, quickly find assets where the OS has not been identified.
operatingSystem is null
interfaces.macAddress is null
Ranges can be specified with the
[lower .. upper] syntax
using () and/or  as follows. This is supported for numeric and date
Please note that interfaces.address and software.version are text fields (not numeric fields). You cannot perform range searches for these. See String matching to search text fields.
openPorts.port:(123 .. 1234)
// Greater than but not equal to 123 and less than but not equal
openPorts.port:(123 .. 1234]
// Greater than but not equal to 123 and less than or equal to 1234.
openPorts.port:[123 .. 1234)
// Greater than or equal to 123 and less than but not equal to 1234.
openPorts.port:[123 .. 1234]
// Greater than but or equal to 123 and less than or equal to 1234.
openPorts.port > 123 //
Greater than 123.
openPorts.port >= 123 //
Greater than or equal to 123.
openPorts.port < 1234 //
Less than 1234.
openPorts.port <= 1234 //
Less than or equal to 1234.
vulnerabilities.firstFound: [2018-01-01 .. 2018-04-01]
// Between January 1st and April 1st 2018.
Use a date range [start date .. end date] or a specific date. Several date variables are also available.
updated <= "2018-10-20"
updated:[now-3d .. now-1s]
Multiple values (In)
Use to match values "In" fields. You'll include a comma-separated list of values within square brackets. Available for all fields except analyzed fields (i.e. full text search fields). Values must exactly match. Matches are case sensitive.
Example: Find all assets with an operating system value that exactly matches one listed:
operatingSystem:["Cisco IOS Version 12.4(19)","Windows
Server 2003 Service Pack 2",Windows]
Example: Find all assets with a name value that exactly matches one listed:
Example: Find all assets with an asset ID value that exactly matches one listed:
Example: Find all assets with at least one of the CVE IDs listed:
Supported date formats:
YYYY example: [
Analyzed fields (i.e. full text search fields) are not supported such as:
Use keywords AND, OR, NOT to narrow or broaden your search. Click the link below for info on max query depth.
Note: The NOT operator can be used only with Asset search tokens. Vulnerability search tokens do not support the NOT operator.
AND NOT agentActivations.status:"INACTIVE"
(operatingSystem: windows OR operatingSystem:
linux) AND (openPorts.port: 80 OR openPorts.port: 8080) NOT operatingSystem:
Use a single nested query, using parentheses, to include multiple fields in your query per examples below.
Example: Show findings having vulnerabilities with a patch available and that require Windows authentication
Example: Find assets on port 80 and TCP
openPorts:(port:80 AND protocol:TCP)
Example: Find assets that have Windows Time service that is running
service:(name:Windows Time AND status: running)
Maximum query length allowed: 4096 characters
Maximum field value length allowed: 256 characters
Good to know:
- If your query exceeds a limit, an error message is shown and you won't get search results
- These query limits apply to queries created using these apps: AV, TP, CA, VM dashboard
- Spaces in between characters are counted as characters