ManageEngine Log360 Reviews

We primarily use it for network-wide event monitoring and incident backtracking. It helps us identify what events caused certain incidents and understand how they happened.

It's also useful for incident tracking and investigating.

Having a functional event and log analyzer is crucial for any organization, especially considering ISO mandates. It has helped us meet those requirements and integrate all our functional-level needs. It has greatly facilitated our daily operations and compliance.

I use ManageEngine Log360 to manage company alerts. It is used in the security part, looking for issues in Active Directory and performing various tasks in Office 365.

Using ManageEngine Log360 has been a significant improvement for our company because it consolidates multiple tools into a single platform. This allows us to monitor various aspects, such as login times, network failures, and helpdesk attendance, that were previously unmanageable with older tools.

The solution helps us identify and manage any security-related incidents in the environment. It collects logs from various sources in the IT department, including end-user devices, antivirus software, UTM, firewall box in our data center, and server logs. It also gathers Aneesh's IP device logs from our network monitoring. Log360 brings all logs from different devices into a single platform and then runs intelligence to detect patterns of attacks. This allows us to set up automation rules so that we can take appropriate actions if such patterns are detected in the future. For instance, we can isolate a machine or a user account from our Active Directory and send alert emails to the IT admin, network admin, or CEO, depending on the nature of the incident. This automation capability allows us to respond promptly and effectively to various security incidents, blocking many routine attacks beyond the protection offered by antivirus software.

Deploying ManageEngine Log360 is challenging in terms of knowledge. They offer some out-of-the-box configurations, but determining the specific firewall or antivirus in use and importing logs from various software sources can be complex.

There is a need for more automation in such solutions, moving towards single-click deployments with minimal configurations. This would be more efficient than setting up complex systems, waiting for log collection, identifying issues, and relying on security experts to analyze logs and configure tools for future attacks. Incorporating more intelligence into the system could significantly improve this process, although the exact method remains unclear due to the evolving nature of cyber threats.

This is a module we use for our CM for the logging aspect.

We are collecting logs from our firewalls and we are collecting logs from the antivirus site. We are using Bitdefender for that. We are going to be implementing it so that all the logs flow through that mechanism, of course. Right now, these two are being planned at once.

Right now, we are still learning so I don't feel too comfortable saying something about the product very confidently. That said, everything's going fine. 

It is a combined toolset, ManageEngine. We can use a single toolchain for more than one purpose altogether and manage them from one administrative console. It's combined everything and will probably make some things easier for us.

The price is decent.

It is user-friendly.

We haven't had any stability issues.

It can scale.

The support has been great.

We usually use this solution as a pro system for purchasing and holiday approvals. They're usually a public system with MyCheck. We also use the repo system, including investing, and search systems for the organization.

The Sharecon feature is the most valuable. 

Our primary case for this solution is log management and finding vulnerabilities. It has file server monitoring and we use it to oversee specific file paths from file servers. For a few of them, we also do servers, Linux, and syslogs from network devices. We are trying to add it to our Windows Server, and they inform us whenever there are changes in their PaaS. We deploy it on-premises.

We have found the FIM (file integration monitoring) feature valuable.

If the client does not have much knowledge regarding the SOC and cyber, then ManageEngine Log360 is good because you can get default reports.

It is easier to deploy than are other SIEMs, which is great. You can also get an overview of your environment, which is very handy.

It's difficult to find which conditions have been applied to a report because they are provided by default by ManageEngine. However, with other SIEMs if you want to create a report, they provide details, like which conditions are triggering certain reports. This needs to be there in ManageEngine. It would be good to know which parameter has been applied to the report that is updating the system.

The on-premises solution is very slow. When I move to another tab inside Log360 or in the SIEM, even if my system is running on 36 GB and with a high processor, it takes a lot of time to get into the alert page or the search page.

It takes a long time to load a single page. With other solutions, such as Splunk, Securonix, Wazuh, I can quickly grab the details within seconds, but with ManageEngine, it takes a lot of time.

We basically utilize the tool to monitor security events based on a logon process such as bad passwords, lockout, etc.

We are using its latest version. We just upgraded it over the weekend.

It basically helps us. We have to stay in compliance with certain issues with some of our customers. We have to have these types of tools in place for protecting our network and our data. We're in the aerospace industry, so we have a lot of defense contracts. So, all those guys will make sure that we're protecting their information, and it does a good job in that aspect.