IBM Resilient: Healthcare
March 14, 2019

IBM Resilient: Healthcare

Gokul Karuppiah | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with IBM Resilient Incident Response Platform

In our organization (Healthcare Recovery Department) we have been using this application for the past two years. Ee replaced a tool called HPBSM which creates the incidence when the application is having an outage. To Replace the HPBSM we came to the tool of IBM Resilient Incident Response. IBM Resilient is used in our recovery application which is created in the net for increasing/classifying the severities of incidents and notifying IT in the event of an outage or cyber attacks caused. lt is also used by the IT team to classify the incidents and take measurable action on time when threats or outages happen.
  • Increasing the severity of incidents when threats or outages happened and informing the IT team/management to take action. Our application is a .net one which is a legacy with SQL server. The number of times it is more vulnerable to threats and the action to be taken was identified using this tool.
  • Prior to using this tool, we were informed of threats by IBM customer support and we took action in around 2 to 3 hours to prevent using NOC team support. However, after we deployed this tool we were able to respond quickly based on the action plan provided along with threat level and severities.
  • Prior to deploying this tool, our incidents were provided by IBM customer support with no necessary information on the same. After this tool was installed in our organization, we were able to get the security alerts instantly and take action with the severity level for threats/attacks.
  • Not anything so far since we are highly dependent on this tool. Probably reduce the number of small alerts we get.
  • Integration with existing technologies optimizes the experience. Due to this, it is well suited for most of the technologies across the market.
  • Since the threat was resolved on time with priority, downtime is less which in turns increases the ROI in the applications across the department.
I have selected this since we are highly dependent on this tool for our applications in healthcare where 1600+ users are working across the world where we need a high level of security and actions to be taken when it is more vulnerable.
This is well suited for a high-level application with 1000+ users that work across timezones of EST, IST, and APT where actions can be taken across 24/7 applications. This tool is less appropriate for the small scale application for which is not much is needed. For example, where the application is used only by users 2-5 users on around 10+.