Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 9 · Reading 5 of 10

Prioritizing findings and proving remediation

Security+ SY0-801 · Objectives 4.3

A deployment ticket is green. The scanner still sees the affected component on the public service. The engineer believes the scanner is wrong, and the analyst believes the patch failed. What evidence would let both people resolve the disagreement?

Turn discovery into a scoped finding

An authenticated scan can inspect installed packages. An unauthenticated scan approximates what is visible from a particular network location. Source review can identify vulnerable patterns before deployment, and cloud posture tools can find unsafe permissions or exposed storage. Compare scan coverage with address management and asset inventory. Record the identity, version, location and confidence of each observation. Some operating system vendors backport fixes without adopting an upstream version number. Check their advisory before escalating a version-only match.

Deduplicate findings against a stable asset and component identity. Start priority assessment with technical severity, then add reachability, current threat activity, privileges, data sensitivity and service dependencies. A publicly exposed portal with credible exploitation reports may need attention before an isolated higher-scoring test image. Assign a named owner and deadline. An exception requires an approving risk owner, a compensating control, an expiration date and a way to verify the control.

Verify the outcome, including recurrence

Remediate at both the source and the deployed instance. Rebuilding a container from a corrected base image leaves the old running container unchanged until deployment. Compare the running image digest with the approved release, check service health and repeat an authorized defensive check from the original observation point. Track regressions when an older template or recovery snapshot is restored.

Report aging by priority, exception expiry and verified closure. A falling raw count can reflect missing credentials or decommissioned scanners. For an externally reported issue, acknowledge the reporter through the disclosure process, limit sensitive details to authorized recipients and coordinate the advisory and fix with the relevant parties. Preserve the connection between the initial report, affected builds and closure evidence.

Read the history before counting a reopening

Consider a ticket that closed after the running service was patched and later reappeared on a replacement instance. The first closure may have been technically correct at the time. A stale recovery image can recreate the problem later. Distinguishing recurrence from a finding that was never fixed changes who must act. One points toward the source of future deployments, the other toward the initial verification process.

Preserve the observations for both dates and match the service to the actual instance identifiers. A later incident review can then ask whether the repair addressed both the current exposure and the process creating new systems. That is more informative than counting the same identifier twice and declaring that the team has fallen behind.

Walk the request to the running copy

A load balancer can send users to several instances. One may still use the previous image while the dashboard shows the new template as the default. Compare stable instance identities and observed builds across the service, then match the scanner’s observation point to a particular running instance. Check the vendor's release information if package versions alone are ambiguous. Preserve the initial observation and verification result together. If a future recovery recreates the vulnerable instance, that history helps the team identify which deployment source still needs correction.

Remediation evidence chain

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

1. Advisory

Advisory lists a vulnerable component in build 8.

2. Inventory

Change ticket records an update to the deployment template.

3. Verification

Running production instance still reports build 8.

Apply the reading

How could a corrected deployment template leave production vulnerable?

Compare your reasoning

A previous instance may still be serving traffic. Verify running versions and then check the source used for replacement.