Andy Ful
From Hard_Configurator Tools
Thread author
Verified
Honorary Member
Top Poster
Developer
Well-known
- Dec 23, 2014
- 8,484
Safe email on SUA.
Although there are known tools that can restrict Windows system/software to support AV protection, they are usually system-wide. So, they are not good solutions for average people without the occasional support of advanced users.
But, there exists a partial solution that I called “Safe email account“. The main idea is preparing a special Standard User Account with strong restrictions applied only to this account (non-systemwide). Such an account can be adjusted for using the email client and some applications that are essential for emails like a web browser, document/ebook reader, document editor (DOC, DOCX), picture viewer, etc. This will separate and neutralize the most casual vector of attack from the rest of the user activities.
Such an account can be highly restricted because it will be used only for email maintenance - no software updates, no software installations, and no admin tasks. It will require the initial configuration, but nothing else. After that, the average user will be able to easily use it without any help from an advanced user.
I think that the below restrictions can be applied:
The user can simply sign in, next run the email client to easily access several email boxes. Even when the phishing link or email attachment is going to introduce something malicious (malware or exploit), it will not execute or will be neutralized. After finishing the work related to emails, the user can sign off and work on the normal account (no restrictions).
What Windows built-in features can be applied?
Software Restriction Policies and some other policies in HKU Registry Hive (the SID of the user account needed).
How they can be applied?
The restrictions can be introduced by running a simple application (with ON/OFF switch) from the chosen Standard User Account. Creating such an application is rather easy (although it is only in my mind for now).
The restrictions can be also applied/removed by importing two REG files (the user SID has to be replaced by the SID of the concrete account).
Is it safe?
Yes. The restrictions do not apply to other user accounts. Furthermore, If the user does not like it, then he can simply sign in to the Administrator account and remove the "Safe email account".
What do you think about such protection? Can it be useful for average users or MT members?
Although there are known tools that can restrict Windows system/software to support AV protection, they are usually system-wide. So, they are not good solutions for average people without the occasional support of advanced users.
But, there exists a partial solution that I called “Safe email account“. The main idea is preparing a special Standard User Account with strong restrictions applied only to this account (non-systemwide). Such an account can be adjusted for using the email client and some applications that are essential for emails like a web browser, document/ebook reader, document editor (DOC, DOCX), picture viewer, etc. This will separate and neutralize the most casual vector of attack from the rest of the user activities.
Such an account can be highly restricted because it will be used only for email maintenance - no software updates, no software installations, and no admin tasks. It will require the initial configuration, but nothing else. After that, the average user will be able to easily use it without any help from an advanced user.
I think that the below restrictions can be applied:
- All scripting blocked (CMD, Windows Script Host, PowerShell, MSI installers).
- All unsafe file extensions blocked (like over 170 Paranoid Extensions in H_C).
- Popular file extensions allowed.
- Office macros blocked or office documents opened by the editor which does not use macros at all (like Softmaker Office free).
- All LOLBins blocked (also task scheduler).
- The access to the autorun registry keys blocked.
The user can simply sign in, next run the email client to easily access several email boxes. Even when the phishing link or email attachment is going to introduce something malicious (malware or exploit), it will not execute or will be neutralized. After finishing the work related to emails, the user can sign off and work on the normal account (no restrictions).
What Windows built-in features can be applied?
Software Restriction Policies and some other policies in HKU Registry Hive (the SID of the user account needed).
How they can be applied?
The restrictions can be introduced by running a simple application (with ON/OFF switch) from the chosen Standard User Account. Creating such an application is rather easy (although it is only in my mind for now).
The restrictions can be also applied/removed by importing two REG files (the user SID has to be replaced by the SID of the concrete account).
Is it safe?
Yes. The restrictions do not apply to other user accounts. Furthermore, If the user does not like it, then he can simply sign in to the Administrator account and remove the "Safe email account".
What do you think about such protection? Can it be useful for average users or MT members?
Last edited: