> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zero-x.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# 1.6 Reports

title: "Reports"
description: "Generate and review security, compliance, vulnerability, inventory, remediation, and other reports in Zero-X Cloud."

## Overview

The **Reports** module in Zero-X Cloud provides a centralized location for generating and reviewing different types of security and compliance reports.

Reports help users analyze security findings, vulnerabilities, cloud inventory, compliance status, remediation activity, SLA performance, and software dependencies.

The Reports page provides the following report types:

* **Licenses & SBOM**
* **Vulnerability Report**
* **SCA Report**
* **Compliance Report**
* **Jira Report**
* **Remediation Report**
* **SLA Report**
* **Security Findings Report**
* **Inventory Report**

***

# Access Reports

To access the Reports module:

1. Sign in to **Zero-X Cloud**.
2. From the left navigation menu, select **Reports**.
3. The Reports dashboard opens.
4. Select the report you want to generate or view.

***

# Reports Dashboard

The Reports dashboard displays available report types as individual cards.

Each report card contains:

* Report name
* Report description
* Report-specific information

Select the required report card to continue.

***

# Report Types

## 1. Licenses & SBOM

The **Licenses & SBOM** report provides information about open-source software licenses and software components identified in connected repositories.

### Purpose

Use this report to:

* Identify open-source licenses.
* Review software component information.
* Analyze potential license-related risks.
* Export license information.

### Available Information

The report can provide:

* License information
* Software component information
* Repository-related data
* Potential license risks

License data can also be exported to a **CSV** file where supported.

### Steps

1. Open **Reports**.
2. Select **Licenses & SBOM**.
3. Select the required repository or data source.
4. Configure the available report options.
5. Generate the report.
6. Review the license and SBOM information.
7. Export the data when required.

***

# 2. Vulnerability Report

The **Vulnerability Report** provides a detailed view of vulnerabilities identified in code repositories.

### Purpose

Use this report to understand:

* Total vulnerabilities
* Vulnerability severity
* Security findings
* Repository vulnerability distribution

### Steps

1. Open **Reports**.
2. Select **Vulnerability Report**.
3. Select the required repository or data source.
4. Configure the available filters or options.
5. Generate the report.
6. Review the vulnerability findings and severity breakdown.

***

# 3. SCA Report

The **SCA Report** provides a detailed **Software Composition Analysis (SCA)** report for repositories.

It helps users identify vulnerabilities associated with software dependencies.

### Purpose

Use the SCA report to:

* Review software dependencies.
* Identify dependency vulnerabilities.
* Analyze vulnerability severity.
* Understand the security posture of third-party components.

### Steps

1. Open **Reports**.
2. Select **SCA Report**.
3. Select the required repository.
4. Configure the available report options.
5. Generate the report.
6. Review dependencies and associated vulnerabilities.
7. Review the severity breakdown.

***

# 4. Compliance Report

The **Compliance Report** provides detailed information about compliance checks performed against connected data sources.

### Purpose

Use the report to:

* Review compliance status.
* Identify failed compliance checks.
* Review individual compliance controls.
* Analyze security compliance posture.

### Steps

1. Open **Reports**.
2. Select **Compliance Report**.
3. Select the required data source or account.
4. Configure the available compliance options.
5. Generate the report.
6. Review the overall compliance status.
7. Review individual compliance checks.

***

# 5. Jira Report

The **Jira Report** provides reporting information for Jira-related security and repository data.

The report can include information related to:

* Code repositories
* Cloud data sources
* Accounts
* Severity mappings
* Jira-related findings

### Steps

1. Open **Reports**.
2. Select **Jira Report**.
3. Select the required repositories or cloud data sources.
4. Configure the available options.
5. Generate the report.
6. Review the generated Jira information.

***

# 6. Remediation Report

The **Remediation Report** provides information about resolved security findings and remediation activity.

### Purpose

Use the Remediation Report to:

* Track resolved security findings.
* Review historical remediation activity.
* Monitor remediation efforts.
* Understand security posture improvements over time.

### Steps

1. Open **Reports**.
2. Select **Remediation Report**.
3. Configure the required accounts, resources, dates, or other available filters.
4. Generate the report.
5. Review resolved findings.
6. Review historical remediation activity.

### Recommended Use

Use the Remediation Report after performing security remediation to verify and track the progress of security improvements.

***

# 7. SLA Report

The **SLA Report** provides information about Service Level Agreement compliance for security findings.

### Purpose

Use the SLA report to track:

* SLA compliance
* Findings resolved within SLA
* Findings that breached SLA
* Mean time to resolution
* Resolution performance by severity

### Steps

1. Open **Reports**.
2. Select **SLA Report**.
3. Configure the required reporting period.
4. Select the required severity or finding filters where available.
5. Generate the report.
6. Review SLA compliance.
7. Review within-SLA and breached findings.
8. Review mean time to resolution.

***

# 8. Security Findings Report

The **Security Findings Report** provides a detailed overview of security findings identified across connected resources.

### Purpose

Use this report to understand:

* Total security findings
* Finding severity
* Resolved findings
* Security posture
* Resolution percentage

### Steps

1. Open **Reports**.
2. Select **Security Findings Report**.
3. Select the required data source, account, or resource.
4. Configure the available filters.
5. Generate the report.
6. Review the total findings.
7. Review findings by severity.
8. Review the resolved percentage.

***

# 9. Inventory Report

The **Inventory Report** provides a detailed overview of assets discovered across connected environments.

It can provide visibility into:

* Cloud assets
* Code assets
* Kubernetes assets
* Asset distribution
* Security posture

### Steps

1. Open **Reports**.
2. Select **Inventory Report**.
3. Select the required cloud account, data source, or environment.
4. Configure the available report options.
5. Generate the report.
6. Review the inventory information.
7. Analyze the asset breakdown and security posture.

***

***

# Choosing the Right Report

| Report | Primary Purpose |
| - | - |
| **Licenses & SBOM** | Review software components and open-source licenses |
| **Vulnerability Report** | Analyze repository vulnerabilities |
| **SCA Report** | Analyze dependency vulnerabilities |
| **Compliance Report** | Review compliance status and checks |
| **Jira Report** | Review Jira-related repository and cloud security information |
| **Remediation Report** | Track resolved findings and remediation activity |
| **SLA Report** | Monitor SLA compliance and resolution performance |
| **Security Findings Report** | Analyze security findings and severity |
| **Inventory Report** | Review cloud, code, and Kubernetes assets |

***

# Best Practices

## Before Generating a Report

* Confirm that the required data source is connected.
* Select the correct repository, account, or environment.
* Configure the required filters.
* Select an appropriate reporting period when available.
* Confirm that the required scan or data collection has completed.

## While Reviewing a Report

* Check the total number of findings.
* Review severity distribution.
* Investigate critical and high-severity findings.
* Compare resolved and unresolved findings.
* Review trends or historical information when available.

## After Generating a Report

* Download or export the report when required.
* Share the report with relevant security or compliance teams.
* Track remediation activities for unresolved findings.
* Retain reports required for audit or compliance purposes.

***

# Summary

The **Reports** module provides a centralized reporting area for analyzing security and compliance information in Zero-X Cloud.

The available reports cover:

* Software licenses and SBOM
* Vulnerabilities
* Software dependencies
* Compliance
* Jira-related information
* Remediation
* SLA performance
* Security findings
* Asset inventory

The standard process is:

**Open Reports → Select Report → Configure Scope → Generate → Review → Export/Download**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.