Advanced Filtering
Last updated
Last updated
Advanced filtering can help you to quickly and easily find the information that you need, and help you save your search filter so you can easily repeat your search time and time again.
Advanced filtering is available in the Filters section of your table, or when selecting an individual column filter.
When selecting which advanced filter to use, there are multiple options to choose from:
Contains
Starts With
Ends With
Wildcard
Regex
The Contains filter is used to check whether an input value is contained anywhere within the search. It performs a case insensitive search by default.
Filtering for xss in the Vulnerability title using a Contains filter will check if xss is contained anywhere within the title. The following results would apply:
Reflected XSS [MATCH]
Reflected Cross-Site Scripting (XSS) [MATCH]
Xss Identified in Application Login Page [MATCH]
Stored xss Leads to Stolen Session Token [MATCH]
You can add further filters to Contains including:
Does Not - checks if the input value is NOT contained anywhere within the search.
Match Whole Word - checks if the input value is contained anywhere within the search and also matches the entire word. Using the example above - 1, 3 and 4 would be a match. 2 would not be a match due to the ( and ) wrapping the word xss.
Match Case - checks if the input value is contained anywhere within the search and the case sensitivity also matches. Using the example above - only 4 would be a match. 1, 2 and 3 all have different cases in use.
The Starts With filter is used to search records which begin with the characters specified within the input value. It performs a case insensitive search by default.
Filtering for xss in the Vulnerability title using a Starts With filter will check if xss is included at the start of the title. The following results would apply:
Reflected XSS [NO MATCH]
Reflected Cross-Site Scripting (XSS) [NO MATCH]
Xss Identified in Application Login Page [MATCH]
Stored xss Leads to Stolen Session Token [NO MATCH]
You can add further filters to Starts With including:
Does Not - checks if the search DOES NOT begin with the characters specified within the input value.
Match Whole Word - checks if the search begins with the characters specified within the input value and also matches the entire word. Using the example above - 3 would be a match.
Match Case - checks if the search begins with the characters specified within the input value and the case sensitivity also matches. Using the example above - there would be no matches.
The Ends With filter is used to search records which end with the characters specified within the input value. It performs a case insensitive search by default.
Filtering for xss in the Vulnerability title using a Ends With filter will check if xss is included at the end of the title. The following results would apply:
Reflected XSS [MATCH]
Reflected Cross-Site Scripting (XSS) [NO MATCH]
Xss Identified in Application Login Page [NO MATCH]
Stored xss Leads to Stolen Session Token [NO MATCH]
You can add further filters to Starts With including:
Does Not - checks if the search DOES NOT end with the characters specified within the input value.
Match Whole Word - checks if the search ends with the characters specified within the input value and also matches the entire word. Using the example above - 1 would be a match.
Match Case - checks if the search ends with the characters specified within the input value and the case sensitivity also matches. Using the example above - there would be no matches.
The Wildcard filter is used to perform Glob matching or globbing using wildcards (like * and ?) to match values based on patterns. It performs a case insensitive search by default.
Wildcards (**, *.js)
Negation ('!a/*.js', '*!(b).js')
extglobs (+(x|y), !(a|b))
POSIX character classes ([[:alpha:][:digit:]])
brace expansion (foo/{1..5}.md, bar/{a,b,c}.js)
regex character classes (foo-[1-5].js)
regex logical "or" (foo/(abc|xyz).js)
pattern
regex equivalent
description
?(pattern)
(pattern)?
Matches zero or one occurrence of the given patterns
*(pattern)
(pattern)*
Matches zero or more occurrences of the given patterns
+(pattern)
(pattern)+
Matches one or more occurrences of the given patterns
@(pattern)
(pattern) *
Matches one of the given patterns
!(pattern)
N/A (equivalent regex is much more complicated)
Matches anything except one of the given patterns
Supports lists - (aka "sets") a/{b,c}/d => ['a/b/d', 'a/c/d']
Supports sequences - (aka "ranges") {01..03} => ['01', '02', '03']
Supports steps - (aka "increments") {2..10..2} => ['2', '4', '6', '8', '10']
Supports escaping a\\{d,c,b}e => a{d,c,b}e
Filtering for xss OR cross site scripting anywhere in the Vulnerability title:
*xss*|*cross site scripting*Filtering for NOT 'HTTP' AND NOT 'MIME' anywhere in the Vulnerability title:
!(*HTTP*|*MIME*)You can add further filters to Starts With including:
Does Not - checks if the search DOES NOT match the glob specified.
Match Case - checks if the search matches the glob specified and the case sensitivity also matches.
The Regex filter is used to perform Regular Expression matching based on patterns. It performs a case sensitive search by default.
Filtering for xss OR cross site scripting anywhere in the Vulnerability title:
^xss|cross site scripting$Filtering for NOT 'HTTP' AND NOT 'MIME' anywhere in the Vulnerability title:
^(?!(.*HTTP.*|.*MIME.*)).*$You can perform a case insensitive search by clicking on flags and selecting insensitive from the options.
You can add further filters to Starts With including:
Does Not - checks if the search DOES NOT match the RegEx specified.
Filtering on List-type fields such as Tags will match against ANY of the tags. That is, if any tag in the list satisfies the filter, the filter will be considered a match.
For example, if you are filtering Vulnerabilities for the tag OWASP TOP 10 - so long as any of the tags on the vulnerability has the tag OWASP TOP 10, that vulnerability will be considered a match.
If you are wanting to filter Tags by multiple tags - for example to determine if any vulnerability has both OWASP TOP 10 and CWE TOP 25 - you can add multiple filter entries:
Custom Views allows you to save your favourite and frequently used table views.
You can easily configure and switch between different views providing flexibility in how you want to see your data.
Each view is saved against your own personal user settings, so you can tailor each view to exactly how you want it. And best of all - you can create as many views as you need!
COMING SOON! Ability for Admins to create Views and make them available to all or selected users, including setting default views for other users.
Each view is unique. You can save the following information and table state for each view:
Table filters, including Advanced filters
Column visibility
Column filters, including Advanced filters
Column ordering
Column sorting
Column locking
Column features
Table scroll
Each view gets its own name. You can also duplicate views to create similar ways of seeing your data.
We also support re-ordering your views, making it easy to switch between frequently accessed data.
You can create a new View by clicking on the + icon:
Once you have finished making the adjustments to your filtering and table, you can save your view by clicking on the Save icon:
You can update an existing View after making changes by clicking on the Save icon:
If you are on a View and you have moved away from what the View is configured to show, for example by further filtering or sorting, you can return back to the original results for the View by clicking on the Restore icon:
