The solution can scale well. You can set up integrations and expand them. 

About 80% to 90% of the company is using the solution. However, not everyone can raise incidents. Maybe only 50% of users could do that.

Eventually, the entire company will be on the solution, so the user base may be as high as 300,000 eventually.

We have around 500 end users using this solution in our organization. 

ServiceNow Security Operations is easy to scale. I wasn't the one who scaled it, and I didn't touch the data from the other tools. Still, it's just a matter of going on a call, gathering the XML files and other requirements, figuring out how the data can be loaded into the different tables, mapping and integrating the data, creating different paths from the map, and loading the data.

The solution is scalable. This is primarily due to the ITSM tools. The actual security monitoring or security orchestration automation is done by other products like Splunk, LogRhythm, or QRadar to provide a holistic solution.

We have many engineers in the ServiceNow space. There are approximately 450 people who are dedicated to working on this, and we can ramp up quickly.

It's absolutely scalable. We were working on one of the largest implementations in the world.

It is fairly scalable. In our organization, we have approximately 200 to 300 users working with ServiceNow Security Operations on the client side.

Our client has 20 to 30 instances managed by ServiceNow Security Operations. It is a scalable platform.

I haven't dealt directly with scaling the solution and therefore cannot comment on it. 

We have 2,000 people using the solution.

Scalability has to be designed and decided before implementation. It depends on how much infrastructure the client wants to invest in and their future plans. These have to be taken into consideration prior to implementation so that the sizing will be correct.

It is very scalable.

Scalability has not been a problem.