We haven't tested it extensively, but we feel that it's going to be a very scalable solution which is going to handle the volume we intend to push to it.

If everything is onboarded the way we want it, the entire company will be using it, in that all samples will be coming from all sorts of sources. It will be "under the hood" doing analysis constantly, 24 hours a day. Our company has 10,000-plus employees.

We're not using it very extensively yet. We're still in the middle stages of implementation. We haven't integrated it with very many systems in our company yet, and we are still trying to figure out the engineering problems surrounding it, and are working on getting it secure enough to deploy in our environment.

There are a number of different use cases for it. One of them is someone using it directly for doing threat hunting or threat detection. I'm not sure how many people are on those teams. But with the different threat-hunting teams and threat-detection teams, as well as forensic teams that might be using it, we could have at least 100 direct users.

With everything else, it's being used indirectly by a number of services, under the hood. Anything that gets saved on a network share, any new updates on any of the operating systems - Linux, Windows, etc. - we want analyzed, as well as anything that gets saved or that gets brought in as an email attachment. We'd like, eventually, that anything that comes over the wire, that comes through our proxies and firewalls, downloaded by someone, to be analyzed. It's going to be the crux of a solution that does a lot of automated analysis. It's just one piece, but it's going to be a very critical piece because it's going to be the on-ramp.

Responsibility for the solution will move to another team once I'm done with it, and that other team has about 15 people. But they support a lot of other things. They're a custom-support team, they support custom solutions.

The scalability is good. It's a scalable product.

Only malware analysts and reverse engineers are currently leveraging the product, and those are around 15 users.

It can be scaled a lot better than the way we're using it. The analogy I like to use is that I have an iPad and I probably only use 15 percent of its capabilities. We're using about the same percentage of ReversingLabs' capabilities. It can be scaled to be more broad-based within our environment. I hope to push that in the next few quarters.

If the solution was to be integrated, we're talking about close to a million assets, worldwide.

I rate the tool's scalability a ten out of ten.