Apr 06 · 3 min read
In the previous post, we dealt with the importance of local admin accounts, the associated security risks, and the need for managing them properly. In this part, let us analyze the pros and cons of different approaches to managing the local administrator accounts.
Before getting into the details, let us examine the various efforts made by Microsoft in managing privileged access.
A vast majority of vulnerabilities in Windows environments are related to the local admin accounts. Microsoft was obviously concerned about this fact and made sincere efforts to find a solution. First, they came up with the concept of User Account Control (UAC), which allowed administrators to log on to workstations with standard privilege and then use “Run as” to elevate rights on-demand. UAC, no doubt, was a brilliant concept, but it too was susceptible to pass-the-hash attacks, besides introducing several operational challenges.
Another significant approach was the Privileged Access Workstation (PAW), which involves separating administrative accounts from normal user accounts - physical separation of standard and privileged access. PAW requires users to access privileged accounts from a dedicated, hardened, locked-down device that is only used for privileged activities. PAW is not to be connected with the internet and won’t accept inbound connections. PAW implementation is not something that is simple and straightforward. It also introduced the burden of maintaining a separate infrastructure. User experience was severely constrained.
Of all the attempts by Microsoft, perhaps the most successful one is the introduction of the Local Administrator Password Solution (LAPS). LAPS enables IT organizations to randomize the passwords of domain-joined local administrator accounts at periodic intervals. This ensures that the local admin accounts are assigned with strong, unique passwords that are periodically changed.
LAPS revolves fully around the Active Directory to manage the passwords of local administrator accounts. The local admin passwords are centrally stored in the Active Directory against the respective machine objects. Authorized users can retrieve the passwords when access is needed.
Through Group Policy, LAPS enforces strong, unique password usage. LAPS automatically identifies password expiration and generates a new password. Even if an attacker gains access to one local admin account, chances of lateral movement become remote. This saves your other endpoints and accounts in your network from attacks.
LAPS is very simple. It is tied to the AD and can manage local administrator accounts passwords. Nothing more. So, this simplicity is both a strength and a weakness. Its scope is too narrow.
Some of the limitations are:
While LAPS serves as a great tool to manage only the local admin accounts, it doesn’t fit the needs of most organizations, which are required to secure privileged access in its entirety.
This is where the Privileged Access Management (PAM) solutions come into the picture.
LAPS is undoubtedly a great solution. But its usage is strictly limited to local admin accounts. It cannot offer holistic privileged access security much needed by the enterprises. A comprehensive PAM solution can help you take total control of privileged access, including local admin access across the organization. PAM solutions deal with all aspects of privileged access - centrally controlling, auditing, monitoring, and recording all access to critical IT assets.
Some of the significant advantages of PAM solutions include:
From the foregoing, it is clear that organizations require a comprehensive PAM solution like Securden Unified PAM for holistic security.
In this part, we have discussed how to automate the best practices when you decide to retain the local admin accounts. Another approach to mitigate the security risks is to eliminate the local admin accounts altogether. Let us discuss the merits and demerits of this approach in the next post.
Local Admin Accounts Management: Microsoft LAPS Vs. PAM (Part-2)
In the previous post, we dealt with the importance of local admin accounts, the associated security risks, and...
Apr 06 · 3 min read
Top 10 password policy recommendations for sysadmins in 2021
Passwords are omnipresent in our personal and business digital environments. An average person has at least...
Apr 01 · 6 min read
Local Admin Accounts - Security Risks and Best Practices (Part 1)
We are all too familiar with the local administrator account that gets created automatically when installing a Windows...
Mar 19 · 4 min read
Poor password security practices cause massive security breaches
Weak passwords, password reuse, password sharing, hard-coded credentials, lax measures to storing credentials...
Mar 13 · 6 min read
Florida Water Treatment Plant Hack: A Wake-Up Call to Strengthen Basic Security Measures, Password Hygiene
One of the worst fears of humanity came true last week. Ever since cyberattacks started increasing in variety affecting organizations...
Feb 13 · 4 min read
Remote work, pirated software, and local admin rights: A deadly cocktail
Endpoints are increasingly becoming an entry point for malware. It has been a common practice to grant local admin privileges to the end users on their ...
Dec 08 · 3 min read
Securden vs. Competitors: A Story of Point-and-Click Simplicity vs. Complex, Illusory Superiority
The story of how a large government agency eliminated admin privileges on endpoints and implemented on-demand application elevation using ...
Oct 29 · 3 min read