ESET PROTECT Enterprise Reviews

I work with another ESET solution called EDR and XDR.

I am working with ESET PROTECT Enterprise and ESET Endpoint Security.

I am using ESET Secure Authentication, also called ESET EDR and XDR Enterprise solution.

I use ESET Inspect through the ESET Full Console, Enterprise Console.

I have bought ESET PROTECT Enterprise version, and everything is included inside.

For security reasons, I am using ESET PROTECT Enterprise for my antivirus and other functionalities.

From my personal perspective, it is easy to see on the console what's happening with each system. I'm able to monitor numerous things. This is a benefit because with all the systems connected, wherever the users are, from my system I can see what's happening on their system.

We have implemented certain policies in ESET PROTECT Enterprise, and it is working according to those specifications.

We are using ESET PROTECT on our workstations. We previously used it on the servers, but now it is mainly implemented on the workstations.

ESET PROTECT has a useful dashboard that makes management straightforward. It is easy to patch, update, and set up scheduled scans. It allows simple whitelisting and has a learning mode for new installations, which reduces false positives by adapting to typical user habits.

I use ESET PROTECT Enterprise for maximum protection on every computer in my organization. I work in a bank, and our security requirements mandate that we use only on-premise solutions.

One of the strong features of ESET PROTECT Enterprise is its ability to work well on old computers. This is crucial for us as we save resources by not having to upgrade hardware frequently. It is not resource-intensive and is easy to configure and use. Additionally, it provides good protection without requiring extensive hardware.

ESET Protect is mainly an antivirus. It has evolved over the years, building in additional features such as a web component that analyzes websites and prevents infections from malicious websites. It serves primarily as an anti-malware tool.

ESET's strong points are that it is an unintrusive, easy-to-maintain, and deploy antivirus solution. Once installed, it requires little to no manual intervention as it automatically updates itself. Its web component prevents infections from malicious websites, which enhances its anti-malware capabilities.

The documentation is of decent quality. I tend to look for documentation if I need it. But if I were a new person, I would want a quick start guide on how to set ESET up for a small company and handhold people through how to set it up, configure it, and deploy it. It's not difficult to do, but if I'd never seen it before, I'd be confused.

I would like to see more features on the reporting side of things, as in regularly reporting on what's going on with statistics. It might be there, and I just haven't come across it yet, but certainly, some more information on reporting would be good.

We've worked with their products since they came out about five or six years back.

Our primary use case involves approximately 180 workstations, 180 laptops, and office protection in our environment.

ESET PROTECT Enterprise is reliable. 

With every type of ESET product installed, we use ESET Protect to manage endpoint protection, including servers, workstations, laptops, and mobile phones. ESET Protect is a web-based console where you monitor ESET protection in the network. On-premises solutions are still prevalent, but customers are slowly transitioning to the ESET Protect cloud.

Without the ESET Protect console, a large number of endpoint clients can't be adequately managed. It allows you to create tasks, policies, dynamic groups, notifications, and a high level of automation for basic and advanced tasks.

We're able to manage the computers with ESET Protect. There are different ways to connect the computers to the server, and the common way is to deploy the agent through the domain cloud, like Windows servers. That's how we've deployed the agent for all the computers. I work with our organization unit and know which computer belongs to which department. Once the computer is connected to the server, I create two folders, static and dynamic. The dynamic folders are under the static folders. The reason that we use the dynamic is to automate the test. For example, if a computer doesn't have an anti-virus in any dynamic folder, we can install an anti-virus automatically.

We can create a task under the dynamic folder, which helps with implementing all the processes, installing an anti-virus, installing an agent, updating the anti-virus, or updating the practice system. For example, if a computer is under attack, we also create isolate folders when we detect the ESET because one of those texts automatically moves the computer to that dynamic folder, which isolates the computer from the network. Then, from that moment, we check what is happening and the issue. For example, with something like Trajan, we check if the malicious object was blocked or what happened with the malicious object. Then we check the computer errors, and the malicious object is blocked if we don't find anything. So we create a report and then resolve the computer, and it automatically moves again to the folder.

Another use case is how we allow users to connect devices to the computer. With ESET Protect, you can restrict or allow devices. For example, we like to allow the users to connect live phones, VSP, CDs, and the content filter wireless. Every month we have to give a report to the customer informing them that we have received an attack, blocked these attacks and resolved it. That's the kind of report we provide to the customer at the end of the month. We also use ESET Protect for the MSP and the users' administration.

Depending on your organization, you can set different rules. For example, for the executives, we can block malicious or adult websites and leave the game and streaming websites. For the office or a salesperson, we can restrict more things. It's helped us with restrictions and knowing which users we can provide permissions to and which users we need to restrict.