Release Notes: January 2025
Explore What’s New from Cobalt This Month
DAST Release: Blackout Period
Problem
- Customers needed a way to pause DAST scans during maintenance, high-traffic events, or other sensitive times to avoid conflicts, performance issues, or inaccurate results. Previously, they had to manually pause scans + resume them later, which was inconvenient and could lead to missed vulnerabilities if scans weren’t restarted.
- Timestamps + inputs were set in UTC, which is not as accessible and required some extra thinkin’ to translate to local timezones.
Solution
- The Blackout Period feature (located in the target settings) allows customers to schedule specific times and days for scans to be automatically paused and resumed, eliminating the need for manual intervention.
- All timestamps + inputs within the DAST UI are now displayed to the user in their local timezone.
Benefits
- Convenience + Automation: No more manual stopping and starting of scans.
- Flexibility: Customers can define blackout periods that precisely match their needs.
- Continuous Security: Ensures critical security testing windows are maintained, as scans automatically resume.
- Efficiency: Prevents wasted time + resources on scans that might be affected by temporary events or maintenance activities.
- Peace of Mind: Customers can confidently schedule maintenance or other activities without worrying about disrupting their security scans or missing potential vulnerabilities.
For more information, have a look at our Blackout Period documentation.

Ticketing Integration for Carried Over Findings
Problem
Previously, our ticketing integrations would create new tickets for findings carried over by pentesters to new pentests, causing inconvenience for some customers who did not want multiple tickets for the same issue, especially larger clients.
Solution
We have introduced a configuration option at the pentest level that modifies the integration behavior to re-associate an existing ticket, if available, to the carried over finding. With this feature enabled, when a carried over finding is marked for pending fix:
- The existing ticket is unlinked from the original finding
- The existing ticket is linked to the carried over finding
- No new ticket is generated
Supported Integrations
- The Integration Builder
- Native Jira Cloud integration
- Native Jira Data Center (server) integration
Benefits
- Customer Flexibility: Clients who prefer not to have new tickets created for carried over findings can now opt-in to this feature.
- Customization Options: The ticketing integration behavior remains unchanged for customers who are comfortable with the current system and choose not to enable this functionality.
For more information, have a look at our Carried Over Findings documentation.
