> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/analysing-scan-results.md).

# Analysing Scan Results

Use results pages in this order: **Activity**, **Analysis**, **Attack Paths**, **Exploit Graph**, then **Reports**. For a Web domain, **Analysis** also shows how each run went, so you can often start there.

## 1. Confirm the Scan Finished

Open **Activity -> Activity**.

Check:

* module status;
* failed or cancelled steps;
* max runtime cancellations;
* agent disconnects;
* browser session failures;
* target blocking or rate-limit events;
* partial cloud collection errors.

Do this before judging coverage. A partial run can still produce findings, but it should not be treated as complete coverage.

{% content-ref url="/pages/QJ9ahgjtOWQNnN87Ivzs" %}
[Activity](https://copilot-docs.bugbase.ai/enterprise/activity.md)
{% endcontent-ref %}

## 2. Review Analysis

Open:

* **Modules -> Web Assessment -> Analysis**, or
* **Modules -> Network Assessment -> Analysis**, or
* **Modules -> Code Assessment -> Analysis**.

**Analysis** replaces the former **Statistics** pages. Old **Statistics** links open **Analysis**.

For Network and Code, **Analysis** shows the statistics for your assessments: findings, severity, categories, affected targets, and, for network and cloud assessments, hosts, services, cloud resources, identities, secrets, and compromise indicators; for code assessments, repositories, vulnerable code paths, dependency risk, leaked secrets, and inventory coverage. See [Statistics](https://copilot-docs.bugbase.ai/enterprise/modules/statistics.md).

For Web, **Analysis** starts with a list of your domains. Select one to open its page.

### Web Domain List

<figure><img src="https://232193438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwolEZzMm5QD9NoFKutSj%2Fuploads%2Fgit-blob-7111a820783a3b006b3c2075953e5797c1e32d76%2Fanalysis-domain-list.webp?alt=media" alt="Web Analysis domain list with columns for Domain, Vetting, Activity over the last 28 days, Alerts as pills, Findings and Last run, and filters All, Scanning, Alerts, Vetting and Needs changes"><figcaption><p>Each web domain in the workspace, with its vetting status, recent activity, and alerts.</p></figcaption></figure>

Each row shows:

| Column                     | What it shows                                                                                                                                                                                     |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Domain**                 | The domain, with **Scan in progress**, **Vetting in progress**, **No scans yet**, or how many runs it has had since its first scan.                                                               |
| **Vetting**                | The latest vetting result, such as **Not vetted**, **Configured**, **Configured · 2 to fix**, **Needs changes**, **Not scannable**, or the run in progress. Shown when AI configure is available. |
| **Activity, last 28 days** | One bar per day: **Scan runs that day**, **A run with an alert**, **A failed run**, or **Running**. A thin line under a day marks a vetting run, amber when it needed changes.                    |
| **Alerts, last 28 days**   | One pill per kind of alert: **Needs attention**, **Run failed**, **Partial discovery coverage**, or **Outside whitelist**. Hover a pill for the detail.                                           |
| **Findings**               | Open findings by severity.                                                                                                                                                                        |
| **Last run**               | When the domain was last scanned, or **Running now**.                                                                                                                                             |

Use the filters **All**, **Scanning**, and **Alerts**, plus **Vetting** (a run in progress) and **Needs changes** (**Needs changes** or **Not scannable**) when AI configure is available, and search by domain name. Select a row to open the domain. A row with an alert opens on the run that raised it.

### Web Domain Page

The domain page brings together everything about one domain. At the top, it shows whether vetting or a scan is in progress, when the domain was first scanned, how many vetting runs and scans it has had, and its open findings. **View findings** opens them in **Attack Paths**. **All domains** returns to the list.

#### Vetting

When AI configure is available, the **Vetting** card shows the domain's vetting runs.

<figure><img src="https://232193438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwolEZzMm5QD9NoFKutSj%2Fuploads%2Fgit-blob-6d3d8b3ded80fbdce25f403cde3ed2d3c6dcded5%2Fanalysis-domain-vetting.webp?alt=media" alt="Vetting card on a domain page with Update inputs in Run Assessment, the run picker showing Run 2, Configured with limitations, its date and latest, your note, three saved scan configurations marked Ready, and All checks and accounts"><figcaption><p>Pick a vetting run to see what it saved and what it left to fix.</p></figcaption></figure>

* **Run picker.** Shows each run as **Run N · outcome · date**, with **(latest)** on the newest. Pick an earlier run to see its results, and **Back to the latest run** to return.
* **Scan configurations.** For a configured run, one line for Unauthenticated and one per account, with the phases it covers, the starting path, and **Ready** or **Not ready**.
* **Things to fix.** **Vetting run N left N things to fix** lists each item with what to update. Select **Update inputs and vet again** to open **Run Assessment** with the run's inputs. Until then, scans use the current configuration.
* **All checks and accounts.** Expand it to see each check's state and what it found, the **Accounts** vetting used, and how many account blocks you gave. Accounts are marked **Your account** or **Created by vetting on your site**.
* **Actions.** **Cancel** stops a run in progress. **Start scan** starts the scan for a run that ended **Scannable with limitations**, or for a scannable run whose scan did not start. **Update inputs in Run Assessment** opens the wizard with the latest run's inputs, and **Configure in Run Assessment** appears when the domain has not been vetted yet.

See [AI Configure and Vetting](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-a-web-assessment/ai-configure-and-vetting.md).

#### Scan Runs

<figure><img src="https://232193438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwolEZzMm5QD9NoFKutSj%2Fuploads%2Fgit-blob-ec083ba3d24461155b9f56e79e0e72f2145e938f%2Fanalysis-domain-timeline-stats.webp?alt=media" alt="Domain page with the Scan runs timeline in Discovery and Assessment lanes, the 7 days, 30 days, 90 days and All range buttons, the run list, and the Statistics panel below"><figcaption><p>Select a run on the timeline or in the list to see its outcome and alerts.</p></figcaption></figure>

* **Timeline.** Discovery and Assessment runs on a time axis, colored **Running** or **Failed** where it applies. Choose **7 days**, **30 days**, **90 days**, or **All**.
* **Run list.** Filter **All runs**, **Discovery**, or **Assessment**. Each row shows the run, its session (**Unauthenticated** or the browser session), the result, when it started, and how long it took.
* **Run detail.** The selected run shows:
  * its result: **Running**, **Completed**, **Completed with gaps**, **Incomplete**, **Failed**, or **Cancelled**;
  * its outcome: what happened, and the next step when there is one, such as running the scan again or vetting the domain again, with **Open Run Assessment**. When BugBase needs to look, the outcome ends with "Contact <queries@bugbase.ai> with reference: ";
  * its alerts, each with an action: **View activity** for a failed run, **Show domains** and **Scan** for domains found but not followed, and **Review whitelist** for domains outside the whitelist;
  * **New webpages** and **New user flows** for Discovery, or **Findings** and **Critical and high** (or **P1 and P2**) for Assessment, with **View findings in Attack paths**.

#### Top Findings and Statistics

**Top findings** lists the domain's most severe verified findings. **View all N in Attack paths** opens the rest.

**Statistics**, at the bottom of the page, shows the domain's statistics directly. Filter them by **Session**, **Found**, and **Findings**. See [Statistics](https://copilot-docs.bugbase.ai/enterprise/modules/statistics.md).

## 3. Triage Attack Paths

Open:

* **Modules -> Web Assessment -> Attack Paths**, or
* **Modules -> Network Assessment -> Attack Paths**, or
* **Modules -> Code Assessment -> Attack Paths**.

Start with Critical and High findings. For each finding:

1. Open the finding detail page.
2. Read the summary, evidence, AI reasoning, remediation, and references.
3. Open the attack path drawer.
4. Confirm the graph chain makes sense.
5. Mark the finding Valid, False Positive, or Duplicate.
6. Retest when your team needs fresh verification.

For code assessments, also review the repository, branch or commit, affected files, and whether a fix can be suggested or opened as a pull request.

For cloud assessments, confirm the provider, discovered cloud scope, affected resource, effective identity, evidence, and cleanup status.

{% content-ref url="/pages/Qq4eYhCnXnWRSOdpI5cq" %}
[Attack Paths](https://copilot-docs.bugbase.ai/enterprise/modules/attack-paths.md)
{% endcontent-ref %}

## 4. Inspect the Exploit Graph

Open **Dashboard -> Exploit Graph**.

Use the graph to answer:

* What did discovery find under this root entity?
* Which assets led to the finding?
* Which browser session, trajectory, test case, or network host was involved?
* For code assessments, which repository, branch or commit, dependency, file, or inventory component was involved?
* For cloud assessments, which identity, policy, resource, network, or trust relationship created the path?
* Are there related findings on the same path?
* Does the path cross a boundary your team considers out of scope?

{% content-ref url="/pages/SVOgW3WWDsCNP6N3NZ7R" %}
[Exploit Graph](https://copilot-docs.bugbase.ai/enterprise/exploit-graph.md)
{% endcontent-ref %}

## 5. Generate Reports

Open **Reports** after triage is complete.

Before generating:

* resolve obvious false positives;
* mark duplicates;
* confirm report root entity;
* decide whether full output is needed;
* choose severity filters for comprehensive reports.

{% content-ref url="/pages/5R9A4WOfbwrPI78VKDKg" %}
[Reports](https://copilot-docs.bugbase.ai/enterprise/reports.md)
{% endcontent-ref %}

## What Not to Miss

* Authenticated findings should identify the browser session or role used.
* Code assessment findings should identify the repository, branch or commit, and affected file or dependency.
* Code assessment inventory should be reviewed from **Modules -> Code Assessment -> SBOM** before sharing SPDX, CycloneDX, or AI-BOM exports.
* Cloud findings should identify the provider scope, effective identity, affected resource, and rollback or cleanup status.
* Network findings may require cleanup or credential rotation even if they are later marked duplicate.
* A clean scan is not proof of no risk if discovery, browser sessions, or agents failed, or if the run's outcome is **Completed with gaps** or **Incomplete**.
* Scheduled scans should be reviewed against approved scope and browser-session validity.
