Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 5 · Reading 4 of 5

When two findings disagree

Security+ SY0-801 · Objectives 4.3

A facilities engineer points to a completed change ticket. The maintenance portal still appears in a vulnerability report. Both people responsible for the records have done real work. Settling the disagreement requires more than choosing whichever tool looks more authoritative.

First establish whether the records describe the same thing

Write the service address, observed instance identity, collection time and scope of each record on separate lines. A portal might have a public gateway, two application instances and a background worker. A web banner can describe the gateway while an operating system package report describes the worker. An address might also have moved between devices. Before arguing about the version, establish whether the two sources even refer to the same component at the same time.

Suppose a vendor has backported a fix. Its package keeps the original upstream version but adds a vendor revision. A network banner may show the upstream version only. Look for the vendor advisory that names the affected and fixed revisions. A completed purchase or a downloaded package cannot establish that the running component uses the fixed revision. Ask for evidence from the deployed system and account for whether a restart or replacement was necessary.

Decide what would settle the question

Define the smallest authorized observation that could distinguish the plausible explanations. An authenticated package inventory might settle a version mismatch. A running process record might establish that an old library remains loaded after an update. A check from the original network location might confirm whether the exposed route was actually closed. Avoid repeating a disruptive test simply because the original finding was dramatic.

Record the confidence and the limit of your conclusion. “The current image contains the fixed library” is narrower than “all users now reach a corrected instance.” A service owner can act on that distinction by reconciling every active instance behind the gateway. If the supplier's information is incomplete, keep the finding under review, assign an owner and set a time to revisit it.

Identify who can close which part

The engineer can confirm a corrected package, the service operator can confirm which instance handled a request and the dispatcher can confirm that the portal still routes a maintenance ticket. These observations belong to different people. Place them in the same case with dates and stable identifiers. The vulnerability owner then has a basis for closure that survives a shift change. If the service later fails or a finding reappears, the original evidence helps narrow where to begin.

Report uncertainty without losing the issue

A false positive is a reported problem that the available evidence shows does not apply. An unverified finding is still an open question. A false negative can leave a real weakness entirely absent from the queue. Give these outcomes distinct labels in your report. A team that closes every uncertain result will look efficient while leaving the owner less informed. These disagreements ultimately bring you back to asset identity: what belongs to the service, who owns it and how current the evidence is.

The maintenance portal evidence board

Inspect the three records, then use the evidence to answer the question.

1. Scanner identity

Probe observed server P4 reporting upstream release 8.

2. Release record

Supplier confirms its fixed package is 8-r12.

3. Live service

Authenticated inventory identifies P4 as 8-r10.

Apply the reading

What observation would settle a disagreement about two running instances?

Compare your reasoning

Match stable instance identities and running package revisions with the original observation point and supplier advisory.