- Feb 14, 2013
- 113
Has anyone used Comodo Sandbox with Appguard? Is there any conflict, or special configuration needed? The last time I used Comodo with AppGuard I didn't use Comodo Sandbox at all.
I've used Sandboxie before, but it does not fit in well with my layered security.Could you use Sandboxie in place of Comodo Sanbox? Hmm! Thinking!
Yeah, I actually tried AppGuard, and VoodooShield with Comodo, but I never did try Comodo Sandbox. Sandboxes have not really fit in well with my setup over the years. I feel that i'm well protected without them, but I was curious if AG would work with Comdo Sandbox. I should have tried them together during the 6 weeks I used Comodo. It's probably been 6 weeks since I tried Comodo. If I try Comodo again I will be removing all trusted publishers immediately. I think its none sense having all those allowed for users that know what they are doing.
I wish Comodo would just focus on making Comodo FW/HIPS lighter, and fixing bugs. I would also like to see what methods they use to intercept various executions. I tried Comodo with AG, and VS. Comodo was always the last to intercept executions. I had not used Comodo in a long time, and I thought Comodo would intercept executions first because Online Armor intercepts execution before AG, and VS. I assumed Comodo would use similar methods as Online Armor. I assume they use hooks, and probably injection also. I wonder if they use a KMD for any of their mitigations. I will see if they will release any information on the methods they use if I decide to try Comodo again. I want bother them unless I decide to use Comodo again.
Thank you for information! If I try them together I may check with you to make sure I have the right exceptions to use comodo Sandbox to avoid conflicts.used CIS + AG (with proper exceptions done) , no issues so far.
That's very interesting. It makes me want to go back, and try it again.When I combine Comodo with NVT ERP or VS, it is always Comodo that detects and notifies first - and it is very fast. I have Proactive Security\HIPS enabled... so perhaps that has something to do with it.
In any case, it appears two different users with two different systems = two different experiences with security softs.
I would assume they have made some changes since that article came out around 2012 that showed verified methods for bypassing Comodo HIPS. They took advantage of Comodo not using ASLR, and DEP. I know they use ASLR now.. well I think I remember checking, and verifying that they do now with Process Explorer. I think that's probably not all they have changed since then, but keeping quite about their method undoubtedly helps to prevent Comodo from being bypassed by exploit. I would like to see them spend more time on the Firewall, and add IDS protection for common inbound attacks. I don't think Comodo has IDS protection yet, but I could be wrong.I, as well as a lot of other CIS users, have tried to get infos regarding how CIS works - but little, if anything, is to be found. Comodo itself never provides any in-depth technical explanations; their answers are almost always two-liners. It seems to me they don't want to give up technical details...
Thank you for information! If I try them together I may check with you to make sure I have the right exceptions to use comodo Sandbox to avoid conflicts.
That's very interesting. It makes me want to go back, and try it again.
I would assume they have made some changes since that article came out around 2012 that showed verified methods for bypassing Comodo HIPS. They took advantage of Comodo not using ASLR, and DEP. I know they use ASLR now.. well I think I remember checking, and verifying that they do now with Process Explorer. I think that's probably not all they have changed since then, but keeping quite about their method undoubtedly helps to prevent Comodo from being bypassed by exploit. I would like to see them spend more time on the Firewall, and add IDS protection for common inbound attacks. I don't think Comodo has IDS protection yet, but I could be wrong.
The last time I used Comodo I had already done all that for AppGuard except for the appdata folders. I didn't know that would be needed. During that time I did not try the sandbox at all. I've just kind of got the urge to try the sandbox lately.
I think they will be a lot better off if they stop adding stuff now, and fix what they have. If I was in charge of Comodo development all I would be concerned about is discovering, and fixing bugs.In all honesty, CIS + antiexecutable is complete overkill for typical, daily use since CIS sandbox can be configured to block all Unrecognized files. When configured in this way, it is essentially an antiexecutable with integrated firewall and HIPS.
There are still various bugs - that vary widely depending upon the OS. In my estimation, CIS still operates best on W7 systems. You are accustomed to ESS which means you will find CIS' bugginess intolerable. ESS is a polished soft whereas I don't think CIS will ever be... at least not anytime within the next five years - if that...
Currently, I use CIS with either NVT ERP or VS since AE configuration does not block certain installers. I am working with Comodo engineering to get it fixed. There is some indication that it is W8\8.1 specific but I am not absolutely certain of it.
I think they will be a lot better off if they stop adding stuff now, and fix what they have. If I was in charge of Comodo development all I would be concerned about is discovering, and fixing bugs.
The last time I used Comodo I had already done all that for AppGuard except for the appdata folders. I didn't know that would be needed.
this is what I've found, and I run Comodo with Proactive Security\HIPS enabled and VS..When I combine Comodo with NVT ERP or VS, it is always Comodo that detects and notifies first - and it is very fast. I have Proactive Security\HIPS enabled... so perhaps that has something to do with it.