Product Announcements & Troubleshooting Exposure Management

After onboarding a new Elements Exposure Management, the Identities view in the Elements Portal does not populate data.
False positive or false negative detection when scanning backported software with Elements Exposure Management
How does WithSecure Elements Vulnerability Management count scanned unique IP addresses?
Some Elements Vulnerability Management scheduled system scan end up with "Terminated" status
When requesting a scan node license in Elements Exposure Management Portal, the error "number of allowed scan node licenses has been reached" is displayed.
What kind of network firewall openings need to be in place between scan nodes and hosts to be scanned?
This operation is forbidden error when accessing Elements Exposure Management pages in portal
How can a partner or end-customer get admin rights so that they can access Elements Exposure Management
No identity found and scan results do not show any details on Elements Exposure Management
After a new Elements Exposure Management is onboarded, the Identities view in Elements Security Center does not populate with data

Troubleshooting Radar Scan Node connectivity to Radar Security Center

Issue:

There is an issue with scan nodes not being able to connect to F-Secure back-end servers. In short, the Last seen and Engine update indicators on https://portal.radar.f-secure.com/mmc/settings/scannodes.aspx show a delay of more than 3-4 minutes.

Resolution:

To troubleshoot the scan node connectivity:
1. Make sure that the F-Secure Radar Scan Node Agent (legacy name= Karhu.Scan.Daemon) service is running. Check this by using Windows Task Manager or Windows Local Service.