You can display what needs to be done for vulnerability resolution using a command or Ansible Playbook.
The update command is a task function, so it can be displayed by selecting a task. The update command can be displayed from the task list or from the details of a task.
After selecting a task with a patch available, click the “Update Command” button to display a dialog. If you select multiple tasks, the commands to resolve the vulnerabilities of the selected tasks are aggregated on a per-server basis and displayed in the dialog.
If there are updatable packages, the “Update Command” button will be displayed under the related packages.
The contents of the dialog are explained below.
You can check the command to confirm the dependencies of the update target package and the processes that will be affected by the update work.
The command to be executed on the target server to resolve the selected vulnerabilities is displayed.
The command to check the status of the update application is displayed.
By manually executing the Vuls scanner on the actual server, the latest configuration information is obtained and uploaded to FutureVuls. FutureVuls recognizes that the package has been updated and automatically changes the status of the vulnerability resolution task to “Patch_applied” and closes the task.
The command for rolling back the update is displayed. If you want to roll back the package update in case of a problem during the update, please execute this command.
Just like the update command, Ansible’s Playbook is displayed.
The hosts item needs to be edited by each user.
If you want to run Ansible Playbook without a hosts file, please refer to the following link. https://stackoverflow.com/questions/37652464/how-to-run-ansible-without-hosts-file/42254084
Also, when you click the download button, the Ansible Playbook will be downloaded.
When specifying multiple tasks to display an Ansible Playbook, the playbook is generated separately for each task.
Clicking the download button at the top of the screen also downloads the playbook that serves as the starting point for executing all the playbooks, making it effective for simultaneous execution.
The content of the starting point playbook is as follows:
---
## Generated by FutureVuls
## created at 2018/12/18 16:55:33
- hosts: {enter target host}
tasks:
- include: ip-192-168-0-188_CVE-2014-9402.yml
- include: ip-192-168-0-188_CVE-2015-5180.yml
Edit the hosts as well and execute it.