Let's say a thief steals your phone, as phone thiefs tend to do. One of the first things they will do is turn the device off to help keep the product from being tracked, just in case. Once they get home or whever they want to toy with the phone, they will have to turn it back on to try to unlock the device or factory reset it.
Therefore, I would like to see Webroot SecureAnyhere upload the location of the device to the users Webroot account whenever the device is turned on or off. That could potentially be the one difference in locating a stolen device.
This enhancement/suggestion is certainly not necessary but would be helpful in certain situations.
By adding a more simple method to filter the viewing of the Active Connections and Active Processes, it would simplify and speed up the process of viewing (ONLY) those in a blocked or monitored condition.
While the current screens provide the above-mentioned information it is a bit unwieldy when forced to scroll through many lines of information while looking for blocked or monitored conditions. Sometimes an active process or connection is temporary and if you don’t catch it quickly while it is being executed, you can miss out on valuable troubleshooting information.
This would be most helpful to the non-techie user who is probably overwhelmed by the amount of information on the screen when trying to troubleshoot if WSA is preventing their application or function from working properly.
In the Group Management tab, while viewing the endpoints list there is the Scan History pane at the bottom of the screen.
When having opened to view a specific client's item of Scan History, then, in order to view the next one, we have to close the one that is currently open and then open the next one or the previous one.
It is not rare that we would want to view the batches of files being detected consecutively at each "timestamp" being offered by the scans. It gives a totally different perspective than when viewing all the files detected for a specific client.
We need this to determine what went on and when, and the history behind that.
If in every opened Search History item we had navigation buttons to load the next item and the previous item it would be much easier for tracking the actual history behind some important for us threat detections.
I didn't find anything relevant in the previous feature requests, but if I only missed it, please inform me as to move this under an already existing relevant thread.