What is our primary use case?
We provide IT security or cybersecurity services to our customers. ThreatLocker is a key component of our security stack, and we roll it out to every one of our customer's endpoints. It's not an optional component, but a must-have because we are strong proponents of zero trust.
We provide remote monitoring and management services, which can be considered remote IT security for our clients. Our clients have minimal interaction with ThreatLocker Protect directly. It is one of the security tools we install on their systems to secure their networks and end devices. More importantly, it allows us to manage and control the specific applications and services running on their endpoints.
For instance, we can maintain a pre-approved list of applications that are allowed to run in the environment, while preventing unauthorized applications from executing. Even for permitted applications, we implement additional security measures.
ThreatLocker's unique capabilities are particularly evident in its handling of Adobe Acrobat, a common PDF reader. PDFs can be exploited by malicious actors, or hackers, to gain access to systems. Typically, a user clicks on a PDF, it opens, and without their knowledge, malicious code executes on the system, interacting with other components to enable hacker access.
With ThreatLocker, we can restrict Adobe Acrobat to only accessing the official Adobe update servers on the internet, preventing it from accessing any other websites. Additionally, we can restrict Adobe's access to other applications and underlying files on the computer, preventing hackers from utilizing the program to compromise the system.
ThreatLocker is a cloud-based endpoint protection platform that utilizes endpoint agents installed on each device. The deployment of these agents can be automated through Microsoft Intune or RMM, depending on the specific scenario. The ThreatLocker portal is also cloud-based, and once the agent is installed, it communicates directly with the ThreatLocker cloud. One of the key advantages of ThreatLocker is the instantaneous implementation of changes made in the cloud to the endpoints. This ensures that devices are always protected with the latest security policies.
How has it helped my organization?
Administration of Allowlisting is incredibly simple, and ThreatLocker provides numerous methods for approving applications and ensuring their legitimacy. One of ThreatLocker's strengths is its dedicated team that continuously monitors applications for changes. For instance, Microsoft's infamous "patch Tuesday" releases require thorough vetting of all patches. If not vetted, ThreatLocker will block them. ThreatLocker's team proactively prevents these issues by adding validated applications to the system. Occasionally, an unpopular application may slip through their team's detection. In such cases, the process for blocking is straightforward. Upon receiving an alert, we can examine the application and its characteristics, including its files. Directly from ThreatLocker, we can verify the application against known repositories that track applications based on their hash or unique Digital DNA to determine if it's a registered application with a known location. Additionally, we can check for any malicious characteristics. Based on this assessment, we can take two actions: either approve the application or utilize ThreatLocker's newly introduced virtual sandbox environment. With a simple click, we can isolate the blocked file in a virtual environment. ThreatLocker creates a separate Windows screen, copies the file over, and executes it within the environment for two purposes. The first is for capturing the file's signatures and any missing elements. The second is for observing the file's behavior in a controlled environment.
Software approval requests for end users are simple. The end user will typically see a small box, which can be customized. We can create a custom appearance or use the ThreatLocker standard box that appears and states that the application has been blocked. There is a box where users can justify the application and explain why they need it. They can then request approval. This is their interaction in terms of requesting approval. On the backend, either the Cyber Heroes or our team will review and approve everything. If the application is approved, the users will receive another small box in the lower right-hand corner of the screen stating that the app has been approved and can now be run. The box will have a button that users can click to run the previously blocked application.
The combination of Allowlisting and Ringfencing is a key advantage of ThreatLocker, particularly in preventing applications from accessing unauthorized internet sources or tampering with sensitive system programs. Allowlisting explicitly permits specific applications to run, while Ringfencing imposes additional restrictions on their behavior. This layered approach ensures that applications can only execute authorized actions and cannot escalate privileges or compromise system integrity. Allowlisting simplifies application control by eliminating the need to define granular permissions for each application. Instead, administrators can simply check a few boxes to whitelist trusted applications. However, for more advanced configurations, ThreatLocker provides granular control over application permissions. Ringfencing acts as a safeguard, akin to guardrails along a mountain road. Just as guardrails prevent vehicles from plunging over the edge, Ringfencing prevents applications from engaging in unauthorized or malicious activities. This additional layer of protection provides peace of mind and enhances overall security.
Establishing trust is crucial, and with Allowlisting, we have a thorough vetting process to ensure applications meet the necessary security criteria. We first evaluate whether the application is truly needed in the environment or what its purpose is. Additionally, we can identify who initiated the request. Furthermore, ThreatLocker's portal provides access to historical data on applications, including file hashes, which act as unique digital DNA. This allows us to verify whether the application is in its original form and check for any known threat advisories. This comprehensive information empowers us to make informed decisions about whether to Allowlist or deny an application based on our findings. Additionally, we can sandbox the application to observe its behavior in a controlled environment and detect any malicious activities. This rigorous vetting process ensures that only trustworthy applications are Allowlisted.
ThreatLocker allows us to maintain consistent environments by providing a central repository that tracks which applications are authorized to run. This simplifies application management and ensures that only approved applications are installed. Additionally, ThreatLocker enables us to control bloatware, which can often contain vulnerabilities. We can prevent bloatware from executing within our environment, further enhancing security. ThreatLocker's zero-trust architecture, including application control, ringfencing, and other features, strengthens our overall security posture. With ThreatLocker, we no longer need to worry excessively about end users clicking on malicious emails, as the embedded code cannot execute due to the restrictions we have implemented. Overall, ThreatLocker's zero-trust architecture is mandatory across all clients in our environment. It is not an optional security measure; it is essential for doing business with us. ThreatLocker empowers us to control our environment and ensure comprehensive security.
ThreatLocker has helped us reduce our helpdesk tickets by preventing rogue applications from running in our environment. This significantly reduces the overhead associated with managing tickets. With ThreatLocker, we have complete control over which applications are allowed to run, so we don't have to worry about users clicking on something they shouldn't. Occasionally, we do receive requests from end users who are trying to run blocked applications, such as games. These requests are denied and do not become tickets. Overall, ThreatLocker has significantly improved the standardization of our environments and reduced the overhead associated with managing user-related tickets. It has given us complete control over which applications can run in our environment, and we rarely have any end-user-related tickets as a result.
Many tickets are created due to an inconsistent or non-standardized user environment. Users encounter differences in software configurations between systems, leading to curiosity and clicking on unfamiliar items. In the current era where 96 percent of security incidents originate from phishing email clicks, we have clear evidence, supported by metrics, of the impact and consequences of such actions within client environments. By standardizing the environment and utilizing a common system like ThreatLocker, which enables whitelisting, blacklisting, or implementing guardrails, the number of tickets and user-generated noise can be significantly reduced.
Our current security stack is very lean and well-integrated. Whenever I attend a trade show or conference with vendor halls, I'm always approached by vendors trying to sell me something. ThreatLocker already does what they're offering, so there's no need for additional purchases. From a cost perspective, ThreatLocker has allowed us to consolidate and save significantly. Additionally, without ThreatLocker, we would likely need six or seven different tools to achieve the same level of security, further reducing costs.
What is most valuable?
We use ThreatLocker's Allowlisting to whitelist specific applications and prevent unauthorized software from running.
We utilize Ringfencing to establish guardrails around implementations, ensuring that applications operate within defined boundaries.
We leverage network access control to granularly control interactions between computer systems and servers. This enables us to restrict communication between specific applications, even within a locked-down environment.
We employ storage control to impose additional security measures on data storage. This includes controlling access to network shares, network files, and folders, as well as USB storage devices. We can whitelist specific devices based on their serial numbers or allow access based on predefined conditions.
We rely on ThreatLocker's Cyber Hero support, which provides exceptional assistance and responsiveness. At any time, we can initiate a chat session and receive immediate support. If the issue requires escalation, it is promptly handled.
Cyber Hero support also plays a crucial role in vetting application updates. When a user attempts to install or update an application, and the update has not been approved from a security standpoint, it is blocked by ThreatLocker. A notification is presented to the user, informing them of the block and providing an option to justify the application's need. These requests are then reviewed by ThreatLocker's Cyber Hero support team, who evaluate them against our security criteria and make an informed decision to allow or deny the application.
We utilize ThreatLocker's elevated control feature for applications that require administrator-level access. We avoid granting full administrative privileges to end users, as this elevates the risk of compromise if the device is infiltrated. Instead, elevated control allows us to precisely define the execution conditions for specific applications, such as QuickBooks updates. By verifying the application's signature and certificate, we can enable the update to run with administrative privileges while restricting the user's overall administrative access.
Integrating ThreatLocker with other products is simple and only requires a few clicks. ThreatLocker's deployment is also very straightforward. The company provides extensive and well-written online documentation, which is continuously being improved. They also offer a variety of training resources, including university courses, training videos, webinars, and conferences. I have no complaints about the level of support and knowledge transfer provided by the company. ThreatLocker is also developing a new reporting tool, which I had the opportunity to beta test. The company has also been showcasing the new reporting tool at conferences. The new reporting tool provides a level of detail that is unmatched by any other product on the market.
What needs improvement?
From a reporting perspective, enhancing the ability to customize reports would be beneficial. This could include the option to export reports to a Word document for further tailoring, allowing users to add their own executive summaries and additional content.
For how long have I used the solution?
I have been using ThreatLocker Protect for five and a half years.
What do I think about the stability of the solution?
ThreatLocker's development team is capable of releasing beta versions of upcoming releases. Our organization has a policy against deploying beta code due to potential stability and security issues. We don't want to inconvenience our customers or use them as guinea pigs. Overall, ThreatLocker has been a stable platform. However, the threat landscape changes rapidly, and even vetted releases can have minor glitches, such as applications being categorized differently. This can sometimes have adverse effects. However, ThreatLocker's team is very responsive and quickly addresses any issues we bring to their attention.
What do I think about the scalability of the solution?
I haven't identified any inherent limitations or restrictions, or let's say, a ceiling. I'm aware that ThreatLocker is deployed in large corporations around the world. So, they can accommodate organizations of all sizes, from single-person entities to Fortune 500 companies. It's undoubtedly scalable. When I evaluate scalability, I consider not only the number of endpoints and various supported components but also the ability to adapt to the evolving threat landscape. ThreatLocker has certainly been doing that with the introduction of new products and services, as well as the continuous evolution of the platform as a whole.
How are customer service and support?
ThreatLocker is the only company where, regardless of the time of day or whether it's a holiday, I can get immediate support by just jumping into the portal, clicking on the chat, and having someone respond. And it's not just a bot; it's a real Cyber Hero who is ready to assist. They even offer the option to request a Zoom link so that we can have a face-to-face meeting to explain our scenarios and share our screens. If the Cyber Hero is unable to resolve the issue, there are two additional levels of support available online 24/7. We've dealt with many vendors, but we've never experienced this level of support.
How would you rate customer service and support?
How was the initial setup?
The implementation process was relatively straightforward. ThreatLocker provides us with granular control over almost every aspect of the system, which is one of its key advantages. Upon initial installation, ThreatLocker enters a learning mode where it identifies and catalogs all applications within the environment. We can then determine when to transition ThreatLocker from learning mode to full secure mode, with options ranging from one day to 30 days. In our case, the transition to full secure mode was relatively seamless. We completed the learning phase and had ThreatLocker fully operational within 30 days.
We utilize Microsoft Azure and Intune to manage the majority of our services. In this instance, we employed a PowerShell script provided by ThreatLocker, tailored to our specific environment, and deployed it via Intune. Intune ensures that every device is enrolled. Upon defining and adding the PowerShell script, Intune automatically distributes it to the endpoints, completing the installation process. The deployment process is simple.
We don't require many people for the deployment of ThreatLocker.
What was our ROI?
ThreatLocker has been instrumental in our ability to standardize and secure our environments, enabling us to replicate them consistently. This standardization has significantly reduced overhead, as we no longer need to rebuild the infrastructure for each new client or prospect. Furthermore, the controlled environment that ThreatLocker has facilitated resembles a well-policed community, where crime rates are low, residents are content, and property values are rising. In contrast, an uncontrolled environment akin to one with inadequate law enforcement would result in chaos. Consequently, ThreatLocker has allowed us to operate efficiently and effectively, minimizing support tickets, eliminating security concerns, and ultimately contributing to our profitability.
What's my experience with pricing, setup cost, and licensing?
Today, the term "zero-trust bubble" is used to describe the growing number of vendors offering zero-trust security solutions. However, I've observed that the IT security industry, as a whole, tends to over-hype new technologies with acronyms and buzzwords without fully understanding their implications. When I examine the current zero-trust landscape and compare it to other security bubbles like endpoint detection and response, secure access service edge, and so on, I find ThreatLocker's pricing to be reasonable for the services it provides.
Which other solutions did I evaluate?
Previously, we had not implemented any solutions for zero trust because it was a relatively new concept at the time. We were exploring various options to gain more granular control over applications running on separate networks within our environment. Our goal was to standardize and normalize these applications while preventing the execution of unauthorized applications or scripts. However, we were unable to find any solutions that met our specific requirements. When we were introduced to ThreatLocker, we evaluated other available solutions and found that ThreatLocker offered the most comprehensive feature set.
There was nothing else in the market at the time that was doing what ThreatLocker was doing or even attempting to do anything with Zero Trust. The CEO and co-founder visited my office and provided me with an in-depth explanation of the product, its vision, and its future plans. This was sufficient for me because, first and foremost, what matters most to me, especially in the security industry, is having personal connections with my vendors. I don't want to be just another customer. I specifically want to know that I have people I can call on my speed dial when something goes wrong. And that's the kind of relationship I have with ThreatLocker.
What other advice do I have?
I would rate ThreatLocker Protect nine out of ten. There are many security products available today that companies like mine utilize, and some of these products could be replaced with ThreatLocker. However, ThreatLocker is one of those tools that I consider indispensable to our security stack. We have such a strong conviction about this because we understand its capabilities and have seen its effectiveness firsthand. While a significant portion of our work is proactive security, we have also been called upon by companies who have experienced ransomware attacks. In these situations, we have been able to assist them in their recovery efforts. If these companies had ThreatLocker in place, they would not have been vulnerable to these attacks. This reinforces our unwavering belief in the value of ThreatLocker.
We implemented ThreatLocker from the outset within our environments. Therefore, it's difficult for me to compare it to previous solutions as it has become an integral part of our security framework. When I interact with colleagues who don't use ThreatLocker, I hear a lot of complaints, particularly regarding ticketing and the time wasted on text-based communications. I would say that the vast majority of these issues could be avoided if they had ThreatLocker in place.
The company as a whole has experienced and addressed all the concerns that have been raised. Firstly, they are continuously developing and enhancing their product offerings, which include not only the product itself but also the accompanying knowledge base and support structure. Most recently, we have been beta testing their latest portal upgrade, which is remarkably impressive. Ultimately, if I were forced to reduce my security stack to just one or two tools, ThreatLocker would undoubtedly be among them.
Occasionally, a less popular application pushed by a publisher may be flagged by ThreatLocker. In such instances, customers may inquire about the issue. However, once the reasoning behind the flag and the importance of our application vetting process to safeguard their environment are explained, the concerns typically subside.
ThreatLocker's user interface has undergone a significant transformation since its inception. The new beta portal, which we now have access to, is a vast improvement over the original portal. It is both aesthetically pleasing and functional, fulfilling all of its intended purposes. In terms of UI customization, I see little room for improvement. One area where I always seek enhancements is integration with third-party products, particularly PSA platforms. We utilize ConnectWise Manage, now known as ConnectWise PSA, and it seamlessly integrates with ThreatLocker. During a recent client audit, I compared the actual numbers to the PSA's reports, and everything matched up perfectly. When I consider ThreatLocker as a whole, I am impressed with not only the product itself but also the company's culture and commitment to innovation. They continuously invest in thought leadership initiatives, such as webinars, training programs, the ThreatLocker University, and their annual conference. These efforts demonstrate their dedication to providing their customers with the best possible experience. I have no specific wishlist items for ThreatLocker. I am genuinely satisfied with their product and overall approach.
We began realizing immediate value from ThreatLocker, as it provided us with the ability to view blocked applications, scripts, or files within the environment through its unified audit feature. This allowed us to quickly identify and eliminate unwanted software from our environment. Additionally, we could revisit applications that had been vetted or cataloged and decide to block them if they were no longer deemed necessary. Overall, the time to value for ThreatLocker was within the first 30 to 45 days.
ThreatLocker is used by all of our clients and on all of our endpoints. We currently have over 250 endpoints protected by ThreatLocker.
From a maintenance standpoint, ThreatLocker is relatively straightforward. While application signatures inevitably change, the most frustrating aspect is the lack of consistent code signing by software publishers. Despite the current cybersecurity emphasis and efforts to minimize risk, it's baffling that reputable software developers often fail to sign their code. This necessitates an additional vetting process to verify the code's authenticity and ensure it hasn't been tampered with. One of ThreatLocker's strengths is its audit service. Upon request, their system engineers conduct a thorough audit of our client's environment via a Webex or Zoom session. They examine what's being blocked, what's not, our configurations, best practices adherence, and potential changes. This proactive approach ensures we're on the right track and adhering to best practices.
First and foremost, it is crucial to thoroughly understand the clients' environments and develop a tailored strategy for each one before implementing ThreatLocker. A one-size-fits-all approach is ineffective as every client environment has its unique set of applications and requirements. Thorough education is key. When rolling out ThreatLocker, we spend a considerable amount of time educating our customers about its purpose, functionality, and potential impact. We address their concerns and explain the rationale behind the restrictions. This education process should be ongoing for end customers. In the technology industry, there is a tendency to focus on the latest bells and whistles, neglecting the importance of educating end users about the benefits and implications of new technologies. This oversight can hinder the successful implementation of security solutions like ThreatLocker. It is essential to dedicate sufficient time to educating end users to ensure a smooth and effective rollout.
Know the environment. Before implementing ThreatLocker, thoroughly document and understand the client's environment. Initially, run ThreatLocker in learning mode to capture all applications used in the environment. Fine-tune the policy. Before switching to secure mode, collaborate with a Cyber Hero or solutions engineer to identify and address potential application conflicts or redundant applications. Leverage ThreatLocker University. Encourage the team to participate in ThreatLocker University training to gain in-depth product knowledge. Test in the environment first. Before deploying ThreatLocker to clients, thoroughly test it in your own environment to gain familiarity and expertise. ThreatLocker is not suitable for every organization. It is not intended for those who lack a serious commitment to security or are unwilling to invest the time and effort required to properly vet and configure the product for their specific environment. ThreatLocker is most effective for organizations that are willing to take advantage of its comprehensive features and dedicated support to tailor the solution to their unique needs. Remember, the success of ThreatLocker implementation depends on thorough planning, education, and a commitment to security.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
