CISM Information Security Program Practice Question
An organization's security program includes metrics to measure performance. Which metric BEST indicates the effectiveness of the vulnerability management process?
⚠ Common exam trap
Test-takers frequently confuse activity metrics (number of patches, scan coverage) with outcome metrics (MTTR), which is the only option that directly measures the effectiveness of closing vulnerabilities in a timely manner.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Mean time to remediate (MTTR) vulnerabilities
Mean time to remediate (MTTR) directly measures how quickly the organization closes the window of exposure after a vulnerability is identified. A lower MTTR indicates a more effective vulnerability management process because it reduces the risk window, whereas raw counts of vulnerabilities or patches do not reflect the timeliness or completeness of remediation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Number of vulnerabilities identified
Why it's wrong here
Counting identified vulnerabilities measures discovery volume, not whether they were remediated, so it says nothing about process effectiveness. It tempts because scanning output is easy to report, and a coverage metric for scanner tuning would make it correct.
- ✗
Number of patches deployed per month
Why it's wrong here
Patch counts measure activity, not risk reduction: deploying many patches says nothing about whether critical exposures were remediated within SLA or whether exploitability dropped. It is tempting because patch volume is easy to report and suits capacity or compliance tracking, such as evidencing patch cadence to an auditor, but effectiveness requires tracking remediation of identified vulnerabilities against risk and time targets.
- ✗
Percentage of systems scanned weekly
Why it's wrong here
Scanning coverage measures discovery activity, not whether identified vulnerabilities were remediated, so a fully scanned estate can remain unpatched. It is tempting because coverage is easy to automate and report, and would be correct for measuring vulnerability identification capability, but effectiveness demands remediation and time-to-fix metrics.
- ✓
Mean time to remediate (MTTR) vulnerabilities
Why this is correct
MTTR measures elapsed time from vulnerability discovery to remediation, directly reflecting how quickly the process reduces exposure. Unlike raw counts of findings or scan coverage, it captures the operational efficiency of the entire remediation workflow, making it the strongest indicator of whether the vulnerability management process actually works.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CISM question from scratch — 924 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CISM practice question is part of Courseiva's free ISACA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISM exam.