Search Modifiers

You can use a search modifierWhen you search audit results, you can further qualify search terms with an issue attribute as a modifier. The syntax is: modifier:search_term to specify which attribute of an issue the search term should apply to. To use a modifier that contains a space in the name, such as the name of the custom tagDuring audits, users assign values to custom tags to indicate which issues to address and in what order. The system supplies the default Analysis tag. Administrators and security leads can add custom tags to the system. To be considered audited, an issue must have a value assigned to its primary custom tag., you must delimit the modifier with brackets. For example, to search for issues that are new, enter [issue age]:new.

A search that you do not qualify using a modifier matches the search string based on the following attributes: kingdom, primary rule id, analyzerA component of a security software product that looks for security issues using one or more particular techniques., filename, severityThe hierarchy of vulnerability seriousness (Critical, High, Medium, Low). (Same as Fortify Priority Order), class name, function name, instance id, package, confidenceThe degree of certainty that rules and Fortify Static Code Analyzer's capabilities can find an issue’s true vulnerability., type, subtype, taintData that a user inputs into the system. Insufficient validation of user input can lead to security issues. flags, category, sinkA place in the code where a potentially harmful function call or operation can take place., and sourceA place in the code where malicious data can enter..

To apply the search to all modifiers, enter a string such as control flow. This searches all modifiers and returns any result that contains the specified string.

To apply the search to a specific modifier, type the modifier name and the string as follows: analyzer:control flow. This returns all results whose analyzer is control flow.

The following table lists the search modifiers. A few of these have a shortened names, which are indicated in parentheses. You can use either modifier string.

Modifier	Description
`[issue age]`	Searches for the issue age, which is `new`, `updated`, `reintroduced`, or `removed`.
`<custom_tagname>`	Searches the specified custom tag. Note that tag names that contain spaces must be delimited by square brackets. Example: `[my tag]:value`
`analysis`	Searches for issues that have the specified auditThe process of assessing an application or program for security vulnerabilities. analysis value (such as `exploitable`, `not an issue`, and so on).
`analyzer`	Searches the issues for the specified analyzer
`audience`	Searches for issues by intended audience. Valid values are `targeted`, `medium`, and `broad`.
`audited`	Searches the issues to find `true` if the primary custom tagA list-type custom tag that to which a user must assign a value in order to successfully complete the audit of an issue. An application version must have a primary custom tag assigned to it for auditing. By default, the Analysis tag is the primary tag. is set and `false` if the primary custom tag is not set. The default primary tag is the Analysis tag.
`category` `(cat)`	Searches for the given category or category substring.
`comments` `(comment, com)`	Searches for issues that contain the search term in the comments that have been submitted on the issue.
`commentuser`	Searches for issues with comments from the specified user.
`confidence (con)`	Searches for issues that have the specified confidence value. Fortify Static Code Analyzer calculates the confidence value based on the number of assumptions made in code analysis. The more assumptions made, the lower the confidence value.
`file`	Searches for issues where the primary location or sink node function call occurs in the specified file.
`[fortify priority order]`	Searches for issues that have a priority level that matches the specified priority determined by Fortify Static Code Analyzer. Valid values are `critical`, `high`, `medium`, and `low`, based on the expected impact and likelihood of exploitation. The impact value indicates the potential damage that might result if an issue is successfully exploited. The likelihood value is a combination of confidence, accuracyA measure of how closely the rules used in scanning and analysis come to uncovering an application’s actual vulnerabilities. of the rule, and probability that the issue can be exploited.
`historyuser`	Searches for issues that have audit data modified by the specified user.
`kingdom`	Searches for all issues in the specified kingdom.
`maxconf`	Searches for all issues that have a confidence value equal to or less than the number specified as the search term.
`<metadata_listname>`	Searches the specified metadata external list. Metadata external lists include [OWASP Top 10 2013], [SANS Top 25 2011], and [PCI 3.2], and others. Square braces delimit field names that include spaces.
`minconf`	Searches for all issues that have a confidence value equal to or greater than the number specified as the search term.
`package`	Searches for issues where the primary location occurs in the specified package or namespace. For dataflow issues, the primary location is the sink function.
`[primary context]`	Searches for issues where the primary location or sink node function call occurs in the specified code context. Also see sink and [source context].
`primaryrule (rule)`	Searches for all issues related to the specified sink ruleRule that identifies points in a program that tainted data must not reach..
`sink`	Searches for issues that have the specified sink function name. Also see [primary context].
`source`	Searches for dataflow issues that have the specified source function name. Also see [source context].
`[source context]`	Searches for dataflow issues that have the source function call contained in the specified code context Also see source and [primary context].
`sourcefile`	Searches for dataflow issues with the source function call that the specified file contains. Also see file.
`status`	Searches issues that have the status reviewed, not reviewed, or under review.
`suppressed`	Searches for suppressed issues.
`taint`	Searches for issues that have the specified taint flagAn attribute of tainted data that enables the Dataflow Analyzer to accurately identify issues..

For examples of search queries that use modifiers, see Search Query Examples.

See Also

Searching Issues