About Remediation Objectives

Remediation Objectives help you set a clear scope, schedule, and target value for a failing metric. They allow you to track progress over time, ensuring you stay on schedule and meet your target efficiently.

Objectives can be high-level organizational priorities such as Increase CMDB coverage to 99% or Reduce the average time to patch from 16 days to 7 days or have a more specific operational focus such as Remove all detections of Log4Shell from Critical devices by the end of the quarter.

Objective tracking allows you to understand your progress and if you are on track to achieve the target in the chosen schedule.

Demo

Glossary

Use cases

Vulnerability backlog

Coverage improvement

Coming Soon

Control Check resolution

Coming Soon

Zero Day Vulnerability response 

Coming Soon 

FAQ

How is progress calculated?

The progress of an Objective is your current position between the start and target state.

• Example: start value: 100, target value: 50 current value: 75, Progress: 50%.

If your current value goes in the opposite direction of the target value from the start value, then while this is negative progress, we display it as 0%.

A target can either be above or below the start value depending on the direction, however progress will always be positive progress towards the target.

Progress is dynamically calculated on request, so if historic data changes progress can change as well.

Formula used to calculate progress:

targetChange = target - start
actualChange = current - start
progress = actualChange / targetChange
progressAboveZero = if progress >= 0 then progress else 0

Fixed vs Dynamic scope?

Objectives uses a dynamic scope rather than fixed scope. This means that if you start an objective to remove all detections of a particular vulnerability and there are new detections after you create the Objective, then these will still be added to your Objective. This can cause the progress of your Objective to get worse before getting better.

• Example: Your Objective is to remove all Log4Shell detections, and it starts with 100 detections. A week into the objective, you have resolved 20 detections but there have been 10 new detections. This means that you still have 90 to resolve your target.
• Example: Your Objective is to increase CMDB coverage from 90% to 100% with a population of 100 devices. You add the 10 missing devices that were missing at the beginning of the Objective, but 20 new devices are added to your estate and are missing from the CMDB. The progress of your Objective looks to have gotten worse even though you have remediated 10 devices.

What happens when an Objective is finished?

When an Objective is complete, whether it succeeds or fails, you will see the value, progress, burn down chart and remaining assets as of the end date of the Objective. The schedule can still be updated to extend the run time of the Objective if necessary.

What are the possible Statuses?