Some fields containing strings of text (like names, descriptions) allow you to use full text search. Quickly find data of interest, combining advanced search capabilities to better interpret your query. Full text search fields do not support exact matching.
Let's take a look at the search field control.name. There are many ways you can search this field.
Show any findings with this name
control.name: Ensure IAM Password Policy is Enabled
Show any findings that contain "ensure" and "IAM" in the name (in any order, case insensitive)
control.name: "ensure IAM"
Show any findings with "90" in the name
control.name: 90
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.
Example: control.name field has value "Ensure IAM Password Policy is Enabled"
The value is split into 6 tokens: "Ensure", "IAM", "Password", "Policy", "is" and "Enabled". 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:
control.name: "ensure iam pass"
The "ensure" and "iam" tokens match completely and "pass" matches the prefix search for "password".
control.name: "is enab"
The "is" token matches completely and "enab" matches the prefix search for "enabled".
control.name: "iam password policy"
All 3 tokens "iam", "password" and "policy" match completely.
Non-matching:
control.name: "ens password"
The "ens" token is leading and it does not match completely so this search would not return a match.
control.name: "pass policy"
The "pass" token is leading and it does not match completely so this search would not return a match.
control.name: "iam policy word"
The "word" token is the last token and it does not match completely nor does it match a prefix search.
Example: name 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:
name: "10,1"
name: "10"
name: "10.134"
Non-matching:
name: "125"
name: "13"
Example: name 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:
name: "qual"
name: "qualys.corp"
name: "qualys.corp.com"
Non-matching:
name: "corp"
name: "com"
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:
name: "1023"
name: "qualy"
Non-matching:
name: "354"
name: "lys"
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:
name: "qua"
name: "cor"
Non-matching:
name: "alys"
name: "orp"
Tell me about related findingsTell 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.