Help Center
Contact us

Remediation Process Best Practices

On this page

What You'll Learn on This Page

This page outlines best practices for executing and managing the remediation process within your RADAR environment. It provides guidance on prioritizing mitigation efforts, implementing corrective actions efficiently, and collaborating effectively with your mitigation vendors. Following these practices helps ensure that remediation activities are precise, minimally disruptive, and fully aligned with your existing mitigation capabilities.


Apply Fixes at the Most Upstream Layer

During validation and remediation, always implement fixes at the most upstream security layer relevant to the attack vector, and extend remediation to downstream layers only when necessary. Addressing issues upstream ensures that malicious traffic is mitigated as early as possible in the traffic flow, reducing the load on downstream components and minimizing the potential for collateral impact. This approach improves overall efficiency and maintains optimal protection coverage across the environment.


Start with the Simplest Corrective Actions

Initiate remediation by applying the most straightforward corrective measures first such as configuration tuning, rule updates, or threshold adjustments before introducing more complex changes.
Beginning with low-impact actions allows faster validation, limits potential disruption to production services, and often resolves the issue without requiring major policy modifications. MazeBolt Professional Services recommends confirming that basic mitigations are fully optimized prior to implementing advanced configurations.


Collaborate with Vendors Using Targeted Mitigation Techniques

When working with your mitigation vendor, avoid broad or aggressive methods such as wide-scale traffic filtering or rate limiting, as these may create false positives and disrupt legitimate traffic. Instead, collaborate with the vendor to apply precise and advanced mitigation techniques that directly address the specific security layer. Targeted remediation ensures accurate protection without degrading service quality and supports a data-driven, cooperative improvement process with the vendor.


Fine-Tune Activation Thresholds Instead of Increasing Attack Intensity

In some remediation scenarios, teams may be tempted to increase the simulated attack rate when an attack vector continues to bypass mitigation or when protection results remain Partially Protected or Vulnerable. The idea is that by generating higher volumes of malicious traffic, they can “force” the mitigation systems to trigger their defenses or expose thresholds that appear too permissive.

Rather than increasing the attack rate during testing, adjust mitigation activation thresholds to achieve the desired level of protection. Fine-tuning thresholds allows controlled testing that preserves the integrity of mitigation systems while still validating their responsiveness under realistic conditions. This method delivers a more reliable understanding of system performance without introducing unnecessary risk.


Evaluate Existing Mitigation Capabilities Before Expanding Services

Before committing to additional vendor services or product upgrades, assess the full capabilities of your current solution. Many protection gaps can be closed simply by optimizing existing configurations, adjusting thresholds, or enabling features that may not yet be active. Reviewing your current setup with your mitigation vendor or internal security team ensures that all available resources are fully utilized before additional investments are made. This approach helps maximize the effectiveness of your existing deployment and prevents unnecessary operational costs.

Was this article helpful?

Need further assistance? Contact support