The initial setup was complex.

I'd rate it an eight out of ten in terms of the ease of setup. We implemented it in a few weeks, but it took time to normalize and pass all the logs. It took a few weeks to set up things. In a few months, we had a fully exploitable solution.

It is very simple. There is a virtual machine that you download, and this virtual machine has everything in it. There is nothing for you to really do. You just download and install it, and once you have the machine up and running, you're good to go.

The implementation took three months. I had a complete listing of my log sources, so I just went down the list. I started with the most important logs, such as DNS, DHCP, Active Directory, and then I went down from there. We have 33 sources being collected currently.

The initial setup was a little bit complex. However, it is not complex for users with experience using the solution. I rate the initial setup a six out of ten.

We did the Azure setup of LogPoint and it was very easy and straightforward. The process took us less than 15 minutes.

The initial setup was straightforward. It was very easy, however, in the beginning, there were some errors and those errors were based on some bugs in the software. It's been worked on and so now it's fixed, however, beyond that, it was pretty straightforward, pretty easy.

You only need one person to do a deployment, however, I recommend three, it depends on your organization You basically need a system administrator that can deploy it. Configuration needs to be done by a security analyst.

There is continued maintenance required. Both of the roles that I just described are needed for maintenance, constant maintenance.

We had the vendor for the setup, but it wasn't very complicated. Even though our architecture is a little bit complicated, the setup was quite easy. 

We first started with the PoC, and then we kept the PoC and added two more services. So, it took a long time because we tested the solution very thoroughly before buying it. The vendor let us test it for a very long time. It took us about a year.

The product is straightforward to install as we already have a system snapshot. We downloaded the VMware template and changed the server's admin passwords, time zone, and hostname. It requires an hour to complete. I rate the process a ten out of ten.

It was average. LogPoint is not as complex as some of the other more complex products, such as ArcSight and enVision. I would rate its initial setup a seven out of ten in terms of ease.

It took about six months with fine-tuning, et cetera. We had to bring it live and have all the angles corrected. It was up and running in a couple of weeks, but of course, it takes some time for specific development for the use case that we needed.

Setting up a SIEM tool is never easy. It is very complex because of the components that are involved. You have to onboard all the devices that will be communicating with the tool. It is tedious. You need to get it right. That's the whole strategy.

For its maintenance, we have a two-man IT department, which includes me and somebody else.

The initial setup was straightforward. Usually, we can deploy the solution within three days. We usually take two days and keep an extra day for a buffer, just for fine-tuning some policies and things like that. For a small deployment, one person is enough.

The initial setup was quite straightforward.

It took us a couple of weeks to set up all of the log sources and to configure them.

To maintain this solution it's one person and half their time to work on it.

I rate the tool's deployment an eight out of ten. 

We took a month to deploy the solution.

The initial setup for LogPoint is pretty straightforward. It's relatively easy to learn and understand, especially for small organizations. I belong to a small organization that can't afford more expensive products. You won't see LogPoint in review site scoreboards, for example, in Gartner, and the product isn't found under Leaders and Visionaries, but it's still quite effective. It's comparable to going for open-source systems.

Deploying LogPoint was relatively easy. I've been deploying it for a long time. The process is easy, but it's based on how many systems you need to connect to LogPoint. For example, my company has more than fifty assets that need to be integrated with LogPoint, so that could take some time, though the deployment process is much easier. I was able to deploy it within one hour, though.

I believe the initial setup was straightforward but there have been some issues with some of the vendors we are using such as Dell EMC Isilon storage systems. They have a very cool setup for sending logs to a log management system.

I rate the setup an eight out of ten. The solution is deployed on cloud, and it takes a few hours to deploy with a team of five people made up of some engineers.

At first glance, LogPoint is easy to set up. But when you lift the hood, this is where problems start and the learning curve is very steep.

The initial setup is straightforward. Deployment takes about one month, but it depends on the scope of the project.