Hello. First, I went to run Steam, which is a well-known application, but got several warnings from Def+. I chose to allow Steam and remember it, yet even after closing Steam, it is still in the sandbox. Also, Firefox was sandboxed after Steam opened it, even though Def+ has not bugged me about it yet. This isn’t a huge issue, but I wanted to let you know so you can improve the program.
This is one of the hallmarks of CIS technology: despite the HIPS warning you most emphatic, the user decids HIPS is in error, ergo: ALLOW!
I don’t understand how Firefox - a greater reknown app than the one you mention - got sandboxed on your system - when it’d never get sandboxed on anybody’s elses system - because you ran your app (which is not recognized), and that despite your app being so ‘very well known’, and it got sandboxed.
It smells as if you have gremlins afoot; look into the CIS on-line help info conerning ‘sandboxing’ and what that entails.
I believe this to be a prime example of why heuristic cloud-based assessements of threats is superior to legacy click-volume of the technology in existance some few weeks ago…
WxMan1, I hardly follow your English full of abbreviations.
I don't understand how Firefox - a greater reknown app than the one you mention - got sandboxed on your systemThe documentation says that even safe applications get sandboxed when exexuted by an already sanboxed application. View this link [url=http://help.comodo.com/topic-72-1-155-1184-unknown-files---the-sand-boxing-and-scanning-processes.html]Unknown Files: The Sand-boxing and Scanning Processes[/url].
Steam gets updated so often the white list will basically be always too late.
Also, Firefox was sandboxed after Steam opened it, even though Def+ has not bugged me about it yet. This isn’t a huge issue, but I wanted to let you know so you can improve the program.That’s by design.