Troubleshooting Server Registration and Cloud Integration#

When You Need Help

Server registration is where we receive the most inquiries. Check how you registered and what your environment is, then look through the questions below.

Check First#

Registration method: Scanner, paste, ECR/Docker, AWS integration, or another method.
Environment: Whether it's an environment, such as AMI-based or auto scaling, where servers with the same configuration are added and removed.

FAQ#

A. Multiple servers with different configurations ended up duplicated under the same UUID

FutureVuls identifies servers by UUID (an identifier for each server). Scanning with the same UUID mixes their information together. To fix this, delete the server with the duplicated UUID, write a new UUID (created with uuidgen or a similar tool) in each server's config.toml, and scan again.

B. How is licensing handled in AMI or auto scaling environments?

Servers with the same configuration can be treated together as one server. Install the scanner on a representative instance, run a scan once to generate the UUID, and then create the AMI. When you scale out using that AMI, the instances share the same UUID and are treated as one server, which saves licenses. If you create the AMI without scanning, each instance is issued a different UUID and registered as a separate server.

C. I want to register ECR or Docker images

To register multiple images on one server, or to learn the difference between ECR basic scanning and enhanced scanning, see the related articles below. For instructions, see Docker Scan (ECR/GAR).

D. I registered a server, but no vulnerabilities appear

For servers registered with Paste Scan, detection runs automatically as soon as you click "Submit" (for both Windows and Linux). If nothing appears after a few minutes, check that the pasted output isn't cut off. Software that shows "CPE required" in the "Vulnerability Detection" column of the software list isn't checked for vulnerabilities until you assign a CPE.