A company upgraded a hosted vulnerability scanner to the latest version, and now tickets are not being created to assign critical vulnerabilities. After confirming the ticketing issue, all the scanning services are confirmed to be running on the VM. Which of the following is the MOST likely cause and best method to fix the issue?

Question

Accepted Answer

D. There is an application compatibility issue. Roll back to the previous working backup. Because the upgrade is the only change made and scanning services are confirmed operational, the broken ticket creation points to a compatibility issue between the new scanner version and the ticketing system integration - rolling back to the previous working backup immediately restores the known-good configuration without requiring further diagnosis of the new version's bug.

Answer

A. There was an IP change to the VM. Make changes to the server properties. An IP address change would disrupt all network-dependent scanner functions and connectivity, not solely ticket creation, and would have been apparent before confirming services are running.

Answer

B. The upgrade has a bug Reboot the server and attempt the upgrade again. Rebooting and re-attempting the same upgrade would not resolve a compatibility bug introduced in the new version - it would reproduce the same broken state.

Answer

C. The vulnerability scanner is on a different subnet. Open the ports, and it will reconnect. A subnet or firewall port issue would prevent the scanner from communicating with the ticketing system entirely from the start, and is unrelated to the upgrade event that triggered the problem.

A company upgraded a hosted vulnerability scanner to the latest version, and now tickets are not being created to assign critical vulnerabilities. After confirming the ticketing issue, all the…

Question

Options

How the community answered

Why each option

Topics

Community Discussion