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
NotPetya and Standard User Account
Message
<blockquote data-quote="Andy Ful" data-source="post: 659486" data-attributes="member: 32260"><p>UAC still works, but in a different way: no UAC alert, and no possibility to elevate processes started as standard user. If the malware is started by the user or it exploited an application ran as standard user, then the malware cannot elevate on such protected SUA.</p><p>This is not the same, as no possibility to run processes with higher rights. Some processes, like many scheduled system tasks, do not require elevation to start with higher rights - they start from built-in 'NT Authority\System' account.</p><p>If you happen to be infected via kernel exploit, then the malware is installed with system rights (no elevation), and SUA cannot save you.</p><p>It is true, that users have to log on as administrator, to execute their applications via 'Run as administrator' from Explorer context menu, or when performing software installations and application updates. With default UAC settings, those tasks require admin credentials on SUA.</p><p>Look also, at an Example in my thread :</p><p><a href="https://malwaretips.com/threads/user-account-like-a-castle.73633/#post-652203" target="_blank">User Account like a Castle</a></p><p></p><p>Edit.</p><p>One can bypass 'no elevation' SUA using tools that can log on as administrator (for example runas Microsoft tool). So, additional system hardening is necessary to protect administrator credentials:</p><p>; Default value CachedLogonsCount = 10 must be changed to 0 (restart the system).</p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]</p><p>"CachedLogonsCount"="0"</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 659486, member: 32260"] UAC still works, but in a different way: no UAC alert, and no possibility to elevate processes started as standard user. If the malware is started by the user or it exploited an application ran as standard user, then the malware cannot elevate on such protected SUA. This is not the same, as no possibility to run processes with higher rights. Some processes, like many scheduled system tasks, do not require elevation to start with higher rights - they start from built-in 'NT Authority\System' account. If you happen to be infected via kernel exploit, then the malware is installed with system rights (no elevation), and SUA cannot save you. It is true, that users have to log on as administrator, to execute their applications via 'Run as administrator' from Explorer context menu, or when performing software installations and application updates. With default UAC settings, those tasks require admin credentials on SUA. Look also, at an Example in my thread : [URL='https://malwaretips.com/threads/user-account-like-a-castle.73633/#post-652203']User Account like a Castle[/URL] Edit. One can bypass 'no elevation' SUA using tools that can log on as administrator (for example runas Microsoft tool). So, additional system hardening is necessary to protect administrator credentials: ; Default value CachedLogonsCount = 10 must be changed to 0 (restart the system). [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "CachedLogonsCount"="0" [/QUOTE]
Insert quotes…
Verification
Post reply
Top