- Apr 13, 2013
- 3,224
A very short video in reference to a current War Room discussion:
So you maxed CIS settings.Guess I should have specified that I was using my suggested settings- sandboxed processes as Untrusted. As there is no reason not to harden the Box in this way- Not making this change is like never taking a Lamborghini out of First gear.
Tony- the issue with scripts in general is many Security products can't distinguish a legitimate script from a malicious one. This is a severe issue in the Enterprise space, and the cause of most of the recent breaches (and also the reason why many Corporations are switching from Traditional protection to solutions based on virtualization like FireEye and Palo Alto).
Ok.SB doesn't have any such generalized setting.
Ok.
You test mostly modified CIS settings...thats good as it shows the power of CIS.
But would be good to see tests with default settings too... as there are many users like me those go with default settings & would like to see how default settings does against any/all threats....& default settings are kind of recommended settings for majority so defaults should be put to test more.
SB doesn't have any such generalized setting.
Could you show the tweaks, necessary to additional protections?
hi, like umbra said using and restriction setting of it depends on how you configure and based on your liking. if you asking me it is same like using and understanding how comodo works.nothing to add more on this learning curve, nobody will became perfect in one day, it will take years to become one, so have patience and fun in learning, only personal experience is the best teacher.Could you show the tweaks, necessary to additional protections?
Kind regards,
not to say that Sandboxie is incompatible with Comodo sandbox. (well known fact on both Comodo and sandboxie forums)
You can see that the tray icon of Sbie doesnt keep the red dots (meaning no sandboxing is applied).
i sufffered this bug when i installed CIS and Sbie, Sbie couldn't protect my browser; in fact it even didn't start at all.
i didn't pay attention that both was running when i wrote my post earlier. it is by reading @Av Gurus' comment that i saw the issue.
so basically the test is irrelevant for checking Sbie protection. Sbie should have been tested alone with proper settings.