What is Remediation History Page in RADAR?
The Remediation History page in RADAR gives a clear, validated view of what actually improved in the DDoS protection posture - not just what was tested.
It allows teams to track which vulnerabilities were successfully closed after remediation and retesting, creating a direct link between mitigation actions and measurable protection outcomes.
Beyond visibility, it serves as an operational record where teams can document how issues were resolved, enabling structured knowledge sharing, easier collaboration with vendors, and faster future troubleshooting.
In practice, this page transforms remediation from a fragmented, manual process into a data-driven, traceable workflow, supporting continuous validation and ongoing improvement of the organization’s DDoS defenses
What You'll Learn on This Page
On this page, you’ll learn how to track remediation progress across your tested assets, identify which vulnerabilities were successfully resolved after retesting, and understand how protection status changes over time.
You'll also learn how to document remediation actions using the Remediation Details option and use this information for analysis, reporting, and collaboration with internal teams or mitigation vendors.
Reviewing the Remediation History Page
Follow these steps to review and document your DDoS simulation remediation in the RADAR platform:
- In the left-hand navigation menu, click Simulations.
- Select Remediation History.
Filter by Date Range
At the top of the page, at the Show Results by Date bar, you can filter the results by selecting a start (“From”) and end (“To”) date to define the desired date range.
If no filters are selected, the table will display the latest simulation results.
Apply Filters
Below the date range, you’ll find additional dropdown menus that allow you to narrow results by specific Event Names, Targets, Attack Vector Types, Security Layers tested within the simulation cycle or Previous Statuses. Once you’ve selected the relevant filters, click the Refine button to apply them.
View the Results Table
In the table below the filters, you’ll see all simulation results that were previously Vulnerable or Partially Protected and have changed their status to Protected. Each entry represents the outcome for a specific combination of Target, Attack Vector, and Security Layer tested during a simulation cycle.
• Click the Target Name to view its configuration details and adjust settings
• Click the Attack Vector to open its detailed entry in the MazeBolt Knowledge Base, which provides an in-depth technical breakdown of the vector’s behavior, traffic patterns, and potential impact on network components
Add Remediation Details
On the right side of each row, you’ll find the Remediation Details action button. Click this button to open a pop-up window for documenting how the vulnerability was resolved for the selected Target, Attack Vector, and Security Layer combination.
Use this form to capture the actions taken during remediation and provide context for the status change. This helps maintain a clear history of fixes and supports future analysis and collaboration.
The Remediation Details window includes the 3 following fields:
1. Method of Resolution
Select how the issue was resolved. This field describes the approach used to remediate the vulnerability (for example, configuration changes, infrastructure updates, or policy adjustments). Choose the option that best reflects the action taken:
- Deliberate Mitigation
The issue was resolved through a direct and intentional action taken to address the vulnerability (for example, updating WAF rules, modifying configurations, or applying a specific mitigation). - Accidentally Solved
The issue was resolved unintentionally as a result of unrelated changes. The fix was not specifically aimed at addressing this vulnerability. - Resolved on a Different Layer
The issue was resolved by an upstream security layer rather than by the layer originally tested. Use this option when the protection was provided by another mitigation layer in the traffic path. - Unknown
The reason for the resolution is not clearly identified. Use this option if it is unclear what change led to the improved protection status. - Other
The resolution does not fit into the predefined categories. Select this option if none of the above accurately describe the remediation approach.
2. Remediation Type
This field helps classify how the issue was resolved and supports analysis of mitigation patterns across your environment. Select the category that best describes the type of remediation applied:
- IP or Service Block
Blocking access to specific IP addresses, IP ranges, or service ports to prevent malicious traffic from reaching the Target. - Connection Handling / Timeout Configuration
Adjusting how the network or mitigation device manages incoming and existing connections (for example, connection limits, timeouts, or session handling). - WAF Rule Update
Modifying or updating Web Application Firewall (WAF) policies to detect and block malicious requests. - Threshold Activation / Adjustment
Adjusting the rate or threshold at which mitigation actions are triggered (for example, request rate limits or anomaly thresholds). - Attack Simulation Rate Adjustment
Changing the rate at which the attack was simulated to better align with mitigation thresholds or expected traffic conditions. - Rate Limiting / Traffic Throttling
Applying rate limits or throttling mechanisms to control the volume of incoming traffic and reduce the impact of high-rate attacks. - Mitigation Platform Configuration Change
Updating general configuration settings within the mitigation platform, such as tuning behavior, switching configurations, or modifying vendor-specific settings. - Challenge Mechanism – Layer 7
Enabling or adjusting application-layer challenges (such as redirect challenges or JavaScript challenges) to validate legitimate users. - Challenge Mechanism – Layer 4
Enabling or adjusting network-layer challenges (such as SYN cookie challenges) to validate connection legitimacy. - Signature-Based Protection Enablement
Activating mitigation mechanisms that block traffic based on known attack signatures. - Out-of-State Mitigation
Enabling mechanisms that block traffic which is not part of a valid or established connection. - Behavioral Protection Enablement
Activating mechanisms that detect and block traffic based on deviations from normal behavior patterns. - Application-Specific Protection Enablement
Applying mitigation actions tailored to the specific target application or service. - Invalid Packet Filtering
Blocking malformed or improperly structured packets that may indicate malicious activity. - Other
The remediation does not fit into the predefined categories.
3. Description
Enter a brief summary of the changes applied. Use this field to provide additional context, such as: what was changed, where the change was applied and any other relevant notes for future reference.
After completing the fields, click Save to store the remediation details. The information will be associated with the selected combination and recorded in the Remediation History page.
Once saved, the remediation details are added to the main table, providing visibility into the actions taken for each result.