Servers / Products#
Feature Overview#
The Server / Product tab allows you to check the servers and products that have been registered through scanning. It displays a list of servers within a group and allows you to manage network devices by registering pseudo-servers.

| Item | Details | Update Timing |
|---|---|---|
| Server Name | The name of the server. The initial value is set in config.toml during the scan. It can be changed after registration in Server Settings on the Server Details tab. |
On Server Settings Update |
| Role Name | The role to which the server belongs. If not set, it is assigned to the "Default Server Role". | On Server Settings Update |
| OS Reboot Required | Whether the OS needs to be rebooted or outdated processes need to be restarted. The following commands are used: ・Red Hat family: needs-restarting・Debian family: checkrestart |
On scan |
| Container | Whether it is a container image. | On scan |
| OS | The server's OS (pseudo for pseudo-servers, instances, and container registries). |
On scan |
| Version | The version of the server's OS (unknown for pseudo-servers, instances, and container registries). |
On scan |
| Open Immediate Tasks | The number of tasks associated with the server where "SSVC Priority" is Immediate, "Status" is NEW, and it is not hidden. |
On scan |
| Open Out of Cycle Tasks | The number of tasks associated with the server where "SSVC Priority" is OutOfCycle, "Status" is NEW, and it is not hidden. |
On scan |
| Open Tasks | The number of tasks associated with the server where "Status" is NEW and it is not hidden. |
On scan |
| Ongoing Tasks | The number of tasks associated with the server where "Status" is INVESTIGATING, ONGOING, or DEFER, and it is not hidden. |
On scan |
| Completed Tasks | The number of tasks associated with the server where "Status" is not NEW, INVESTIGATING, ONGOING, or DEFER, or where the task is hidden. |
On scan |
| All Tasks | The total number of tasks associated with the server. | On scan |
| Server Tag | Tags set on the server. | On Tag Update |
| Server Type | The type of the server. | None |
| Supplementary Information | Additional information registered for the server. | On Server Settings Update |
| Scanner Version | Whether the scanner version is the latest. | On scan |
| Last Detection Time | The latest date and time when registered configuration information was successfully matched against vulnerability information. | On scan |
| Last Configuration Sync | The latest date and time the scanner synchronized the server's configuration information with FutureVuls. Only applies to servers of type "Scanner". |
On scan |
| Successful Scans This Month | The number of successful scans this month. | On scan |
| Default Assignee | The primary assignee automatically assigned to newly created tasks. ・When adding a server via the FutureVuls console (such as pseudo-servers or paste-servers), the creator is set as the server's default assignee. ・For other cases, such as adding a server via a scanner or REST API, the group's default assignee is set as the server's default assignee. |
On Server Settings Update |
| Server ID | The management ID of the server used in the REST API, etc. | None |
| Server UUID | A unique ID that identifies the server. | None |
| Server IPv4 | The server's IPv4 address. | On scan |
| EOL (Standard Support Deadline) | The End of Life for the server's OS. | On scan |
| Cloud One Status | The status of the Cloud One integration. | On scan |
| Platform | The platform, such as AWS. | On scan |
| Platform Instance ID | The ID on the platform. (When a platform such as AWS exists.) |
On scan |
| Scanner Installation Location | The location where the scanner is installed. | None |
| SSM Integration | The status of the AWS SSM integration. | On scan |
| Server Registration Time | The date and time the server was registered. | None |
Add Server#
Displays a dialog with a form to register a server in FutureVuls, along with links to other registration methods.

| Item | Description |
|---|---|
| Scan a physical machine | Install the Vuls scanner on a server to detect vulnerabilities. For accounts with administrator privileges, clicking the "Add" button will display the scanner installation command. |
| Container Image Scan | Import the results of a Trivy container image scan into FutureVuls. |
| Scan Libraries on File System | Import the results of a Trivy scan of libraries on the file system into FutureVuls. |
| Add Paste Server | Add a server for environments where a scanner cannot be used, such as closed networks, by pasting command results to detect and manage vulnerabilities. |
| Import an SBOM file | Import an SBOM generated from an SBOM tool into FutureVuls and add it as a FutureVuls server. |
| Add Pseudo Server | Add a pseudo server to detect and manage vulnerabilities based on manually registered information, without installing a scanner. The created pseudo server is registered with the OS as pseudo. By creating a pseudo server with a network device name and registering CPEs, you can manage vulnerabilities for various platforms. Pseudo servers are subject to charges just like other servers. |
| Add an instance | Add an Amazon EC2 instance. The created server is registered with the OS as pseudo. |
| Integrate with Container Registry | Integrate with Amazon ECR or GCP Artifact Registry. The created server is registered with the OS as pseudo. |
Pseudo-server#
A pseudo-server is a non-physical, empty server used when you want to manage software and other assets on FutureVuls. For example, if you want to perform a CPE scan on the firmware of a network device, you can create a pseudo-server and then register the CPE.
You can create a pseudo-server from Add Server in the server list.
After creation, you can register CPEs from the software, just like a regular server.
Billing
Please note that a pseudo-server is counted as one server for billing purposes, just like a scanned server.
Pseudo-servers are automatically scanned daily, and manual scans can also be initiated from the server details page.
Edit Servers#
You can edit multiple servers at once by selecting them with checkboxes. For a list of users who can be designated as the "Default Assignee", please see here.

SSM Scan#
You can initiate an on-demand scan for EC2 instances for which AWS credentials have been registered (SSM Integration Scan).