Reply to thread

Message

<blockquote data-quote="SeriousHoax" data-source="post: 835080" data-attributes="member: 78686">After executing a file, WD cloud protection checks the file in the cloud to see if the file is safe or not. If the file you&#039;re running is already known to WD cloud then the checking usually happens within 10 seconds. In fact in less than 10 seconds. Maybe 1 or 2. When the option is set to 10 sec, if WD don&#039;t get any result from the cloud within 10 seconds, it will let the sample run but if you increase to let&#039;s say 60 seconds then WD will wait at least 60 seconds to get a verdict from the cloud. Increasing the time is more helpful in case of executing unknown files. Let me give you an example, few days ago I ran a fresh malious sample in Sanboxie. The sample was not known WD. Not even by their cloud (I checked before executing). My cloud checkup time was set 10 seconds. WD waited 10 seconds but couldn&#039;t get any result from the cloud so let the sample ran. It ran successfully and also created a startup entry. Only 2 minutes later, I went on to delete the contents of Sandboxie but as soon as my PC accessed that file again, WD detected and deleted the file. I manually scanned the source sample on my PC and Windows Defender this time detected that file as well. So, what probably happened was, after running the file WD uploaded the sample in cloud and then their AI checked the file and verified that as a malware. But this took more than 10 seconds. If my cloud protection timeout was set to 60 seconds, WD probably would be able to block the malware before it was allowed to execute. After that, I have set the timeout to 60 seconds. I think it&#039;s better this way. You&#039;ll almost never to wait 60 seconds unless you&#039;re running something brand new which is not even known to WD cloud.I hope this clarifies your question.</blockquote>

[QUOTE="SeriousHoax, post: 835080, member: 78686"] After executing a file, WD cloud protection checks the file in the cloud to see if the file is safe or not. If the file you're running is already known to WD cloud then the checking usually happens within 10 seconds. In fact in less than 10 seconds. Maybe 1 or 2. When the option is set to 10 sec, if WD don't get any result from the cloud within 10 seconds, it will let the sample run but if you increase to let's say 60 seconds then WD will wait at least 60 seconds to get a verdict from the cloud. Increasing the time is more helpful in case of executing unknown files. Let me give you an example, few days ago I ran a fresh malious sample in Sanboxie. The sample was not known WD. Not even by their cloud (I checked before executing). My cloud checkup time was set 10 seconds. WD waited 10 seconds but couldn't get any result from the cloud so let the sample ran. It ran successfully and also created a startup entry. Only 2 minutes later, I went on to delete the contents of Sandboxie but as soon as my PC accessed that file again, WD detected and deleted the file. I manually scanned the source sample on my PC and Windows Defender this time detected that file as well. So, what probably happened was, after running the file WD uploaded the sample in cloud and then their AI checked the file and verified that as a malware. But this took more than 10 seconds. If my cloud protection timeout was set to 60 seconds, WD probably would be able to block the malware before it was allowed to execute. After that, I have set the timeout to 60 seconds. I think it's better this way. You'll almost never to wait 60 seconds unless you're running something brand new which is not even known to WD cloud. I hope this clarifies your question. [/QUOTE]

Verification