IBM Resilient Reviews

Our usage of IBM Resilient was primarily limited to communication and incident resolution. Although there was some automation implemented, we experienced delays from the technical side. Therefore, we only utilized it for incident logging, team communication, and documentation purposes. In case of any future incidents, we could easily refer back to the records.

The solution is reliable in our usage.

IBM Resilient is a flexible cybersecurity solution suitable for different industries like finance, governance, and private businesses. It ensures effective incident response, regardless of the specific sector. Whether dealing with financial threats, governance issues, or private organization security, Resilient's tools and workflows automate incident handling, making it valuable across various sectors.

The most valuable features of IBM Resilient are its flexibility and customization options for incident response. You can easily create dynamic playbooks tailored to your needs, which sets it apart from some competitors like Palo Alto. Resilient offers comprehensive incident response capabilities, from case management to automation, threat intelligence enrichment, and even the Bridge Response Module. This flexibility and depth of features make it stand out in helping organizations effectively handle security incidents. Clients appreciate Resilient for its ability to take action swiftly and efficiently.

We have a team for case management that builds use cases for the solution. We use the solution for SOC analysis.

The product is very good at incident response. We have integrated our security with it. We have a firewall and have integrated our domain controller with IBM Resilient. If we want to contain any alert, we can do it using the product. It has been a great tool for the SOAR platform or automation. It is very beneficial. We were able to control the mean time to escalate (MTTE) metrics with the help of the solution.

I didn't work in SOC and IT. However, IBM Resilient is a good tool. IBM Resilient is a good option, especially for its container capabilities. Apart from that, there isn't something for which I use the solution.

Actually, we faced some internal issues while using IBM Resilient. There are other tools simpler than IBM Resilient. So, you have to develop a new infrastructure that involves a lot of scripting, programming, and some extra work to create a very good one. FortiSOAR is simpler than IBM Resilient. It may take me three months or four months to compare between them. IBM Resilient is quite complex, including its configuration. Also, the dashboard in IBM Resilient is not good. Firstly, the IT support is not good. Secondly, the community of IBM Resilient and the steps for integration mentioned in its audiobooks were not good.

IBM Resilient is used primarily for security, particularly cybersecurity in operation centers. My company uses it to monitor the data security-related aspects of the IT infrastructure.

IBM Resilient is beneficial to my company because it gives endpoint visibility through the system's audited security and data logs. At the same time, you can monitor the communication between the systems at the network and endpoint level through IBM Resilient. Using the data from the solution, you can coordinate security data and activities, and you can audit activities from all angles, from different perspectives.

In my company, we use IBM Resilient SOAR.

One of the drawbacks of the solution stems from the fact that it is an expensive product. The solution's price is an area where improvement is required.

There are shortcomings with IBM Resilient's technical support team that can be considered for improvement in the future.

I use the solution for orchestration and managing incidents.

IBM Resilient is a pretty good tool. It sends an email asking for clearance from a notified member in case there is another identity in the system.

I use IBM Resilient in my company to manage areas like automation of non-easy tasks and to be able to integrate with other security controls in our environment. The tool is also useful to manage areas like ticketing and case management.

The configuration area to deal with during the very beginning or initial stages of the product can be the hardest part for users. Dealing with the configuration part in the beginning stages can be difficult since it is very important for users to have the capability to identify what is required within the tool and what you want to automate. The product's configuration during the beginning stages can be an area that needs to be considered for improvement.

The response time of the support is an area of concern where improvements are required.