Skip to main content
Remediation Due Date
Updated over a week ago


In the fast-paced realm of cybersecurity, timely vulnerability remediation is crucial. The Remediation Due Date feature is tailored to enhance vulnerability management processes. This feature allows managers and users to set specific due dates for resolving vulnerabilities.

Understanding the Value

Remediation Due Date enables remediation campaign creators to set and enforce internal remediation timelines to ensure vulnerabilities are remediated efficiently, reducing the organization's exposure to potential security breaches. This feature is especially beneficial for managers and users who wish to assign internal deadlines to their teams or specific individuals responsible for patching vulnerabilities.

Support and Limitations

This feature is available only for:

  • Manual remediation campaigns via Email

  • Automation/playbook campaigns via Email

What's the difference between Remediation Due Date vs. SLA Policies?

The SLA feature and the Remediation Due Date feature in the Vulcan Platform serve distinct purposes in vulnerability management.

While SLA measures against broad security commitments and policy-driven deadlines, Remediation Due Date offers targeted, adaptable vulnerability remediation planning.

  • The SLA feature in the Vulcan Cyber Platform sets organization-wide timelines based on severity levels for when vulnerabilities should be addressed. It starts a countdown from the discovery date to ensure compliance with security policies. The feature emphasizes adherence to security policies by marking vulnerabilities as "Exceeding" if they are not resolved within the predefined time frame.

  • The Remediation Due Date feature allows Vulnerability Managers to assign specific due dates for each vulnerability within a campaign, tailored to operational needs and priorities. It focuses on internal task management and prioritization without directly tying to organizational compliance standards.

Did this answer your question?