We're in the process of pushing a small update to the ULAV user interface. This update changes the functionality of the context menu accessed by right-clicking on one or more selected files in Windows Explorer. I'd like to briefly explain the change we've made (as it might, on the surface, appear confusing).
Right now, when you scan a file with ULAV, internal logic determines whether it is a file we can send to the cloud for scanning or not. For privacy reasons, we don't send all files to our cloud for scanning. The determination is mostly made based on the type of file we've encountered; executable file types are okay to send to the cloud for scanning, but document types are not, since they may contain private or sensitive information.
The UI change we're pushing out opens up a new context menu option "Cloud scan...". This option will apppear if you have selected one or more files that wouldn't normally be scanned in the cloud. Note that this option will only appear when selecting individual files (not directories). If you select this option, you will be presented with an additional dialog to confirm the action.
Note that when a file is sent for cloud scanning, it only remains on our backend for as long as it takes to be anaylzed, after which it is discarded. The reason we have excluded files that could contain private data from cloud scanning by default is to keep up with our company's privacy promise. However, we wanted to give users the option to send all types of files for a more thorough analysis, should they wish to. By default, all scans initiated by the user in any other way than selecting "Cloud scan..." will obey the regular logic and we will only send selected non-private file types to the cloud for scanning (as mentioned above).
For more information on our privacy principles, check this page: https://www.f-secure.com/en/web/legal_global/privacy/principles
For specific details on our Security Cloud policies, check the following: https://www.f-secure.com/en/web/legal_global/privacy/security-cloud
Sorry for my reply about new feature.
- It was from first.... or after some hours... there comes limitation just for sixteen files per one cloud-scan?
Maybe it should be with something as pop-up.... when choosed more files? On current time it's comes with silence.
- And also... does it normal that cloud-scan (as Security Cloud detection... "!Online"-based) can be about files, which previously was with "detection" - but removed as "false positive". How to understand current situation:
--> Security Cloud not updated about false positive (long time ago). Or random.
--> "not cloud" scan goes to missing detection for "suspicious/malicious" files.
My situation was about ".crx"-file (as Chrome extension, which was previously detected by F-Secure as normal scan... and dropped after that.. as false positive. On current day... it was still ignore this file, but Cloud-scan feature triggered previous detection with "!Online"-addition).
After reding this I tried a small indifferent file and the Cloud scan worked just fine.
Then I tried Ultimate Windows Tweaker 126.96.36.199.exe which was previously blocked by ULAV.
The Could scan option is not there. Wonder why.
I think.... because "Ultimate Windows Tweaker" is executable file. Description for "Cloud Scan" feature says... that executable files and some else (not sure which) goes to be automatically with "cloud scan"-design. Such as... "Cloud scan" created just for files (extensions), which normally ignored to be upload for cloud and cloud-check.
You can try to use tricks probably. Just re-name "uwt.exe" to "uwt.msi" (or any other...) and "Cloud scan" should be visible. If all normally worked... so... there should be not any difference between. Such as... ".exe" files during scanning goes to be checked about "if it was already checked under cloud or there required re-scan" (and if required... to do this automatically).
Sorry for not nice English.
But.. for full topic.
I have else one point to question.
With new design of scan-process (?) there also happened notifications about "failed to scan file".
During normal scan.
As result.. I have about three hundred notifications about files, which was "failed to scan" (after scan for "all local drives"). Probably it's OK... but it's start be "too much" notifications around... and still not possible to remove something as "type of notifications" by one step.
@Ukko is correct. Cloud scan is performed by default for most executable file types and hence the separate context menu option won't appear for these types of files.
We are aware of the increased number of error dialogs arising from failed scans. These are mostly due to network timeouts in the cloud scan functionality. We preferred to make them visible to you guys soo you can see if something wasn't actually scanned.
Thanks for response.
Current design indeed... more nice. Such as... there visible.. that some of files not scanned.
From first... I met current notification "about failed scan" with my steps (I turn off network connection and tried to use Security Cloud). For check... how it will be. :) There indeed time-out.. because some minutes will be "waiting" and trying to scan (and just after that created notification) .
But about "a lot of notifications after scan". There probably same things, but with another reason. Such as.. rights, "in use"-status or something around this. Just because... for some files - notification will be from first.
swapfile.sys and other files (as example)
I think on current time... my experience about files, which was not scanned.. can be partly same with files, which will be not scanned by FS Protection (as example). But with FS Protection there more files, which skipped/not scanned.
There anyway... nice points, because previously.. F-Secure ULAV does not trigger current notifications. But probably same files was not scanned too.
Sorry for my reply.
I know a lot of you have had questions about how Banking Protection works, so I thought I'd direct you to a blog post that Micke wrote recently. The blog post can be found here:
Hopefully it helps answer some of those questions!
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support agents and get answers to your questions