Skip to main content

📊 Dashboard – Reading & Understanding

The Dashboard provides a global overview of your security audit results.
It helps you quickly identify risks, track tested targets, and prioritize remediation efforts.

🔎 Key Sections​

1. Vulnerabilities by risk​

  • A gauge chart displays the total number of vulnerabilities detected (e.g., 187 Vulns).
  • Each color corresponds to a risk level (low → critical).
  • This allows you to quickly assess the overall security posture.

2. Hack-Score​

  • A graded scale (A → E) that represents the global security rating of your perimeter.
  • A (green) = very secure
  • E (red) = very vulnerable
  • Example: E – Very vulnerable means multiple high-risk issues have been detected.

3. Targets Summary​

On the top right, a quick status view of all monitored targets:

  • Total: number of declared targets (e.g., 104).
  • Risky: number of targets with confirmed vulnerabilities (e.g., 10).
  • Tested: number of targets already analyzed (e.g., 14).
  • Not Tested: targets not yet scanned (e.g., 90).
tip

This summary helps you track coverage:

  • Are all your assets included?
  • Which ones are still untested?
  • How many require urgent attention?

4. Targets at risk​

A detailed table of the riskiest assets, including:

  • Name: domain or subdomain (e.g., demo.testfire.net).
  • Perimeter: URL or description of the asset (e.g., http://demo.testfire.net/).
  • Type: type of target (e.g., DNS_NAME).
  • Created At: date when the target was added.

This section lists the most exposed systems so you can prioritize remediation.

📌 Example Interpretation​

In the screenshot:

  • 187 vulnerabilities have been found.
  • Global Hack-Score = E → Very vulnerable.
  • Out of 104 total targets, only 14 have been tested, while 90 remain untested.
  • The 10 risky targets (like demo.organization.net, demo.organization.com) require immediate action.

✅ Best Practices​

  • Focus first on risky targets (red zone in the Hack-Score + Targets at risk list).
  • Increase coverage by reducing the number of untested targets.
  • Track Hack-Score over time to measure the effectiveness of remediation.
  • Drill down into the Vulnerabilities tab for detailed technical findings.