Reply to thread

Message

<blockquote data-quote="ForgottenSeer 107474" data-source="post: 1073730">[USER=32260]@Andy Ful[/USER]Since you know so much about build-in Windows security, may I ask you a question about the difference between UAC and running standard user.I started running standard user, because people who know (and Microsoft) always tell that UAC is not a real security boundary. But for a layman it is hard to understand the explanation. The reason most often provided by experts is that UAC is not a real security boundary while standard user is.Do I understand correctly&nbsp; (in layman&#039;s terms) that &quot;not a real/hard&quot; boundary is because:<ol>
<li data-xf-list-type="ol">A standard user does not has the elevated rights/tokens, while an admin with UAC has those tokens assigned, but they are shielded/disabled through UAC.&nbsp; Not in the list is a hard boundary, while in the list, but not granted at that moment, is a soft(ware) boundary. A standard user simply does not has those rights in his/her lists, so they can&#039;t be misused. 
 
</li>
<li data-xf-list-type="ol">Running with different user rights in same context/profile (e.g; Admin and Standard User), makes security complex (with confusing names as user rights, integrity levels, object permissions/process tokens/access control&quot;). An example is the Creater/Owner rights of files/folders created as (elevated) admin being inherited as standard user. 
 
</li>
<li data-xf-list-type="ol">Microsoft treats user boundary issues (e.g. Admin and Standard user) with higher priority and stricter rules than UAC issues or sometimes leaves them open by design (increasing the risk of&nbsp; vulnerabilities, I read something related to this about the UAC internal whitelist).</li>
</ol>Above with the WHH light execution whitelists (for all users, even higher rights than admin) and risky file blocking (for standard users) make a two user WHH light setup so strong?</blockquote>

[QUOTE="ForgottenSeer 107474, post: 1073730"] [USER=32260]@Andy Ful[/USER] Since you know so much about build-in Windows security, may I ask you a question about the difference between UAC and running standard user. I started running standard user, because people who know (and Microsoft) always tell that UAC is not a real security boundary. But for a layman it is hard to understand the explanation. The reason most often provided by experts is that UAC is not a real security boundary while standard user is. Do I understand correctly (in layman's terms) that "not a real/hard" boundary is because: [LIST=1] [*]A standard user does not has the elevated rights/tokens, while an admin with UAC has those tokens assigned, but they are shielded/disabled through UAC. Not in the list is a hard boundary, while in the list, but not granted at that moment, is a soft(ware) boundary. A standard user simply does not has those rights in his/her lists, so they can't be misused. [*]Running with different user rights in same context/profile (e.g; Admin and Standard User), makes security complex (with confusing names as user rights, integrity levels, object permissions/process tokens/access control"). An example is the Creater/Owner rights of files/folders created as (elevated) admin being inherited as standard user. [*]Microsoft treats user boundary issues (e.g. Admin and Standard user) with higher priority and stricter rules than UAC issues or sometimes leaves them open by design (increasing the risk of vulnerabilities, I read something related to this about the UAC internal whitelist). [/LIST] Above with the WHH light execution whitelists (for all users, even higher rights than admin) and risky file blocking (for standard users) make a two user WHH light setup so strong? [/QUOTE]

Verification