The customer needs to suggest the software via his SVM cloud portal, so the Flexera File Signature team can add the product to the database for tracking and detection rule.
SVM > Configuration > Suggest Software
Vulnerability Database hasn't been synced with Flexera SVM backend
Check your SVM onpremise server public IP
If the public IP has been changed and Flexera SVM backend whitelisted public IP is old then the Vulnerability database will not get the latest vulnerability information
Tail the /usr/local/Secunia/csi/log/sync.log for any errors etc tail -n 1000 /usr/local/Secunia/csi/log/sync.log
If you see errors in the sync log or the public IP has been changed, then please contact Flexera SVM support.
Important: The SVM on-premise customers cant suggest the software from their SVM portal via IE, so they need to request SVM support to provide them the SVM cloud account with one host license, so they can suggest the software.