The scan results are not reflected
Run scan process with –debug option, the same JSON that will be uploaded to FutureVuls will be output to files under /opt/vuls-saas/results on the server.
WordPress related settings will be shown as 26293-26297 in the sample below.
If this is empty, there is a problem with the config.toml settings.
``sh [vuls-saas@kusanagi2 vuls-saas]$ pwd /opt/vuls-saas [vuls-saas@kusanagi2 vuls-saas]$ grep -n4 wordpress results/current/kusanagi2.json 26289- “port”: “local”, 26290- “scanMode”: [ 26291- “fast-root”. 26292- ], 26293: “wordpress”: { 26294- “osUser”: “kusanagi”, 26295- “docRoot”: “/home/kusanagi/yokota/DocumentRoot”, 26296- “cmdPath”: “/usr/local/bin/wp”, 26297- } 26297- }
#### Sample config.toml
``sh
[vuls-saas@kusanagi2 vuls-saas]$ cat config.toml
[servers]
[servers.kusanagi2]
host = "localhost"
port = "local"
user = "vuls-saas"
scanMode = ["fast-root" ,]
[servers.kusanagi2.wordpress].
cmdPath = "/usr/local/bin/wp"
osUser = "kusanagi"
docRoot = "/home/kusanagi/yokota/DocumentRoot"
[saas].
GroupID = xxx
Token = "xxxxxxxx"
URL = "https://auth.vuls.biz/one-time-auth"
Refer to Help to check config.toml.
Run the scan manually on the server and check if any errors are displayed.
Also, see above
> JSON uploaded to FutureVuls also remains on the server.
Check if the value is set to the wordpress item in the following command output, as described in `>.
[vuls-saas@kusanagi2 vuls-saas]$ grep -n4 wordpress results/current/kusanagi2.json
Set sudoers on the server to be scanned