Filter Index
Note: Currently this article only covers Finding Filters available in the DefectDojo Pro UI, but this article will be expanded in the future to govern more object types, along with Open-Source filters.
Here is a list of filters that can be applied in the DefectDojo Pro UI to sort lists of Findings. DefectDojo Filters can be used to assist with navigating through lists of Objects, building custom dashboards, or creating automation via Rules Engine.
How date filters are evaluated
Filters that take a date β Date Created, SLA Expiration Date, Last Status Update, Planned Remediation Date, and the Jira date filters listed below β offer five operators:
| Operator | Matches |
|---|---|
| On | The whole of the named day. |
| Before | Everything up to the start of the named day. The named day itself is not included. |
| After | Everything past the start of the named day β so the named day is included. |
| During | A start day through an end day, both inclusive. |
| Within | A rolling window ending now: Past 7, 14, 30, 90 or 180 Days, or Past Year. |
Note that Before and After are deliberately not mirror images of each other: Before 8 August excludes 8 August, while After 8 August includes it.
Day boundaries and your timezone
On, Before, After and During resolve their day boundaries in your own timezone, detected from your browser. A date range therefore covers midnight to midnight as you experience it, rather than in UTC or in the server’s timezone. Two people in different timezones can see slightly different results from the same filter for Findings falling close to a day boundary.
Within is unaffected β it is a rolling window measured back from the current moment, so it has no day boundary to resolve.
Where this does not apply. Only requests from the Pro UI carry your timezone. Anything that runs without a browser β the
/api/v2REST API, scheduled reports, and the Rules Engine β falls back to the server’s configured timezone (DD_TIME_ZONE,UTCunless your administrator changed it). If your browser timezone differs from the server’s, a scheduled report and an on-screen filter using the same date can return slightly different rows. Exports started from a filtered table in the UI are not affected β they use your timezone, matching what you were looking at.
How number filters are evaluated
Numeric filters β including Age and SLA β offer a match operator alongside the value: Equals, Not Equals, Greater Than, Greater Than or Equal To, Less Than, Less Than or Equal To, In List, and Not In List. Entering a value without choosing an operator matches on Equals.
SLA filters
Three filters cover SLA, and they answer different questions:
| Filter | Type | What it matches |
|---|---|---|
| SLA Expiration Date | Date, with the operators above | The date the Finding’s SLA runs out. |
| SLA | Number, with operators | Days remaining on the SLA clock. Negative values are overdue, so Less Than 0 finds everything currently past its deadline, and Less Than 7 finds what is due within the week. |
| Mitigated Within SLA | True / False | Whether a Finding that has been mitigated was mitigated before its SLA expired. |
Mitigated Within SLA is narrower than it sounds, and this catches people out. Both values only ever match Findings that are already mitigated and are not Info severity:
- True β mitigated on or before the SLA expiration date.
- False β mitigated after the SLA expiration date.
An open Finding that is already overdue matches neither value, because it has not been mitigated yet. To find those, use SLA Less Than 0 instead. Info-severity Findings are excluded from both sides.
If a Finding’s SLA configuration has Cap SLA by CISA KEV Due Date enabled, both SLA and SLA Expiration Date reflect the tightened, KEV-capped deadline rather than the plain severity-based window. There is no separate indicator for this in the filters β see EPSS / KEV.
Findings
These fields are specific to DefectDojo Findings and are used to organize a Finding. Each of these filters is a separate column in the All Findings table.
Findings in DefectDojo can be filtered by:
DefectDojo Metadata
These Filters are related directly to DefectDojo core functionality.
Cannot be modified
These Filters are assigned at the time of issue creation, and cannot be directly modified via Edit Finding.
- Finding Severity (any of Info, Low, Medium, High, Critical)
- Asset
- Organization
- Engagement
- Engagement Version
- Test
- Test Type
- Test Version
- Date Created
- Age (Finding age in days)
- SLA (days remaining on the SLA clock β negative means overdue; see SLA filters)
- SLA Expiration Date (see SLA filters)
- Mitigated Within SLA (True or False β note this only matches Findings that have already been Mitigated; see SLA filters)
- Reporter (user or service who created the Finding)
- Found by (refers to the Tool)
Can be modified
These fields are set when an issue is created, but can be modified as an issue progresses.
- Status
- Last Status Update (Timestamp)
- Mitigated (True or False)
Additional Model Functions
These DefectDojo functions can be used to further organize your Findings or track remediation.
- Finding Tags
- Reviewers (Assigned User)
- Has Notes (True/False)
- Group (refers to the Finding Group, if one exists)
- Risk Acceptance (select one or more existing Risk Acceptances from the list)
Tool-Specific Metadata
These fields have no direct impact on the functionality of DefectDojo, but provide additional information to help explain and mitigate issues. They can be set when a Finding is initially created (using information in an incoming report), or they can be changed by a user.
- CWE Value
- Vulnerability ID (usually a CVE)
- EPSS Score
- EPSS Percentile
- Service
- Planned Remediation Date
- Planned Remediation Version
- Has Component (True/False)
- Component Name
- Component Version
- File Path
- Effort for Fixing
Jira Metadata
If using the Jira integration, these filters track updates to linked Jira Issues.
- Jira Issue (Can filter by whether the Finding has one, or not)
- Jira Age (Age of Jira Issue)
- Jira Change (Last time changes were pushed to Jira)