This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

KnowBe4 RanSim - CryptoGuard didn't stop InsideCryptor

I recently run KnowBe4's ransomware simulator on my desktop. Whilst it appears that Sophos did better than most of their competitors it still missed InsideCryptor. I'm looking for an explanation on how this could happen. Is it a configuration problem? An issue with the simulator or did CryptoGuard drop the ball and Sophos is working on this? 



This thread was automatically locked due to age.
Parents
  • Here is some feedback from KnowBe4: The original poster, who originally noted InsideCryptor not being blocked, uses a very old version of Ransim (1.0.3.4). Since then, several things have changed in the code and those changes also reflect in the results. I would advise them to give it a try with the latest version.

    The rest of the people did use the latest version in which InsideCryptor appear to be blocked, as that person from Support states (he probably used the latest version as well), but there are other scenarios that are not blocked (the support guy doesn't mention anything about them - he only says "it" referring to InsideCryptor).

    About the inconsistencies, badrobot got slightly different results from Simeon Lewis, but the results are not that different. From the screenshots one can see that in both cases Injector, ReflectiveInjector and VirlockVariant are not blocked. On the Simeon's machine, the miner also ran fine and one false positive scenario was blocked. 

    We've seen such results form time to time with certain AVs, but it is not a problem in Ransim. The detection methodologies used by AV engines, the performance/processing and I/O load on the machine on which the test occurs play a major in the outcome of the test. To give you an example, we saw a few cases when Windows Defender flagged a particular scenario several minutes after the test was over and attempted to quarantine it, but the executable was already erased from disk and the files remained encrypted. Another time, on the same machine, the same Ransim setup, Windows Defender didn't complain at all on the same scenario.

    In conclusion, based on the somewhat limited information on that thread, we don't really see an with Ransim. Moreover, as one of the participants said, everyone can have a look at the files (they can even use their own files) and see if they are encrypted or not after the test. 

    Hope this clarifies,  Warm regards, Stu 

Reply
  • Here is some feedback from KnowBe4: The original poster, who originally noted InsideCryptor not being blocked, uses a very old version of Ransim (1.0.3.4). Since then, several things have changed in the code and those changes also reflect in the results. I would advise them to give it a try with the latest version.

    The rest of the people did use the latest version in which InsideCryptor appear to be blocked, as that person from Support states (he probably used the latest version as well), but there are other scenarios that are not blocked (the support guy doesn't mention anything about them - he only says "it" referring to InsideCryptor).

    About the inconsistencies, badrobot got slightly different results from Simeon Lewis, but the results are not that different. From the screenshots one can see that in both cases Injector, ReflectiveInjector and VirlockVariant are not blocked. On the Simeon's machine, the miner also ran fine and one false positive scenario was blocked. 

    We've seen such results form time to time with certain AVs, but it is not a problem in Ransim. The detection methodologies used by AV engines, the performance/processing and I/O load on the machine on which the test occurs play a major in the outcome of the test. To give you an example, we saw a few cases when Windows Defender flagged a particular scenario several minutes after the test was over and attempted to quarantine it, but the executable was already erased from disk and the files remained encrypted. Another time, on the same machine, the same Ransim setup, Windows Defender didn't complain at all on the same scenario.

    In conclusion, based on the somewhat limited information on that thread, we don't really see an with Ransim. Moreover, as one of the participants said, everyone can have a look at the files (they can even use their own files) and see if they are encrypted or not after the test. 

    Hope this clarifies,  Warm regards, Stu 

Children
  • Hi Stu, 

     

    Thanks for replying, I appreciate the you taking the time to address this yourself.  I also think as IT admins we tend to panic and or freak out a little when we hear Ransomware and vulnerable in the same sentence.  If there are any logs or information I can provide to narrow down if the vulnerability does really exist or if it is showing as a false positive please let me know.  In the end my highest concern is the security of my network. 

    Respectfully, 

     

    Badrobot