The solution is straightforward and simple. 

In our case, it was a quite complicated setup due to the client's policies. It took us about three months to go live.

The initial setup is a bit difficult. I noticed that it took a while for the secured operations to go live. There were six months of delays, and we were already six months delayed on our end. A one-year delay from their go-live date is a bit too long. 

It doesn't require a separate application; it's accessible via a browser. We use it browser-based.

The initial setup for ServiceNow Security Operations isn't complex, and you can easily customize and deploy it for customers.

Deploying the solution requires one architect and two developers, and on average, it takes almost six months to deploy ServiceNow Security Operations. Still, if you have six people in the deployment team, it would only take three months to deploy, but that doesn't include customization, requirement gathering, and reporting.

The initial setup of ServiceNow Security Operations is easy. It does not take too much time. It is a mature service management product. It is out-of-box integration for almost all the leading SIEM tools as well as SOC platforms. The setup is straightforward. 

It does depend on the use cases that need to be developed. Sometimes there are out-of-the-box use cases that can be integrated directly. Sometimes you might have certain applications which require you to make new use cases or have some integrations that are not available out of the box. In these cases, for custom integrations, you might have to do customer development, which would take a bit longer.

For a medium-sized deployment, it should not take more than two and a half months or eight to ten weeks. You would need a small team of approximately seven people to support that, depending on the operating window you are supporting.

I would rate setup 4 out of 5. It could be simpler.

Our implementation plan just depends. We use an agile process and we do iterative development and let people try and see how it works in the organization and then tweak it. That was the approach, on a spectrum of incremental improvement or continuous improvement.

The amount of staff needed for deployment and maintenance depends on the scale of what you're rolling out. You could implement it with three people, or you could implement it with a team of five or six. It depends on how you want to support it.

Setting up ServiceNow Security Operations initially can be a bit complex, especially if you are new to the field. Based on my experience, having a background in security, hardware, infrastructure, and network alerts makes the process more manageable. However, for those less familiar with these areas, it might pose a challenge and require additional support from developers or individuals with relevant expertise. Overall, the complexity of the setup depends on one's familiarity with security and related domains.

The initial setup is easy. We refer to the setup and installation guide provided by ServiceNow. They have good documentation, which makes it easier to handle the process. It takes a few hours to complete.

The number of executives required to implement it depends on different regions. We currently have a team of four resources and one solution architect to oversee the deployment.

Most clients prefer to deploy it on-premises for security reasons, but we suggest they go for the cloud version. We appoint one resource to take care of the maintenance post setup.

I didn't get involved in the initial setup. That said, I would suppose it's complex due to our needs.

We don't have enough staff to maintain the solution. 

The initial setup has a moderate level of difficulty. It's not simple, but it's not overly complex.

The initial setup was straightforward. It's the people side of stuff that gets complicated.

The analysis you have to put it in with existing processes and the customer needs to adapt and adopt to the out of the box. Sometimes that gets politically challenged because people like to use the systems and processes, they're used to. It's not the technology. It's the impact on their day-to-day.

I have not personally deployed this product but from the feedback that I have heard, my understanding is that it is pretty easy.