Explore the expanded editions. Read every sample free before choosing a book.

Interview practice / 2 MIN READ

Technical severity and remediation priority answer different questions

Compare two fictional findings under a supplied local rule without treating a headline score as a complete risk decision.

Server racks and network cabling inside a data center
Illustrative photograph by imgix on Unsplash.
On this page

A vulnerability severity score is an input to a decision, not the complete remediation order for every organization. Priority also depends on the applicable policy and relevant evidence about the affected environment.

NIST's NVD explanation distinguishes CVSS severity from risk. FIRST's user guide explains the scoring framework and its context. This exercise supplies scores as fictional labels; it does not derive or validate CVSS vectors.

Read the original practice case

The exercise's local rule says: first escalate findings with corroborated active exploitation affecting an in-scope service; then assess other findings using exposure, business effect and available safeguards. This is a fictional rule, not a recommended universal remediation policy.

FindingSupplied severity scoreAdditional evidence
A9.8Lab asset; owner reports isolation, but the network evidence is pending
B8.1In-scope external service; packet corroborates active exploitation affecting that service

Under the supplied rule, B meets the first escalation condition. That does not make A harmless or change its supplied score. A's claimed isolation remains unverified, and its exposure needs prompt clarification through the responsible process.

Make the recommendation traceable

Write: “B meets the packet's active-exploitation condition for first escalation. A retains its supplied technical severity; its exposure is unresolved because isolation is asserted but not evidenced. Request the missing scope and exposure records and assign both findings to the appropriate owners.”

Do not invent a 24-hour fix deadline, likelihood percentage, financial loss or risk-acceptance authority. None is supplied. Escalating B first also does not mean all investigation or protective work on A must wait; actual parallel action depends on the authorized process and resources.

Revise when the record changes

Suppose new evidence shows A supports an in-scope service through a reachable management path. Remove “lab isolation” from the supporting rationale and reassess against the local rules. You still lack evidence of active exploitation of A, so do not manufacture it to justify urgency. Record precisely what changed and ask the authorized decision owner to resolve any priority conflict.

Your final note should preserve the rule, both score labels, the contextual evidence, missing information and the decision owner. It is a reasoning artifact, not a scan result or compliance opinion.

Use vulnerability-priority preparation to compare the free task with broader interview rehearsal. For a general recommendation structure, see the GRC decision memo.

PUT IT INTO PRACTICE

GRC Interview Case Workbook

Keep practicing how to explain an evidence-based decision with original cases and timed mock sessions.

Choose another free evidence, application or portfolio task