ServiceNow Security Operations Reviews

If we encounter challenges while deploying, we raise incidents. These incidents are categorized by priority: high, medium, and low. We assign an incident number and notify the relevant teams to address the issue. For instance, if we experience a problem with Cloud services or any other issue, we will raise an incident and suggest a course of action. Similarly, they are categorized into expedited, emergency, normal, and planned changes when raising change requests.

Every tool we are using, such as PNC, ServiceNow, Jira, and many others, is fine. 

ServiceNow Security Operations is used for threat intelligence and managing issues, offences or incidents. 

The SOAR module of ServiceNow Security Operations is the most valuable feature and it can be managed easily. 

I use ServiceNow for ticketing purposes. Specifically, I raise tickets between the support team. This is used by internal teams within the company for managing support-related tasks.

ServiceNow is a convenient platform to raise tickets, and the respective support team will contact us to resolve any issues. Although the platform is neither exceptional nor poor, it facilitates communication and organization within the support framework.

Customer awareness and understanding of ServiceNow's SecOps capabilities could be improved, as many clients may not fully utilize the platform's potential due to a lack of awareness or training.

I have been using ServiceNow Security Operations for 12 years. 

The product has a very simple UI. I am biased toward ServiceNow. I like the look and feel. I find it very easy to navigate.

This automated integration that they have should work flawlessly, and we should not have an experience on our end where maybe it's more manual than expected. Somebody needs to push those users and the access through. There needs to be more integration on the side of security permissions.

The initial setup is difficult. 

The product needs better descriptions of rows. We're checking the dependencies of the applications. Most of the time, we're just puzzling together to see, okay, which application is this owned by, which row gives permission to this application, et cetera. Therefore, a better description of the connection of items in the applications for the security operations center management would be ideal.

I used this solution for incident management for issues that take longer to resolve.

About 1,000 people were using this solution in my organization, including management and procurement.

I wasn't using the latest version. 

It's very slow. When you click a button or update a field, it takes forever to actually react.

It's not very user-friendly. You almost need a degree in IT management to be able to use it.

I would like it to have a more intuitive UI or at least better documentation.

I am a security architect. I construct the solutions. ServiceNow Security Operations is on-premises, however, it's a hybrid model where you can have a public cloud also working in tandem with your on-site deployment.

The main use case is SecOps or security operations. ServiceNow Security is a two-way ticketing model that gets integrated with Splunk, for example. Splunk will provide two-way integration into the service management process. You have Splunk on one end and ServiceNow on the other end. The tickets will be integrated between the two and be either manually or automatically created. The tickets can be initiated from either platform and automatically or manually pushed as well.

I like that you can also work the solution together as a hybrid modern service for your customers. At the backend, you can make the solution any way you would like, whether it is purely on-premises or a hybrid model. You can offer it as a service to your clients.

The most valuable features are service management and case management. It also takes care of problem management. ServiceNow Security Operations also takes care of GRC, governance, risk, and compliance, enabling it to provide risk assessment.

We use it on a daily basis. We received tickets in ServiceNow. We can connect with the user using the ServiceNow application. 

We can drop an email, use the top bar, create filters, see how many tickets we have, monitor daily usage, track received tickets, and manage follow-ups. We can also manage dependent tickets and the "Accredited Fine."

The "follow" feature is really good. If the user is not responding, there's an option to "follow". Just click on the button, and it will automatically trigger an email to the end user.