# CSV Report

> What is Simulation Results - CSV Report in RADAR? The Simulation Results – CSV Report in RADAR is designed for technical teams that prefer working with

Part of the [MazeBolt Help Center](https://support.mazebolt.com/) › [Reporting and Analysis](https://support.mazebolt.com/reporting-and-analysis). Updated 2026-01-27. HTML page: https://support.mazebolt.com/reporting-and-analysis/csv-report

---

![](https://support.mazebolt.com/images/07627a32-8075-41d4-9fc4-39e4bf050380.png)

## What is Simulation Results - CSV Report in RADAR?

The Simulation Results – CSV Report in RADAR is designed for technical teams that prefer working with raw data. It provides a comprehensive view of all simulation results in your environment, including detailed simulation metrics and status indicators, in a structured CSV format. This report can be downloaded at any time, with the data reflecting the state of your environment at the moment of download.

## What You'll Learn on This Page

On this page, you’ll learn how to generate the Simulation Results CSV Report in the RADAR platform. The exported CSV file delivers a complete record of every simulation parameters, outcomes, and metrics, enabling you to analyze the findings and take the appropriate actions.

---

## Generating and Reviewing the Simulation Report - CSV

Follow these steps to generate your DDoS Simulation Report - CSV in the RADAR platform:

1. In the left-hand navigation menu, click  Reports.
2. Select **Simulations Results - CSV**.
3. Use the filter bar to select the Security Layer you want to include in the report, then click **Generate**.
4. In the generated report table, click **Download Report** to export the report.

![](https://support.mazebolt.com/images/7124722b-99c5-4d92-aea0-156c89731e4a.png)

### Review the Simulation Report - CSV

The Simulation Results – CSV Report is organized into 17 columns, with each column representing a specific aspect of your DDoS simulation data. In the following section, you’ll find a breakdown of each column to help you quickly interpret the insights and identify any required actions.

1. **Target Validator**
   Specifies the DDoS attack vector executed during the simulation.
2. **Attack Layer**
   Specifies the OSI layer (3, 4, or 7) to which the tested attack vector pertains.
3. **Status**
   Shows the latest simulation outcome: Protected, Partially Protected, Vulnerable or Unchecked.
4. **Priority**
   Specifies the remediation urgency for each attack vector group:
   - **BaseLine** vectors - High priority
   - **BaseLine Plus** vectors - Medium priority
   - **Complete Insight** vectors - Low priority

The **BaseLine** group is assigned **High priority** because it provides the broadest coverage across your available security mechanisms, delivering significant protection value with a minimal number of attack vectors.

5. **Security Layer**
   Identifies the security component tested during the simulation such as your Web Application Firewall (WAF), Content Delivery Network (CDN), or Customer Premises Equipment (CPE).
6. **Validator State**
   Indicates whether the specified attack vector is enabled on the Target.
7. **Target**
   Specifies the Target tested during the simulation.
8. **Port**
   Indicates the destination port number used in the simulation.
9. **IP Version**
   Specifies the Target's IP address version.
10. **Target Status**
    Indicates whether the specified Target is currently enabled or disabled for simulation.
11. **Test Start Date and Time**
    Specifies the exact date and time when the simulation began.
12. **Test End Date and Time**
    Specifies the exact date and time when the simulation ended.
13. **Test Rate**
    Specifies the simulation attack intensity, measured by the defined rate metric.
14. **Received Total**
    Specifies the total volume of simulated DDoS traffic received during the simulation.
15. **Sent Traffic**
    Specifies the total volume of simulated DDoS traffic generated during the simulation.
16. **% Passed**
    Indicates the percentage of simulated DDoS traffic that successfully bypassed the configured security layer.
17. **Had Deviation**
    Indicates whether a response time anomaly occurred, based on whether the measured response time exceeded the configured deviation threshold during the simulation.
