- Apr 18, 2016
- 3,684
HMPA can't stop bugging people's computers
Assuming others are not admins. they don't have your admin password and their account asks for one for elevation and you don't share storage devices then yeah you are pretty much right. Their actions can't really affect you.Current config:
Emsisoft
AppGuard at protected level
I used to run additional softs because I was worried about what noobs might do on the other user accounts on this PC (they are on standard user accounts). But then I realized that I personally have nothing to worry about, because they can only hurt themselves.
Appguard, even out-of-the-box settings, should prevent any malware activity that could affect a different user account, because:
1 Even if malware is signed, it won't be able to write to system space, because it first executes in user space.
2 Processes running in one user account cannot interact with processes running in another user account. (This is the principle on which ReHIPS is based, if I am not mistaken.)
Do you agree?
Your config is similar to my productivity machine, i just have ReHIPS on top because:Current config:
Emsisoft
AppGuard at protected level
Your config is similar to my productivity machine, i just have ReHIPS on top because:
1- i love it.
2- i'm so used to sandboxes, i can't live without them.
3- for beta testing sake.
Thanks. Good points. So I need to prevent certain user accounts from accessing my second hard disk, which has storage.Assuming others are not admins. they don't have your admin password and their account asks for one for elevation and you don't share storage devices then yeah you are pretty much right. Their actions can't really affect you.
Remove their write permissions or even read for the whole drive. That should solve normal people issues and if you are also running something decent on those machines you are 100% covered.Thanks. Good points. So I need to prevent certain user accounts from accessing my second hard disk, which has storage.
What's the easiest way to do that?
I think the safest choice -- the choice most likely to do the job without causing conflicts -- is Binisoft Windows Firewall Control.How are you doing bro? I need your advice on my combo's configuration, please....
"Avast Free Antivirus + OSArmor"
I am using this combo but I actually don't have a Firewall module in my combo and I want to add a 3rd party Firewall into that combo
which does not overwrite or conflict with any of both softwares of the combo.
Questions
1. Which of the following Firewalls do you recommend to be added into my combo and why?
- Comodo Firewall
- Xvirus Personal Firewall
- SpyShelter Firewall
- ZoneAlarm Firewall
- FortKnox Firewall
2. Avast Free Antivirus includes a BB which is Behavior Shield. I wonder if that aspect of Avast would be redundant with some aspects of OSArmor or not?
Any advice is welcome, Thank you for your good assistance bro
Best regards,
Rebsat.
Right now I am trying out Comodo (just the firewall, everything else disabled) + Windows Defender (at high settings, with exploit guard and protected folders) + OSArmor + Appguard.1. Which of the following Firewalls do you recommend to be added into my combo and why?
- Comodo Firewall
- Xvirus Personal Firewall
- SpyShelter Firewall
- ZoneAlarm Firewall
- FortKnox Firewall
Can you run OSArmor with another av?@Windows_Security I guess this is the place for me to ask you about your configuration for OSArmor, rather than hijacking @Umbra's thread...
Yes, OSA is designed to accompany your AV. It is not an AV and is not a replacement for an AV.Can you run OSArmor with another av?
Appguard, even out-of-the-box settings, should prevent any malware activity that could affect a different user account, because:
1 Even if malware is signed, it won't be able to write to system space, because it first executes in user space.
Yes, locked down mode with extra tweaks is much more secure.I once heard of a person using one of Appguards whitelisted trusted sig for malware to test. That is why I run it locked down mode with extra tweaks to PowerShell ect.
I also did the registry hack to set powershell to constrained language.
First of all, you should disable the old, deprecated version of powershell, you can do this from "turn windows features on or off", in Control Panel/Programs and Features.Does the reg hack cover just powershell.exe in sys 32 & 64 folders or does it also cover PowerShell in the syswow 32 & 64 folders too? And does it cover powershell_ise.exe in the sys 32 and syswow folders?
Thanks