Home

Full Text Search on Certain Fields

Many asset fields containing text allow you to use full text search. Quickly find data of interest, combining advanced search capabilities to better interpret your question.

How to Search - The Basics

Let's take a look at the search field installedPatchTitle. There are many ways you can search this field.

Show any findings with this title

installedPatchTitle: Chrome

Show any findings that contain parts of the title

installedPatchTitle: "Vulnerabilities in Windows Media Could Allow Remote Code Execution"

Show any findings that match exact value

installedPatchTitle: `Chrome 40.0.2214.91`

Additional Search Capabilities

In some cases, field values are split into tokens that can be searched individually. Let's consider some scenarios for searching field values with additional search capabilities.

1) Field value contains a comma (,) or period (.) between numbers

Example: field contains the value "10,125" or "10.134".

In this case, the value is not split into tokens. Only exact or prefix matching on the full value is supported.

Matching:

installedPatchTitle: "10,1"

installedPatchTitle: "10"

installedPatchTitle: "10.134"

Non-matching:

installedPatchTitle: "125"

installedPatchTitle: "13"

2) Field value contains a period (.) between text

Example: field contains the value "qualys.corp.com".

In this case, the value is not split into tokens. Only exact or prefix matching on the full value is supported.

Matching:

tags.name: "qual"

tags.name: "qualys.corp"

tags.name: "qualys.corp.com"

Non-matching:

tags.name: "corp"

tags.name: "com"

3) Field value contains a comma (,) or period (.) between a number and text

Example: name field contains the value "102354.qualys" or "qualys,25576.13".

The value "102354.qualys" is split into 2 tokens: "102354" and "qualys". Prefix search on each token is supported.

Matching:

tags.name: "1023"

tags.name: "qualy"

Non-matching:

tags.name: "354"

tags.name: "lys"

4) Field value contains special characters and line/paragraph separators

Value contains a comma (,) dash (-), semicolon (;), line separator, paragraph separator (space/tab), carriage return, line feed, brackets ( ( [ { } ] ) ) or other special characters (? @ $ % & / \)

Example: name field contains the value "qualys-corp"

The value "qualys-corp" is split into 2 tokens: "qualys" and "corp". Prefix search on each token is supported.

Matching:

tags.name: "qua"

tags.name: "cor"

Non-matching:

tags.name: "alys"

tags.name: "orp"

5) Field value contains a phrase with a space, tab or new line

Example: field has value "Vulnerabilities in Windows Media Could Allow Remote Code Execution"

The value is split into tokens: "Vulnerabilities", "Windows", "Media", "Could", "Allow", "Remote", "Code", "Execution". We will perform complete case insensitive matching on each token in your search string and perform a prefix match on the last token in your search string.

Matching:

missingPatchTitle: "vulnerabilities remote win"

The "vulnerabilities" and "remote" tokens match completely and "win" matches the prefix search for "windows".

missingPatchTitle: "windows vuln"

The "windows" token matches completely and "vuln" matches the prefix search for "vulnerabilities".

missingPatchTitle: "remote code execution"

All 3 tokens "remote", "code" and "execution" match completely.

Non-matching:

missingPatchTitle: "vuln execution"

The "vuln" token is leading and it does not match completely so this search would not return a match.

missingPatchTitle: "vuln execution"

The "vuln" token is leading and it does not match completely so this search would not return a match.

Looking for something else?

Tell me about related findings

This actually broadens your search in many cases which can be helpful for finding what you're interested in. These searches can return more than what you might expect.

Analysis - The field value you enter is analyzed against an index of the field value on the platform. This index is created by removing punctuation, lowercasing, expanding to synonyms and other logical matches.

Results - Searches of the field index will return results that may not match casing or the exact words you enter and results may include related terms or synonyms.

Not using backticks?

If you're not using backticks we'll strip punctuation (including quotes) and match the words in any order, case and in most cases prefix.

I want case sensitive matches

Be sure to use backticks within your search value if you want to find exact matches.

 

Step by step search tutorial