In the previous post, we discussed the fact that many organizations are creating security risks by handing out local admin rights to too many users. The goal is to keep users happy by providing them with more control of their devices and reduce reliance on IT, but the convenience factor shouldn’t outweigh the security risk. When normal users have the power to change configurations established by admins and override security measures, these users and their workstations become more vulnerable to attack.
One of the primary reasons for implementing access control policies and limiting local admin rights is to reduce the risk associated with stolen user credentials. The same principle applies to privileged accounts. Just as local admin rights should be reserved for IT teams that perform updates and maintenance, privileged account credentials should be reserved for only those users who legitimately need them.
A privileged account gives the user access to systems that house sensitive data, and/or the ability to modify settings and configurations. Local admin rights are one type of privileged account. Privileged user accounts provide users with administrative privileges and are sometimes shared among multiple admins.
A domain admin account is another type of privileged account that provides access to all workstations, servers and controllers within a domain. Service accounts are used by an application to interact with an operating system either at the local or domain level. Application accounts are used to access databases or other applications, which often include sensitive company data. Organizations can also create accounts to provide unprivileged users with admin privileges in case of an emergency.
While privileged accounts are essential to keeping an organization running, they create major security risks. These accounts often have access to financial account numbers, customer databases, proprietary information, passwords and other sensitive data. They have the ability to modify workstations, databases, servers and other critical assets. They can often create and delete user accounts. In a nutshell, both insider and outsider threats become more dangerous when they involve privileged accounts.
This is why privileged account management is so important. Privileged account management is a discipline that involves the authorization and monitoring of privileged accounts to reduce the risk of intentional and unintentional misuse. Privileged account management enables you to control access to disparate systems, grant access to specific systems only when needed, and revoke access when no longer needed. It also keeps passwords secure and provides an audit trail of privileged account activity.
Privileged account management best practices help protect systems and minimize the impact of data breaches. The first step is to maintain an inventory of privileged accounts, including who owns the account, the scope of permissions for each account, and the level of risk associated with each account and user. Keep privileged accounts to a minimum, eliminate shared accounts, and make sure passwords are complex and frequently changed.
To overcome a situation in which privileged accounts have unlimited access and capabilities, use the separation of duties and the principle of least privilege. The separation of duties ensures that no single user can perform all tasks in a system, and least privilege means users are only given the privileges required to do their jobs. Monitor and log account activity, review privileges regularly, and maintain a formal policy for both privileged account use and management.
Are privileged accounts and the lack of privileged account management making your organization more vulnerable to a major data breach? Let us help you get a handle on privileged accounts and implement a management strategy to minimize risk.
