Recurring Vulnerability Logging Rules

Once a vulnerability is resolved, there’s still a chance it might resurface in a future release. This can happen if a fix gets undone (for example, by a code rollback) or if a new configuration doesn’t work as intended, reintroducing the issue. To handle such cases, Strobes allows you to configure a Vulnerability Logging Rule for recurring vulnerabilities. This setting defines what the platform should do when a previously resolved vulnerability is detected again – either log it as a new issue or reopen the original one.

Logging Rule Options

Strobes provides two options for how recurring vulnerabilities are logged. You can choose the option that best fits your workflow:

• Create a new vulnerability ticket: If a previously fixed vulnerability reappears, Strobes will log it as a completely new vulnerability ticket. The recurring issue is treated as a fresh finding, with its state set to ‘New’ (just like any newly discovered vulnerability).
  
   
• Reopen an existing vulnerability ticket (Resolved state): If a vulnerability that was marked ‘Resolved’ resurfaces, Strobes will reopen the original vulnerability ticket. The ticket’s state will change back to ‘New’, making it active again for triage as if it were a new issue.
  

In the Vulnerability Logging Rules settings page, you can see these two choices presented as radio button options. The page provides a brief description of the feature at the top and then lets you choose either to create a new ticket or to reopen a resolved ticket as the logging rule. Simply select the radio button for your preferred option – Strobes will apply that choice whenever a vulnerability reoccurs.

How to Configure

Follow these steps to configure the recurring vulnerability logging rule for your organization:

1. Navigate to Settings and click ‘Vulnerability Logging Rules’.
   
    
2. Select the radio button for your preferred logging option (either ‘Create a new vulnerability ticket’ or ‘Reopen an existing vulnerability ticket that is in Resolved State’).
   
    

Once you’ve made your selection, the setting is saved automatically. Going forward, whenever the same vulnerability is reported again, Strobes will use the chosen rule – creating a new ticket or reopening the original one – according to your configuration.