Preview
This guide is a preview. Its content may change.
Managing Tasks (Statuses and Due Dates)#
When You Need Help
A task is a ticket for managing your response to "one vulnerability found on one server." Using statuses correctly helps you make sure nothing falls through the cracks.
FAQ#
A. I updated the software, but the task doesn't change to “Patch Applied”
Check the "Patch Availability" column. For details, see item A in Understanding Detection Results (the Vulnerability List).
B. Which status should I use for vulnerabilities that don't need a response?
If you can determine that you're not affected, use "Not Affected." If you reduced the risk in another way, use "Workaround." There are four resolved statuses you can select manually. "Patch Applied" is set automatically by a scan and cannot be selected manually.
C. What should I do with vulnerabilities that didn't make it into “Important CVE”?
You don't need to do anything. "Important CVE" is a list of vulnerabilities with the status New that are not hidden, narrowed down by your own rules. Leave the ones that didn't make it in as "New" and review them periodically. If you review one and decide not to address it now, set it to "Defer (DEFER)" so that a record of your decision is kept. When you start working on it, change it back to "Ongoing."
Use "Hide" for items you'll never need to look at again, such as those outside your management scope. For tasks whose SSVC decision is Defer, you can use SSVC Triggers & Actions to automatically set the status to "Defer (DEFER)." If you also configure a setting that returns the status to "New" when the decision rises to Immediate or Out-of-Cycle, you won't miss items that have become urgent (SSVC Triggers & Actions). Use Automatic Ignore Settings only for items outside your management scope.
D. I want to make checking due dates a habit
Add the tasks assigned to you and the tasks past their due dates to your daily check. For how to use FutureVuls from an operator's point of view, see How to Use from a Field Operator's Perspective.
Troubleshooting#
If this page doesn't solve your problem, contact us through the support contact form with the task in question, the CVE-ID, and the behavior you expect.