Software Vulnerability Manager on-premises synchronization requirements
Software Vulnerability Manager (SVM) On-Premises synchronizes vulnerability intelligence from Flexera. To ensure successful synchronization, configure your network, firewall, proxy, and security appliances to allow access to the required synchronization endpoint.
Following these requirements helps prevent interruptions caused by changes to cloud service IP addresses.
Synchronization endpoint
Allow HTTPS access to:
Important: Use hostname-based (FQDN) allowlisting whenever possible. Cloud-hosted service IP addresses can change over time. Allowlisting the hostname helps maintain uninterrupted synchronization without requiring network rule updates.
Verify synchronization status
To confirm that vulnerability data is synchronizing successfully, run the following query against the SVM database:
[root@svm ~]# mysql -u root
MariaDB [(none)]> select max(vuln_modified_date)
-> from vuln_track.vuln;
+-------------------------+
| max(vuln_modified_date) |
+-------------------------+
| 2026-08-04 22:07:07 |
+-------------------------+
1 row in set (0.022 sec)
MariaDB [(none)]>
The returned date should show a recent vulnerability database update.
Troubleshoot synchronization issues
If synchronization isn't working, verify the following:
- Confirm that the SVM server can resolve
sync.secunia.com. - Verify that firewalls and proxies allow outbound HTTPS traffic.
- Check whether DNS caching or proxy caching is returning outdated records.
- Run the following command:
- [root@svm ~]# curl -v https://sync.secunia.com
- Verify that the hostname resolves successfully.
Was this helpful?
© 2026 Flexera. All rights reserved.