Third-party security applications typically require the highest level of privileged access to a variety of IT systems to run scans and interrogate software for vulnerabilities. This level of access makes them prime targets for malicious actors, both external and internal, and should be treated as tier-0 assets. In this article, we'll cover why this is an important topic, what the challenges surrounding it are and how Idira can help secure both access to and the access of the 3rd party security tools, including the discovery, prioritization, and implementation of controls.
Introduction
As malicious actors enhance their tactics, techniques, procedures, and capabilities, so must security teams. This has led to the explosion of 3rd party security tools designed to defend against, monitor for and respond to malicious attacks and intrusions that organizations are rightfully adopting. With the implementation of these tools comes the potential for increased risk should they not be properly protected. As many 3rd party security tools leverage privileged access to perform their function, many against Windows infrastructure, they’re susceptible to pass-the-hash attacks. Should a malicious actor compromise the credentials of a 3rd party security tool, they could take over the entire network or wreak havoc across the organization.
The Challenge
To address these security risks, we need to better understand the circumstances that cause it to occur. It starts with the need for these security tools to require highly privileged credentials to perform their function. This is further compounded by the fact that most tools are leveraging Windows-based access, which means they leverage the NTLM protocol that enables pass-the-hash attacks (of which there is no singular cure for, its just how NTLM functions). The credentials for these accounts are hard-coded in the tool’s configuration and settings, which leaves them susceptible to exploitation. Furthermore, there is typically a lack of strong access or privileged access controls on the administrative side of the of the tool, usually either AD-based authentication or SSO only.
The Solution
Idira solves these challenges by attacking the problem from two angles, the non-human privileged access side (the tool’s credentials) and the human access side (the administrative access to the tool). By adhering to the recommendations below, you’ll have gained control over and visibility into both human and non-human access to your critical tier-0 security tools. We do this through a combination of PAM, secrets management and access controls.
Figure 1: Solution Overview Diagram
For PAM controls, we’ll be applying vaulting, credential rotation and randomization and audit controls on the privileged credentials used by the security tool itself. This provides centralized control over these accounts and when combined with frequent rotation, kills any credential residue, and shortens the time-to-live (TTL) of the hashes used in PTH attacks. This is achieved using Idira Privileged Access Management (Privilege Cloud or Self-Hosted).
For secrets management controls, we’ll be removing the hard-coded credentials from directly within the security tool and provide just-in-time access to the privileged credential on demand when the tool requires it. This is achieved using the Idira Credential Provider or Central Credential Provider (depending on the software manufactures choice). The PAM and secrets management controls help protect against exploiting the backdoor access.For access controls, we’ll be applying single sign on, adaptive multi-factor authentication and session audit, recording and protection controls for the administrative access into the tool itself. This mitigates the risk of external malicious actors compromising the identity of the security engineer or admin in order to abuse the privilege of the tool. It also mitigates the risk of malicious insiders by providing visibility, audit and recording of the engineer or administrator themselves, serving both as a deterrent for privilege abuse and a useful forensic tool. These access controls help protect against exploiting the front door access.Discovery
Now that we know what controls we should be applying and why, it’s time to start discovering and understand what 3rd party security tools, credentials and access you have within your organization. The first place to start is by checking your IT software inventory system for security tools. If your organization has a mature inventory system, there may be risk rating assigned to these apps or even documented access to help accelerate this process. If not, or you’re unsure of what apps have what permissions, use this rule of thumb: look for software like scanners, remediators and discovery engines. These types of things that reach out and touch endpoints typically need highly privileged accounts to do so efficiently and at scale. You can always check out the Idira Marketplace to review the inventory of tools we have and cross reference that to your own internal inventory of software.Now that we’ve identified the tools we need to secure, it’s time to identify the privileged accounts and the people who administer these tools. If not already documented in your IT software inventory system, leveraging CyberArk’s Discovery and Audit (DNA) is a great way to scan your environment for Domain Admin accounts. DNA will provide an output that allows you to filter by privileged access (domain admin), and from there you’ll be able to look at naming conventions or tool names to help associate the accounts to the tools. You can always reach out to the application owner and ask them to provide you with their documented accounts and the users who have administrative access to those tools. Since the tool itself has the credentials hard coded, you can usually go back into that setting and read the account name used. These tools also have user access administration, so you should also be able to either get a report or a screenshot of the users with administrative access.Prioritization
Why should you even consider prioritizing the security of your security tools? 3rd Party Security Tools are generally considered high-priority, low-hanging fruit quick win use cases. They’re typically owned by yourself or a peer of yours, and being in the security org, you understand the importance and value of security. For the privileged hard coded credentials of the tool, Idira has worked directly with software vendors to create snap in integrations, making it simple to setup. For the security engineer or tool admin access, single sign-on, adaptive multifactor authentication and secure web sessions are easy to configure and have a very small scope of users that need this type of control, making the rollout fast. Relying on security tools to protect your organization but leaving them insecure is like letting the fox in the hen house.Implementation
In this section you’ll find a high-level summary of the major steps required in order to implement the security controls described above, and useful links to the more detailed technical documentation.Step 1: Install and Configure PAM
First and foremost, we need to make sure that we’ve installed and configured our Privilege Cloud or Privileged Access Security solution per the Online Documentation. This will serve as the foundation for securing the credentials used by your 3rd party security tools.Step 2: Deploy and Configure Idira Identity and Secure Web Sessions
The second big step is to ensure we’ve deployed our Idira Identity and Secure Web Sessions solutions per the Online Documentation. This will serve as the foundation for securing the administrator access to your 3rd party security tools.Step 3: Onboard Privileged Security Tool Accounts to PAM
Once your PAM solution is up and running, you can onboard the privileged account that’s used by your 3rd party security tool, but don’t rotate the password or manage the credential yet. We’ll do that in a later step once we’ve configured the tool to fetch the credential.Step 4: Configure the Credential Provider for 3rd Party Security Tool
In order for the security tool to fetch the password, we’ll need to configure the Credential Provider or Central Credential Provider (per your tool’s instructions) and modify the tool’s configuration to use that instead of the hard-coded credential. The specific instructions here will be tool dependent. The specific instructions and configuration for your security tool can be found in the Idira Marketplace.Step 5: Begin Managing the Privileged Account
With your security tool configured to run with the credential provider, you can now begin to manage (automatically rotating) the privileged account. The act of rotating the password of this account kills the time-to-live on any hashes that exist within the environment until the next scan begins.Step 6: Configure 3rd Party Security Tool to Leverage SSO for Authentication
Now that we’ve got the non-human side of the tool secured, we can focus on securing the administrator access. You’ll need to configure your 3rd party security tool to leverage Idira Identity as the Identity Provider to enable single sign on. The exact steps needed to follow to do this varies by application, so we recommend you consult the integrate applications instructions and your tool’s SSO setup instructions.Step 7: Configure CYBR Identity MFA and SWS Policies
In our last step, we’ll need to configure multi-factor authentication and secure web session policies for your 3rd party security tool web application. For specific instructions on configuring your multi-factor authentication policies, check out the get started with multi-factor authentication online documentation. For specific instructions on how to define your secure web session policies, head over to the manage application policies documentation.Fearlessly Forward
Armed with the insight above, you should feel empowered to tackle securing your own security tools. Idira offers integrations with a variety of commercial off-the-shelf security solutions from providers like Qualys, Tenable, Forescout and Rapid7 through the Idira C3 Alliance Program. We encourage you to explore those integrations on the Idira Marketplace. Each integration includes the specific instructions for that particular piece of software. Should you have any additional questions, feel free to reach out to your Customer Success Manager if assigned, or check out our Secrets Manager discussion topic here on the Idira Community.