We’re also not going to use a regular Windows 10 account connected to an Outlook or Hotmail address, because that increases the potential of getting hacked. The first thing we need is a new local account, which we’ll call “Admin.” We can’t call it Administrator, as that name is reserved for the hidden administrator account on the PC. For that reason we’ll leave the built-in account alone. Most experts caution against using the built-in administrator account, because it has free rein on your PC in a way that other account types don’t. Windows 10 does come with a built-in administrator account that we could activate, but we’re not going to do that. Still, removing administrator rights adds a little more security than leaving them intact on your everyday account. A key logger installed on your system could easily snap up your administrator password, for example, and a UAC pop-up can trick you into doing something you didn’t intend. Restricting admin privileges to a separate account helps mitigate, but does not entirely remove, these threats. Acting as an administrator an attacker could install more malicious software, run a command line program with elevated rights, delete user accounts, and more. If malicious software ever got onto your PC or it was hacked remotely there’s the potential for bypassing the UAC and using your account’s elevated privileges. The argument for doing this is pretty straightforward. You’ll still be able to authorize almost all the actions you do now from your everyday account, but you’ll have to enter a separate password each time instead of just clicking Yes or using your current account password. Then we create a separate local user account to act as administrator.
Nevertheless, we can improve the situation by removing administrator privileges from our everyday account.
The UAC is a little more robust than that description suggests. An example of a User Account Control dialog box in Windows 10.
0 kommentar(er)
