This chart presents the history of reported risk exposure (in CVSSF units), along with that of your actions addressing it. As this risk exposure is caused by the detected software vulnerabilities, the status of the latter, be it closed (remediated) or accepted, is by extension the status of risk exposure. With the help of this chart, you can identify gaps between known risk and managed risk.
This figure is the percentage increase in risk exposure in the current sprint (i.e., the newly reported exposure value relative to the initial exposure value). The value is zero when no vulnerability has been reported in the period.
This figure is the percentage decrease in risk exposure in the current sprint (i.e., the newly remediated exposure value relative to the initial exposure value). The value is zero when no vulnerability has been remediated in the period.
This figure is the resulting percentage change in risk exposure in the current sprint (i.e., the exposure decrement minus the exposure increment). A positive value means that more exposure was reported than remediated. A negative value means that more exposure was remediated than reported. A zero value means that as much exposure was remediated as reported.
This chart shows how you have dealt with risk exposure (in CVSSF units) over time by correspondence with the statuses of vulnerabilities that cause it. Open vulnerabilities are those still present and unaccepted; whereas closed ones are those remediated. The information in this chart allows you to visualize the trends in your vulnerability management efforts, helping you identify areas where you are making progress and those that require more attention.
This chart shows your risk exposure level (CVSSF) and allows you to compare it with that of other organizations, groups, or portfolios. Specifically, you can see how the best-performing and worse-performing at risk management are doing, as well as how many CVSSF units is the average. This benchmarking enables you to gauge your performance relative to your peers to ultimately set goals for reducing your risk exposure.
This chart shows you how risk exposure (in CVSSF units) has changed over time across the nine categories that group the types of vulnerabilities in Fluid Attacks' classification. This information helps you with an overview of the kinds of issues related to changes in your risk exposure.
This figure is the number of days since a code fix successfully remediated a vulnerability. This information may provide insight into the promptness with which your team addresses security issues.
This figure is the average number of days it takes your team to request a reattack, i.e., a retest to verify the effectiveness of code fixes, after the vulnerability in question is reported. This information can serve as one factor to assess the responsiveness of your team to security issue reports.
This figure is the number of vulnerabilities for which currently a reattack has been requested and a response by Fluid Attacks is in the works. This may be one factor to assess your team's productivity.
This figure is an estimated timeframe to remediate all vulnerabilities reported to date. This information may help you set goals for your remediation efforts.
This chart displays the average number of days it takes your team to remediate a vulnerability weighted by risk exposure as measured using the CVSSF metric. Further, it allows comparing your performance against that of the best and worst performing organizations, groups or portfolios, as well as against the average value. This benchmark helps you to evaluate the efficiency of your remediation process compared to your peers and set goals.
This chart shows the average time to remediate vulnerabilities weighted by risk exposure, differentiating by the qualitative severity rating. The qualitative rating groups CVSS scores as follows: Low = 0.1 - 3.9; medium = 4.0 - 6.9; high = 7.0 - 8.9; critical = 9.0 - 10.0. The information in this chart helps you understand how the severity of vulnerabilities impacts your remediation time.
This chart displays the shares of accepted versus open vulnerabilities, categorized by qualitative severity rating (low, medium, high, and critical). Open vulnerabilities are those that have not been remediated nor accepted. This information helps you understand the risks you have chosen to accept.
This chart shows the percentage of vulnerabilities not yet remediated that have been assigned to your team members for fixing versus those still unassigned. This chart provides a quick overview of your vulnerability assignment.
This figure presents, of all vulnerabilities that were assigned for remediation, what percentage is open (pending to be fixed) and what percentage is closed (already fixed). This information allows you to track the progress of your team in addressing assigned vulnerabilities.
This chart displays the distribution of detected vulnerabilities still present in your systems by their current treatment:
This chart shows the percentage breakdown of all reported vulnerabilities based on the security testing technique used to detect them. This information provides insights into the kind of issues more frequently present in your system. The techniques are the following:
This chart illustrates the composition of your assets under assessment, contrasting the share represented by source code repositories with the share comprised of URLs or IPs linked to those repositories. This information might be useful for characterizing the scope of evaluation.
This figure is the amount of types of vulnerabilities reported to you out of all the types recognized by Fluid Attacks' categorization. These categories are the ones into which security issues found in your system most likely fall.
This figure is the total amount of reported security issues with a specific location within your system. This information may be of help to justify the need for additional security investments.
Exclusions are vulnerabilities deliberately omitted by you. The total number of exclusions your group has is shown.
These are all your exclusions categorized by root.
This chart shows the number of vulnerabilities for each of the tags your team has categorized them into when assigning a treatment. This information allows you to analyze the security issues in your software using categories that are especially significant for your team.
This chart shows the number of vulnerabilities for each of the priority values your team has given them when assigning a treatment. This information might help your team to understand its vulnerability prioritization strategy.
This chart shows you the number of accepted vulnerabilities grouped by the user who assigned the treatment. This information provides details about accountability for this important vulnerability management decision.
This chart shows how team members have managed the risk exposure (CVSSF) assigned to them, which is identified by the statuses of vulnerabilities that cause that risk exposure. Open vulnerabilities are those still present and unaccepted; whereas closed ones are those remediated. The information in this chart provides details about accountability for vulnerability remediation.
This chart shows the paths of files with vulnerabilities from the last 20 weeks, not yet remediated nor accepted, along with the total number of such vulnerabilities in each file. This information helps you pinpoint the files that should be prioritized in your remediation efforts.