What is our primary use case?
We are a consulting firm and this is a solution that we use for ourselves, as well as implement it for our customers.
Our use case is to establish a platform for threat analysis across different data sources that we have in the company. Essentially, it is an orchestration platform and we want to make sure that we can tie into different endpoints or data sources from which traffic originates. We need to then detect and analyze threats.
What is most valuable?
The most valuable feature is the risk-based access control.
The team collaboration when it comes to detecting a threat is helpful.
I like the fact that we can leverage the API to be able to establish a connection and share information across different repositories.
The flexibility that it has when using different protocols, like TLP, for communicating, is fairly good.
This solution supports the automated handling of phishing attempts through the collection of potentially malicious emails from end-users. It analyzes them, identifies threats, and assesses risk.
What needs improvement?
Phantom was only recently acquired by Splunk so it is not fully integrated yet. Our area of concern is that Splunk Phantom works with the other Splunk products. At this point, there are certain things that are not fully operational across the rest of the product line.
The extension of the product to allow for better integration with other data sources is something that needs attention. We want to see improvements made to the APIs such that we can connect to many different systems and data sources.
The search capability could be improved by way of better indexing and also integration with third-party solutions such as Elasticsearch.
I would like to see escalation management and integration with communication tools like Slack.
I would like to have more capability around analytics.
There needs to be a better facility for documenting and storing issues, as well as being able to find those issues. Splunk does a good job of that, so I think that it will be done.
What do I think about the stability of the solution?
The solution overall is stable, but it could be more so. It is an application server and there is a vulnerability when a traffic overload occurs, or if there is an incompatibility with a backend or another data source. There is a risk that something can freeze up.
High Availability / Disaster Recovery (HA/DR) is key and Splunk Phantom’s product offerings must ensure sharding and clustering to enable scalability and automated failover
What do I think about the scalability of the solution?
Because this is an orchestration platform, it's supposed to offload the users from being directly involved in looking at and analyzing security issues. It is something that you just let run. From an administration standpoint, we have a team of ten people that work around this platform.
How are customer service and technical support?
Prior to Splunk acquiring Phantom, the support for this solution was subpar. Now, however, the support model has changed and it is pretty reasonable.
How was the initial setup?
The initial setup takes some time because you have to configure it and then connect it to different data sources and make sure that they operate properly. It requires an engineer who's fairly knowledgeable in security, interaction, setup, and administration.
In terms of the deployment time, I think that it is something that you can get up and running in perhaps two or three months. I don't think that you could get this up and running fully in a week, for example.
What's my experience with pricing, setup cost, and licensing?
It is a subscription-based licensing model that varies depending on how much data is processed by Spunk. There are built-in volume discounts.
There are some additional costs if you want to get some front-end support or installation or setup, which is part of professional services. There are also some modules, such as analytics, that Splunk will provide for an additional fee.
What other advice do I have?
My advice to anybody who is considering this solution is to first really understand the requirements that you have, well enough. You need to identify and understand the data sources that you need, prior to purchase, to ensure that there is a need and also that there are no issues with incompatibility or connectivity. You also need to have the right resources to assess, implement, or oversee the implementation. You're going into an environment that requires a little bit of understanding of artificial intelligence because the SOAR platform requires setting up some rules. You also need to have a technical support group in-house to be able to help, otherwise, you would be dependent on Splunk for assistance.
Overall, this product is fairly good but it's not quite mature yet. It needs some enhancement and some stabilization in some areas.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?