I am trying to understand what is the difference between continuous monitoring and just running a vulnerability report or creating a dashboard? Can anyone shed some light on this?
I am trying to understand what is the difference between continuous monitoring and just running a vulnerability report or creating a dashboard? Can anyone shed some light on this?
Continuous Monitoring layers a monitoring and notification layer on top of the detections you get from your sensors (scans, agents, etc.). CM enables you to define sets of systems to monitor, define events you want to watch for (via rulesets) and define who gets alerts at what thresholds. Examples of how people use it are to monitor for unexpected hosts / OSes, expiring SSL certificates, etc.
There's more detail on the Qualys Continuous Monitoring, especially starting in the "Combine continuous monitoring and vulnerability management" section.
Reports and dashboards don't include the alerting functionality, so CM is a good complement.
Thanks a lot, this is very helpful. I didn't even think about alerting for unexpected hosts. I am going to set that up now.
Continuous Monitoring layers a monitoring and notification layer on top of the detections you get from your sensors (scans, agents, etc.). CM enables you to define sets of systems to monitor, define events you want to watch for (via rulesets) and define who gets alerts at what thresholds. Examples of how people use it are to monitor for unexpected hosts / OSes, expiring SSL certificates, etc.
There's more detail on the Qualys Continuous Monitoring, especially starting in the "Combine continuous monitoring and vulnerability management" section.
Reports and dashboards don't include the alerting functionality, so CM is a good complement.