Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
Basic sandbox demo(for beginners)
Message
<blockquote data-quote="AtlBo" data-source="post: 651065" data-attributes="member: 32547"><p>Could be you saw a reference in [USER=7463]@cruelsister[/USER]'s videos where she states that rebooting will shut down the malware from running in the sandbox. You are also correct that the sandbox must be cleared manually. Reboot as you mention doesn't clear the sandbox with Comodo.</p><p></p><p>OK, if I am wrong about the below please correct me. This is how I understand Comodo's auto-sandboxing.</p><p></p><p>I believe the reason [USER=7463]@cruelsister[/USER] mentioned that malware cannot hurt the system even when running while a reboot is begun was that some malware in the sandbox can affect a system such that is makes a system mildly unstable. Depends on the sandbox settings for restriction level, where restricted is basically a block for all purposes. However, I believe with Partially Limited or straight Virtualized with no limitations, malware could open some things and maybe even drop some files sometimes or make the processor race. At any rate running malware in the sandbox could still lead someone to want to try a reboot, and there is no harm in doing so. Malware can't do harm to the system or files, and rebooting will mean the malware is no longer running.</p><p></p><p>You may have noticed that in some of [USER=7463]@cruelsister[/USER]'s videos malware running in the sandbox changed the wallpaper and dropped ransom note. That's an example of what can happen at some sandbox restriction levels (settings). I guess partly she does this to show what the malware attempts to do. Reboot and you will have to fix those problems manually (with or without reboot actually), but the malware will not still be running in the sandbox when the PC restarts. To run it must be restarted manually (bad idea o/c). At that point you can just empty the sandbox manually and its traces will be gone. Just make sure to delete the malicious file too.</p></blockquote><p></p>
[QUOTE="AtlBo, post: 651065, member: 32547"] Could be you saw a reference in [USER=7463]@cruelsister[/USER]'s videos where she states that rebooting will shut down the malware from running in the sandbox. You are also correct that the sandbox must be cleared manually. Reboot as you mention doesn't clear the sandbox with Comodo. OK, if I am wrong about the below please correct me. This is how I understand Comodo's auto-sandboxing. I believe the reason [USER=7463]@cruelsister[/USER] mentioned that malware cannot hurt the system even when running while a reboot is begun was that some malware in the sandbox can affect a system such that is makes a system mildly unstable. Depends on the sandbox settings for restriction level, where restricted is basically a block for all purposes. However, I believe with Partially Limited or straight Virtualized with no limitations, malware could open some things and maybe even drop some files sometimes or make the processor race. At any rate running malware in the sandbox could still lead someone to want to try a reboot, and there is no harm in doing so. Malware can't do harm to the system or files, and rebooting will mean the malware is no longer running. You may have noticed that in some of [USER=7463]@cruelsister[/USER]'s videos malware running in the sandbox changed the wallpaper and dropped ransom note. That's an example of what can happen at some sandbox restriction levels (settings). I guess partly she does this to show what the malware attempts to do. Reboot and you will have to fix those problems manually (with or without reboot actually), but the malware will not still be running in the sandbox when the PC restarts. To run it must be restarted manually (bad idea o/c). At that point you can just empty the sandbox manually and its traces will be gone. Just make sure to delete the malicious file too. [/QUOTE]
Insert quotes…
Verification
Post reply
Top