CFS210 Cyber Defense Fundamentals · CySA+ CS0-004 Bootcamp · PBQ Simulation 6

Interpreting CVSS v3.1 and Scanner Evidence

A practice performance-based question (PBQ) set at the fictional Tamberlin Health Network. Suggested time: 15 to 20 minutes.

How this simulation works

  1. Read the scenario, then open each exhibit tab. Use the evidence to complete the tasks.
  2. Select Submit answers when you finish. Each correct matching row or ordering position earns one point. For multiple-selection tasks, each correct selection earns one point and each incorrect selection subtracts one point, with a minimum of zero for that task.
  3. After submission, review the correct answers and explanations. Select Reset simulation to clear answers, feedback, tools, and the timer.
  4. The pacing timer is optional. You can inspect every exhibit after submitting. Practice scores use this activity's rubric.

CS0-004 objectives practiced:

  • 2.2 Interpret vulnerability-assessment output
  • 2.3 Use vulnerability data and context to prioritize remediation

All organizations, people, events, findings, and tool records in this activity are fictional. External addresses use documentation IP ranges and reserved .example names. Commands and network records are displayed as text only. The activity runs locally, saves no student data, and makes no network requests. Reference links open only when selected. This is practice and is not graded.

Pacing timer

Elapsed time:00:00

Scenario

The Tamberlin vulnerability team has four findings and one immediate production change window. Interpret the supplied CVSS v3.1 vectors, validate a banner-based finding, and select the work that meets the organization’s emergency policy.

Use the reference exhibit when needed. You do not need to calculate a CVSS score by hand.

Exhibits

  • All THN-V identifiers name fictional findings, not published vulnerability identifiers. The example advisory and package versions belong only to this case.
  • Emergency (48 hours): a validated finding has confirmed active exploitation against the organization, or an internet-facing asset has a base score of at least 9.0.
  • Standard (30 days): any other validated finding with an available fix. An isolated test system remains in scope for remediation.
  • False positive: evidence confirms the reported weakness is absent. Document validation before closing the finding.
  • The current production change window can address one finding immediately. Use the stated emergency criteria to select it. Available patches have passed the required compatibility tests.
  • This activity uses Common Vulnerability Scoring System (CVSS) v3.1 throughout. Its base score describes a weakness’s technical severity. The organization combines that information with exposure, business use, and exploitation evidence to decide work order.

Tasks

Task 1 (8 points)

Interpret each base metric in THN-V02’s vector.

Task 2 (4 points)

Assign the qualitative severity for each supplied base score.

Task 3 (1 point)

What does S:C in the original THN-V04 vector describe?

Task 4 (1 point)

What is the best disposition for THN-V04 after comparing S01, V01, and H01?

Task 5 (1 point)

Which finding should take the immediate production change window under the stated policy?

Task 6 (1 point)

An analyst proposes changing THN-V01’s published base score from 9.8 to 3.0 solely because this installation is isolated. What should the team do?
Reference links and simulation notes

These sources support the technical concepts. All case evidence was written for this practice activity. No external source is required to answer the tasks.

The four base scores were independently recalculated from the supplied vectors using the CVSS v3.1 base equations. No v4.0 metrics or scores appear in this activity.